[Touch-packages] [Bug 1861472] Re: upgrade from fresh bionic to focal needlessly prompts user
** Changed in: openssh (Debian) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1861472 Title: upgrade from fresh bionic to focal needlessly prompts user Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: Fix Committed Bug description: Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts for how to handle a change to /etc/ssh/sshd_config To reproduce the issue: lxc launch ubuntu:18.04 u18 lxc exec u18 -- bash # within container do-release-upgrade -d # select restart services when prompted Eventually you'll be prompted to accept changes to /etc/ssh/sshd_config or not because of "local changes". Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.1p1-5 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 03:37:55 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856257] Re: SIOCSIFFLAGS: Input/output error
[Expired for net-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: net-tools (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1856257 Title: SIOCSIFFLAGS: Input/output error Status in net-tools package in Ubuntu: Expired Bug description: My wifi is no longer working since a recent update (yesterday, I think). When typing “ifconfig -a”, I get (among other connections), the following one, which seems to correspond to my wifi card: ```bash wlp59s0: flags=4098 mtu 1500 ether 5c:87:9c:fa:81:c9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` I thus tried to switch it on, but I get the following message: ```bash $ sudo ifconfig wlp59s0 up SIOCSIFFLAGS: Input/output error ``` This error message is not really helpful: I would have expected ifconfig to provide a more user-friendly explanation about what is not working well. Other commands that might be relevant: ```bash $ iwconfig lono wireless extensions. enp0s20f0u1 no wireless extensions. wlp59s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ sudo ip link set wlp59s0 up RTNETLINK answers: Input/output error ``` I’m calling apport-collect on this bug to add other relevant information. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libpcre3 2:8.39-9 libselinux1 2.7-2build2 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-28 (106 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Package: net-tools 1.60+git20161116.90da8a0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1065-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1856257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863396] [NEW] Unable to mkfs.ext4 a 64T Drobo 5DS consumer raid device. Formatted easily on MX Linux.
Public bug reported: I'm also having trouble getting it to recognize some other standard USB external drives. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: util-linux 2.34-0.1ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 14 19:21:55 2020 InstallationDate: Installed on 2020-01-17 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1863396 Title: Unable to mkfs.ext4 a 64T Drobo 5DS consumer raid device. Formatted easily on MX Linux. Status in util-linux package in Ubuntu: New Bug description: I'm also having trouble getting it to recognize some other standard USB external drives. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: util-linux 2.34-0.1ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 14 19:21:55 2020 InstallationDate: Installed on 2020-01-17 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1863396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863165] Re: autoremove-kernels doesn't purge kernels
** Changed in: apt (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1863165
Title:
autoremove-kernels doesn't purge kernels
Status in apt package in Ubuntu:
New
Bug description:
Maybe this is a configuration issue, but:
# apt-get --purge autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# dpkg -l | grep ^rc | cut -c-70
rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext
And the "rc" translates to "Remove/Conf-files". For some reason
/etc/apt/apt.conf.d/01autoremove-kernels (triggered by unattended-
upgrades.service) doesn't seem to remove the kernel's configuration
files.
The kernel images and modules are removed, only the package list (and
maybe /usr/share/doc/linux*) is cluttered with the remnants of old
kernels.
Workaround:
dpkg -l | awk '/^rc.*linux-(image|modules)/ {print $2}' | xargs dpkg
-P
# lsb_release -r; dpkg -s apt | grep Ver; uname -r
Release:18.04
Version: 1.6.12
5.3.0-23-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1863165/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@sponsor team, The change of 'Headset Mic Boost Volume' 1" to 'Mic Boost Volume' 2" in the all LENOVO_*/LENOVO_*.conf is already in the updated debdiff (#10 and #11). And those 4 LENOVO folder names cover all machines we enabled in the oem projects. If need to add new machines' support, I will collect a couple of new machines then open a new SRU. So if possible, please help enqueue the #10 and #11. thx. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861408] Re: firefox apparmor messages
I should further note that this needs kernel patches to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
[10131.880788] audit: type=1400 audit(1580237490.777:123):
apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
comm="firefox" requested_mask="wrc" denied_mask="wrc" fsuid=1000
ouid=1000
these appeared while saving a file:
Jan 30 11:08:28
[Touch-packages] [Bug 1861408] Re: firefox apparmor messages
Firefox uses cap sys_admin to set up its sandbox, which is extremely
unfortunate but required on linux to be able to set up the
user_namespace, do the chroot etc. Current the LSM and user namespaces
don't interact as well as they should.
AppArmor can NOT properly determine the policy namespace that it should
be in with the user_namespace after firefox enters its sandbox. This
result in the cap_sys admin messages
This is a known problem and we are working on it. At the moment we
recommend granting the capability in the profile and letting firefox
setup its sandbox. Unfortunately this means you can't guarantee the rest
of the program isn't doing things it shouldn't.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user"
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Paolo, So far, both ucm2 from upstream and ucm from Intel only support 2 speakers, for Bass speakers support, the upstream is discussing it, please read this thread： https://mailman.alsa-project.org/pipermail /alsa-devel/2020-February/162701.html, if you have some idea, please reply that thread. And after the Bass speakers support is ready, I will co-work with Intel audio team to backport it to ucm. (maybe need some change in the pulseaudio too.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861408] Re: firefox apparmor messages
i asked about sys_admin capability and got some answers:
https://groups.google.com/forum/#!topic/mozilla.dev.platform/UK4nm7MtTxQ
(i wanted to ask in firefox-dev mailing list but the dev-platform list
was said about as more appropriate).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
[10131.880788] audit: type=1400 audit(1580237490.777:123):
apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/dinar/.cache/mesa_shader_cache/index"
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
** Also affects: gnunet (Ubuntu) Importance: Undecided Status: New ** Changed in: gnunet (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in gnunet package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: In Progress Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863261] Re: modinfo prints an error message if modules.builtin.bin is missing
This bug was fixed in the package initramfs-tools - 0.133ubuntu15 --- initramfs-tools (0.133ubuntu15) focal; urgency=medium * mkinitramfs: Copy modules.builtin.bin into initramfs (LP: #1863261) -- Rafael David Tinoco Fri, 14 Feb 2020 15:05:29 + ** Changed in: initramfs-tools (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1863261 Title: modinfo prints an error message if modules.builtin.bin is missing Status in initramfs-tools package in Ubuntu: Fix Released Status in kmod package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: Fix Released Status in kmod source package in Focal: Fix Released Bug description: Running a simple "update-initramfs -u" in a system with kmod version 26+20191223-1ubuntu1 (from focal-proposed) will result into a bunch of: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_FLkEYb/lib/modules/5.4.0-14-generic/modules.builtin.bin' errors. That happens because: modinfo prints an error message if modules.builtin.bin is missing and it was fixed upstream (Debian) in: commit 835d584 Author: Ben Hutchings Date: Sat Jan 18 15:44:32 2020 mkinitramfs: Copy modules.builtin.bin into initramfs modinfo now prints an error message if modules.builtin.bin (created by depmod) is missing. Copy it in early if it's present. Closes: #948257 Signed-off-by: Ben Hutchings and reported in bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863219] Re: WiFi module RTL8723DE not supported @live / installed session
You could test preview images of 20.04 by downloading them from here: http://cdimage.ubuntu.com/ubuntu/daily-live/current/ ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) ** No longer affects: kernel-package (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1863219 Title: WiFi module RTL8723DE not supported @live / installed session Status in linux package in Ubuntu: Incomplete Bug description: Hi I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some wireless connectivity problems with Realtek chips. My system compatible with rtl8723de wifi driver module. Laptop model no HP 14q-cs0009tu. Ubuntu live session can’t detect the card nor the post-installed OS does. Therefore, no wifi switch/icon. I would hope Ubuntu 20.04 LTS natively support this wireless chip. regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863219/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev
Here's the upstream changes to growpart I'm suggesting: https://code.launchpad.net/~raharper/cloud-utils/+git/cloud- utils/+merge/379177 I've also proposed on modifications to cloud-init's cc_growpart as a further method to aid debugging if this hit as well as some mitigation around the race. https://github.com/canonical/cloud-init/pull/213 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: New Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863356] Re: libtool and libtool-doc 2.4.6-12 both contain /usr/share/doc/libtool/AUTHORS causing upgrade failures
see also bug: https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1862925 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtool in Ubuntu. https://bugs.launchpad.net/bugs/1863356 Title: libtool and libtool-doc 2.4.6-12 both contain /usr/share/doc/libtool/AUTHORS causing upgrade failures Status in libtool package in Ubuntu: Confirmed Status in libtool package in Debian: Unknown Bug description: Unpacking libtool-doc (2.4.6-12) over (2.4.6-11) ... dpkg: error processing archive /tmp/apt-dpkg-install-tTUGeR/289-libtool-doc_2.4.6-12_all.deb (--unpack): trying to overwrite '/usr/share/doc/libtool/AUTHORS', which is also in package libtool 2.4.6-12 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libtool 2.4.6-12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: i3 Date: Fri Feb 14 09:04:32 2020 InstallationDate: Installed on 2017-12-15 (790 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libtool UpgradeStatus: Upgraded to focal on 2019-09-23 (144 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1863356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863356] Re: libtool and libtool-doc 2.4.6-12 both contain /usr/share/doc/libtool/AUTHORS causing upgrade failures
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libtool (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtool in Ubuntu. https://bugs.launchpad.net/bugs/1863356 Title: libtool and libtool-doc 2.4.6-12 both contain /usr/share/doc/libtool/AUTHORS causing upgrade failures Status in libtool package in Ubuntu: Confirmed Status in libtool package in Debian: Unknown Bug description: Unpacking libtool-doc (2.4.6-12) over (2.4.6-11) ... dpkg: error processing archive /tmp/apt-dpkg-install-tTUGeR/289-libtool-doc_2.4.6-12_all.deb (--unpack): trying to overwrite '/usr/share/doc/libtool/AUTHORS', which is also in package libtool 2.4.6-12 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libtool 2.4.6-12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: i3 Date: Fri Feb 14 09:04:32 2020 InstallationDate: Installed on 2017-12-15 (790 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libtool UpgradeStatus: Upgraded to focal on 2019-09-23 (144 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1863356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863369] Re: Livepatch is running, but appears OFF in 'software & updates'
The 'Software & Updates' interface is software-properties, not update- notifier. ** Package changed: update-notifier (Ubuntu) => software-properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1863369 Title: Livepatch is running, but appears OFF in 'software & updates' Status in software-properties package in Ubuntu: New Bug description: I have a similar problem to #1758980 Enabling LivePatch fails, but not so sure it is the same. When I verify Livepatch status (sudo canonical-livepatch status): client-version: 9.4.8 architecture: x86_64 cpu-model: Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz last-check: 2020-02-14T09:29:57-03:00 boot-time: 2020-02-14T07:29:23-03:00 uptime: 2h26m29s status: - kernel: 4.15.0-76.86-generic running: true livepatch: checkState: checked patchState: nothing-to-apply version: "" fixes: "" But in 'Software & Updates' Livepatch tab all I got is 'OFF', and I can't switch ON or click on it. It is written 'Livepatch requires an internet connection'. Is this a known bug to be ignored, or something else that must be fixed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1863369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863369] [NEW] Livepatch is running, but appears OFF in 'software & updates'
You have been subscribed to a public bug: I have a similar problem to #1758980 Enabling LivePatch fails, but not so sure it is the same. When I verify Livepatch status (sudo canonical-livepatch status): client-version: 9.4.8 architecture: x86_64 cpu-model: Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz last-check: 2020-02-14T09:29:57-03:00 boot-time: 2020-02-14T07:29:23-03:00 uptime: 2h26m29s status: - kernel: 4.15.0-76.86-generic running: true livepatch: checkState: checked patchState: nothing-to-apply version: "" fixes: "" But in 'Software & Updates' Livepatch tab all I got is 'OFF', and I can't switch ON or click on it. It is written 'Livepatch requires an internet connection'. Is this a known bug to be ignored, or something else that must be fixed? ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- Livepatch is running, but appears OFF in 'software & updates' https://bugs.launchpad.net/bugs/1863369 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Description changed: + + [Impact] + [Test Case] + [Potential Regression] + + [Other informations] + + * Upstream bug[0] and fix[1]: + + https://bugzilla.redhat.com/show_bug.cgi?id=1575944 + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 + + * Only affectinb Bionic: + + $ git describe --contains f03ae35 + 1.10.8~2 + + $ rmadison network-manager + ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates + network-manager | 1.20.4-2ubuntu2.2 | eoan-updates + network-manager | 1.22.4-1ubuntu2 | focal + + [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. - + ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux - - Machine Type = s390x - + + Machine Type = s390x + ---Debugger--- A debugger is not configured - + ---Steps to Reproduce--- - When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. + When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode - root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond + root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 - link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff - inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond -valid_lft 353sec preferred_lft 353sec - inet6 fe80::ff:feb3:b522/64 scope link -valid_lft forever preferred_lft forever - + link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff + inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond + valid_lft 353sec preferred_lft 353sec + inet6 fe80::ff:feb3:b522/64 scope link + valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode - root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond + root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 - link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff - inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute -valid_lft forever preferred_lft forever - + link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff + inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute + valid_lft forever preferred_lft forever ==> Correct LP-Package
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@hui.wang thanks, it's finally works, i've got both speakers and mic recognized as specified in the UCM files. There is just another major drawback that affect thinkpad x1 carbon 7th which has 5 speakers 4+1, but only 2 of them gets recognized, as shown in the attachment. Should the UCM file be in charge of this ? ** Attachment added: "Screenshot from 2020-02-14 21-02-43.png" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5328236/+files/Screenshot%20from%202020-02-14%2021-02-43.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849859] Re: smb printing fails
I'm updating focal to 4.11.5 (hoping debian will update to 4.11.6 soon, and will check again how printing is working in this release. If it still fails, I'll grab the patches I saw being discussed upstream and apply them, and then I will have something I can start preparing as an SRU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Regarding your question about LLDP and IPv6... The default Ubuntu 18.04.3 configuration has an IPv6 enabled kernel, but the interface only has the default link local address configured. I've seen it do router solicitation on link state changes and periodically thereafter. I think I recall seeing somewhere above that you were going to try without IPv6. Have you seen different behavior with IPv6 disabled? I don't expect to see LLDP because I have the two NICs wired directly to each other, back to back. I'm not running any LLDP daemon on the host. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
Thanks for reporting the outcome of your test. We will start the SRU process in order to update network-manager package next week. Regards, Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821810] Re: gdebi crashes when trying to install packages
Hello what is the status of this bug, I just have installed an ubuntu version (elementaryOS) and I have this bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1821810 Title: gdebi crashes when trying to install packages Status in gdebi package in Ubuntu: Confirmed Bug description: When I try to install some deb packages gdebi disapears. It does not show me any error report. It will just disapear from my screen. Lubuntu 18.4 LTS gdebi 0.9.5.7+nmu2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdebi 0.9.5.7+nmu2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 26 23:30:04 2019 InstallationDate: Installed on 2019-03-18 (8 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1821810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
** Changed in: voms-mysql-plugin (Ubuntu) Status: New => In Progress ** Changed in: vtk7 (Ubuntu) Status: New => In Progress ** Changed in: w1retap (Ubuntu) Status: New => In Progress ** Changed in: zoneminder (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: In Progress Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
** Changed in: redland (Ubuntu) Status: New => In Progress ** Changed in: tango (Ubuntu) Status: New => In Progress ** Changed in: tntdb (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
** Changed in: qt4-x11 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
** Changed in: pike8.0 (Ubuntu) Status: New => In Progress ** Changed in: pvpgn (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
The tpa_aborts shouldn't be a concern. They merely indicate that a TCP flow could not be aggregated. That could have a performance impact, of course, but that should manifest as counted drops somewhere if this were the case. Importantly, the tpa_aborts only apply to TCP traffic, but you see the problem for ICMP and UDP too. Note, the tpa_aborts also appear to be evident on the primary as active interface while things are working as expected. A difference in magnitude tpa_aborts from one test run to another may be a clue about something else that's happening though, but I'm not sure that we are comparing apples to apples with respect the ethtool -S dumps posted thus far (when were they captured relative to the test runs, which interface was active at the time, etc?). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$
[Touch-packages] [Bug 1794478] Comment bridged from LTC Bugzilla
--- Comment From abhir...@in.ibm.com 2020-02-14 12:51 EDT--- Eric, network-manager 1.10.6-2ubuntu1.3+testpkg20201202b1 fix provided is Working good. Network connection with auto ipv4 mode and manual ipv6 mode is NOW rightly setting ipv4 from server and manual ipv6. Deactivated and Activated the network connection to see both ips are still retained. No issues seen here. restart of network manager also the ips are retained. --- Comment From abhir...@in.ibm.com 2020-02-14 12:59 EDT--- nmcli c s for bond device , the output parameters being watched are now as expected ipv4.method:auto ipv6.method:manual ipv6.addresses: fe81::ff:fe97:a27f/64 GENERAL.STATE: activated IP4.ADDRESS[1]: 10.2.3.60/24 IP6.ADDRESS[1]: fe81::ff:fe97:a27f/64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
** Changed in: opendnssec (Ubuntu) Status: New => In Progress ** Changed in: opensmtpd-extras (Ubuntu) Status: New => In Progress ** Changed in: orthanc-mysql (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 887079] Re: Software Sources shows codenames not version numbers
** Merge proposal linked: https://code.launchpad.net/~osomon/software-properties/+git/software-properties/+merge/379239 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/887079 Title: Software Sources shows codenames not version numbers Status in software-properties package in Ubuntu: In Progress Bug description: In the updates tab software-properties shows codenames such as 'oneiric-updates' and 'oneiric-proposed'. As I understand it we shouldn't really show the codename to the user. It also seems somewhat redundant, it's not like that screen would ever have anything other than $current_release-* in it. I can see why the 3rd party sources might display codenames as users may (for whatever reason) want to add the source for an older (or newer) release on a 3rd party site to get an app. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: software-properties-gtk 0.81.10 Uname: Linux 3.1.0-999-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Nov 7 11:20:31 2011 PackageArchitecture: all ProcEnviron: PATH=(custom, user) SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/887079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863356] [NEW] libtool and libtool-doc 2.4.6-12 both contain /usr/share/doc/libtool/AUTHORS causing upgrade failures
Public bug reported: Unpacking libtool-doc (2.4.6-12) over (2.4.6-11) ... dpkg: error processing archive /tmp/apt-dpkg-install-tTUGeR/289-libtool-doc_2.4.6-12_all.deb (--unpack): trying to overwrite '/usr/share/doc/libtool/AUTHORS', which is also in package libtool 2.4.6-12 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libtool 2.4.6-12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: i3 Date: Fri Feb 14 09:04:32 2020 InstallationDate: Installed on 2017-12-15 (790 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libtool UpgradeStatus: Upgraded to focal on 2019-09-23 (144 days ago) ** Affects: libtool (Ubuntu) Importance: Undecided Status: New ** Affects: libtool (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug focal ** Bug watch added: Debian Bug tracker #950916 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950916 ** Also affects: libtool (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950916 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtool in Ubuntu. https://bugs.launchpad.net/bugs/1863356 Title: libtool and libtool-doc 2.4.6-12 both contain /usr/share/doc/libtool/AUTHORS causing upgrade failures Status in libtool package in Ubuntu: New Status in libtool package in Debian: Unknown Bug description: Unpacking libtool-doc (2.4.6-12) over (2.4.6-11) ... dpkg: error processing archive /tmp/apt-dpkg-install-tTUGeR/289-libtool-doc_2.4.6-12_all.deb (--unpack): trying to overwrite '/usr/share/doc/libtool/AUTHORS', which is also in package libtool 2.4.6-12 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libtool 2.4.6-12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: i3 Date: Fri Feb 14 09:04:32 2020 InstallationDate: Installed on 2017-12-15 (790 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libtool UpgradeStatus: Upgraded to focal on 2019-09-23 (144 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1863356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 887079] Re: Software Sources shows codenames not version numbers
Reference of the spec update: https://wiki.ubuntu.com/SoftwareUpdates?action=diff=69=70. ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: software-properties (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/887079 Title: Software Sources shows codenames not version numbers Status in software-properties package in Ubuntu: In Progress Bug description: In the updates tab software-properties shows codenames such as 'oneiric-updates' and 'oneiric-proposed'. As I understand it we shouldn't really show the codename to the user. It also seems somewhat redundant, it's not like that screen would ever have anything other than $current_release-* in it. I can see why the 3rd party sources might display codenames as users may (for whatever reason) want to add the source for an older (or newer) release on a 3rd party site to get an app. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: software-properties-gtk 0.81.10 Uname: Linux 3.1.0-999-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Nov 7 11:20:31 2011 PackageArchitecture: all ProcEnviron: PATH=(custom, user) SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/887079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
** Changed in: util-linux (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Released Status in util-linux source package in Bionic: Fix Released Status in util-linux source package in Disco: Won't Fix Status in util-linux source package in Eoan: Fix Released Status in util-linux source package in Focal: Fix Released Status in util-linux package in Debian: New Bug description: [Impact] * Users with an XFS filesystem on top of bcache (this is seen on some ceph, cloud deployments) might fail to reference the bcache device by UUID or other udev properties. * The journal of the regular XFS filesystem in the bcache device is incorrectly detected as an XFS external log; so two superblocks are detected (bcache and xfs_external_log). * Thus blkid fails with ambivalent superblocks detected then doesn't provide the usual udev properties (UUID, etc.) * The fix improves the probe function for XFS external log so it detects it's regular XFS and bails out. [Test Case] * See test steps detailed in comment #7 and later. - Create an XFS filesystem with the journal/log in the beginning of the bcache device (< 256K). - Stop the bcache device. - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'. $ sudo make-bcache -B $BACKING_DEV $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop $ sudo blkid -o udev -p $BACKING_DEV [Regression Potential] * The patch only changes the detection function for XFS external log to be more general about the sector where the magic of regular XFS may be found (which is shifted inside the bcache.) * It still checks at sector zero (the only one checked previously), so this behavior didn't change. * Possible regressions are actual XFS external log devices that are not anymore detected as such. (Although that would probably indicate a different bug in libblkid.) [Other Info] * upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832417] Re: wrong soundfont path
** Changed in: fluidsynth (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fluidsynth in Ubuntu.
https://bugs.launchpad.net/bugs/1832417
Title:
wrong soundfont path
Status in fluidsynth package in Ubuntu:
Confirmed
Status in fluidsynth package in Debian:
Fix Released
Bug description:
libfliudsynth provides an API to locate the default
soundfonts. Its like below:
ret = fluid_settings_dupstr(settings, "synth.default-soundfont", );
if (ret == 0 || access(sfont, R_OK) != 0) {
ret = fluid_synth_sfload(synth, sfont, TRUE);
}
Under ubuntu it returns
/usr/share/soundfonts/default.sf2
but its unclear what package provides this,
if any. At least not fluid-soundfont-gm.
This font path can be specified during fluidsynth
build. The valid one under ubuntu seems to be
/usr/share/sounds/sf2/FluidR3_GM.sf2
But as this font may not be installed, I would
suggest fluidsynth to check against the pre-defined
list of pathes, and return error if nothing is found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1832417/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1
Bug report filed https://bugzilla.kernel.org/show_bug.cgi?id=206535 ** Bug watch added: Linux Kernel Bug Tracker #206535 https://bugzilla.kernel.org/show_bug.cgi?id=206535 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863219] Re: WiFi module RTL8723DE not supported @live / installed session
** Also affects: kernel-package (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1863219 Title: WiFi module RTL8723DE not supported @live / installed session Status in kernel-package package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hi I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some wireless connectivity problems with Realtek chips. My system compatible with rtl8723de wifi driver module. Laptop model no HP 14q-cs0009tu. Ubuntu live session can’t detect the card nor the post-installed OS does. Therefore, no wifi switch/icon. I would hope Ubuntu 20.04 LTS natively support this wireless chip. regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1863219/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863261] Re: modinfo prints an error message if modules.builtin.bin is missing
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1863261 MERGE: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/379222 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1863261 Title: modinfo prints an error message if modules.builtin.bin is missing Status in initramfs-tools package in Ubuntu: In Progress Status in kmod package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: In Progress Status in kmod source package in Focal: Fix Released Bug description: Running a simple "update-initramfs -u" in a system with kmod version 26+20191223-1ubuntu1 (from focal-proposed) will result into a bunch of: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_FLkEYb/lib/modules/5.4.0-14-generic/modules.builtin.bin' errors. That happens because: modinfo prints an error message if modules.builtin.bin is missing and it was fixed upstream (Debian) in: commit 835d584 Author: Ben Hutchings Date: Sat Jan 18 15:44:32 2020 mkinitramfs: Copy modules.builtin.bin into initramfs modinfo now prints an error message if modules.builtin.bin (created by depmod) is missing. Copy it in early if it's present. Closes: #948257 Signed-off-by: Ben Hutchings and reported in bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863219] Re: WiFi module RTL8723DE not supported @live / installed session
** Package changed: ubuntu => network-manager (Ubuntu) ** Description changed: Hi I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some wireless connectivity problems with Realtek chips. My system compatible with rtl8723de wifi driver module. Laptop model no HP 14q-cs0009tu. Ubuntu live session can’t detect the card nor the post-installed OS does. + Therefore, no wifi switch/icon. I would hope Ubuntu 20.04 LTS natively support this wireless chip. regards. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1863219 Title: WiFi module RTL8723DE not supported @live / installed session Status in network-manager package in Ubuntu: New Bug description: Hi I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some wireless connectivity problems with Realtek chips. My system compatible with rtl8723de wifi driver module. Laptop model no HP 14q-cs0009tu. Ubuntu live session can’t detect the card nor the post-installed OS does. Therefore, no wifi switch/icon. I would hope Ubuntu 20.04 LTS natively support this wireless chip. regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1863219/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863219] [NEW] WiFi module RTL8723DE not supported @live / installed session
You have been subscribed to a public bug: Hi I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some wireless connectivity problems with Realtek chips. My system compatible with rtl8723de wifi driver module. Laptop model no HP 14q-cs0009tu. Ubuntu live session can’t detect the card nor the post-installed OS does. I would hope Ubuntu 20.04 LTS natively support this wireless chip. regards. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment realtek rtl8723de wifi -- WiFi module RTL8723DE not supported @live / installed session https://bugs.launchpad.net/bugs/1863219 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758980] Re: Enabling LIvePatch fails
I have a similar problem, but not so sure it is the same. When I verify Livepatch status: client-version: 9.4.8 architecture: x86_64 cpu-model: Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz last-check: 2020-02-14T09:29:57-03:00 boot-time: 2020-02-14T07:29:23-03:00 uptime: 2h26m29s status: - kernel: 4.15.0-76.86-generic running: true livepatch: checkState: checked patchState: nothing-to-apply version: "" fixes: "" But in 'Software & Updates' Livepatch tab all I got is 'OFF', and I can't switch ON or click on it. It is written 'Livepatch requires an internet connection'. Is this a known bug to be ingnored, or something else that must be fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1758980 Title: Enabling LIvePatch fails Status in Canonical Live Patch Client: Fix Released Status in software-properties package in Ubuntu: Invalid Status in software-properties source package in Bionic: Invalid Bug description: I logged in with my Launchpad credentials to GNOME Settings > Online Accounts > Ubuntu Single Sign-On I opened the Software & Updates app. I switched to the Updates tab and tried to enable Livepatch. I entered my sudo password when prompted. After a few moments, I got a popup telling me that LivePatch couldn't be enabled. Edit It appears to have worked the second time I tried to enable it. Here's my status now: $ canonical-livepatch status client-version: "7.29" architecture: x86_64 cpu-model: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz last-check: 2018-03-26T13:25:49.490531157-04:00 boot-time: 2018-03-26T09:18:35-04:00 uptime: 4h7m37s status: - kernel: 4.15.0-12.13-generic running: true livepatch: checkState: checked patchState: nothing-to-apply version: "" fixes: "" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-common 0.96.24.24 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 13:21:36 2018 InstallationDate: Installed on 2017-10-13 (164 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2017-11-24 (121 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/1758980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863261] Re: modinfo prints an error message if modules.builtin.bin is missing
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/379222 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1863261 Title: modinfo prints an error message if modules.builtin.bin is missing Status in initramfs-tools package in Ubuntu: In Progress Status in kmod package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: In Progress Status in kmod source package in Focal: Fix Released Bug description: Running a simple "update-initramfs -u" in a system with kmod version 26+20191223-1ubuntu1 (from focal-proposed) will result into a bunch of: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_FLkEYb/lib/modules/5.4.0-14-generic/modules.builtin.bin' errors. That happens because: modinfo prints an error message if modules.builtin.bin is missing and it was fixed upstream (Debian) in: commit 835d584 Author: Ben Hutchings Date: Sat Jan 18 15:44:32 2020 mkinitramfs: Copy modules.builtin.bin into initramfs modinfo now prints an error message if modules.builtin.bin (created by depmod) is missing. Copy it in early if it's present. Closes: #948257 Signed-off-by: Ben Hutchings and reported in bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863261] Re: modinfo prints an error message if modules.builtin.bin is missing
** Also affects: kmod (Ubuntu) Importance: Undecided Status: New ** Changed in: kmod (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1863261 Title: modinfo prints an error message if modules.builtin.bin is missing Status in initramfs-tools package in Ubuntu: In Progress Status in kmod package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: In Progress Status in kmod source package in Focal: Fix Released Bug description: Running a simple "update-initramfs -u" in a system with kmod version 26+20191223-1ubuntu1 (from focal-proposed) will result into a bunch of: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_FLkEYb/lib/modules/5.4.0-14-generic/modules.builtin.bin' errors. That happens because: modinfo prints an error message if modules.builtin.bin is missing and it was fixed upstream (Debian) in: commit 835d584 Author: Ben Hutchings Date: Sat Jan 18 15:44:32 2020 mkinitramfs: Copy modules.builtin.bin into initramfs modinfo now prints an error message if modules.builtin.bin (created by depmod) is missing. Copy it in early if it's present. Closes: #948257 Signed-off-by: Ben Hutchings and reported in bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863261] [NEW] modinfo prints an error message if modules.builtin.bin is missing
Public bug reported: Running a simple "update-initramfs -u" in a system with kmod version 26+20191223-1ubuntu1 (from focal-proposed) will result into a bunch of: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_FLkEYb/lib/modules/5.4.0-14-generic/modules.builtin.bin' errors. That happens because: modinfo prints an error message if modules.builtin.bin is missing and it was fixed upstream (Debian) in: commit 835d584 Author: Ben Hutchings Date: Sat Jan 18 15:44:32 2020 mkinitramfs: Copy modules.builtin.bin into initramfs modinfo now prints an error message if modules.builtin.bin (created by depmod) is missing. Copy it in early if it's present. Closes: #948257 Signed-off-by: Ben Hutchings and reported in bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257 ** Affects: initramfs-tools (Ubuntu) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: In Progress ** Affects: initramfs-tools (Ubuntu Focal) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: In Progress ** Changed in: initramfs-tools (Ubuntu) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Also affects: initramfs-tools (Ubuntu Focal) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1863261 Title: modinfo prints an error message if modules.builtin.bin is missing Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Focal: In Progress Bug description: Running a simple "update-initramfs -u" in a system with kmod version 26+20191223-1ubuntu1 (from focal-proposed) will result into a bunch of: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_FLkEYb/lib/modules/5.4.0-14-generic/modules.builtin.bin' errors. That happens because: modinfo prints an error message if modules.builtin.bin is missing and it was fixed upstream (Debian) in: commit 835d584 Author: Ben Hutchings Date: Sat Jan 18 15:44:32 2020 mkinitramfs: Copy modules.builtin.bin into initramfs modinfo now prints an error message if modules.builtin.bin (created by depmod) is missing. Copy it in early if it's present. Closes: #948257 Signed-off-by: Ben Hutchings and reported in bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)
dualshock3nerd's solution also works for me too! Thanks!!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1585084 Title: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843099] Re: Unattended upgrades maybe very slow and time out on shutdown
** Changed in: unattended-upgrades (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1843099 Title: Unattended upgrades maybe very slow and time out on shutdown Status in unattended-upgrades package in Ubuntu: Invalid Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu * Ubuntu Xenial 16.04.6 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center * 1.1ubuntu1.18.04.7~16.04.3 3) What you expected to happen * Packages to be upgraded on reboot / shutdown. 4) What happened instead * The host just rebooted. Didn't perform upgrades. No useful output either until I enabled debug logging in the systemd unit file. I'm reporting a new bug but this is very similar to #1806487 and I'm actually wondering if it resurfaced somehow. We're running Ubuntu Xenial 16.04.6 which has 1.1ubuntu1.18.04.7~16.04.3 installed. I see that #1806487 was resolved with 1.1ubuntu1.18.04.7~16.04.2. However I'm seeing similar behavior. So far I've modified systemd to see if anything stands out. I do have an strace and then just debug mode. Unless needed, simply put, this is what a reboot with debug logging looks like (i.e. unattended-upgrades-shutdown.log): 2019-09-06 09:20:04,871 DEBUG - Waiting for signal to start operation 2019-09-06 09:20:43,996 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2019-09-06 09:20:43,996 DEBUG - Starting countdown of 25.0 minutes 2019-09-06 09:20:43,997 DEBUG - get_lock returned 7 2019-09-06 09:20:43,997 DEBUG - lock not taken I hope that helps, please let me know if you need anything else from me or if I can provide any more information. I've done this many times before, this is the first time it hasn't worked. When I patched around the end of May, all went well. My other variants worked, well mainly Trusty but that's EOL for public access. Bionic doesn't seem to have anything it needs to update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1843099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840375] Re: groupdel doesn't support extrausers
** Description changed:
snapd needs the ability to call 'groupdel --extrausers foo' to clean up
after itself, but --extrausers is currently unsupported.
[Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
1. install the libnss-extrausers and configure it (see
/usr/share/doc/libnss-extrausers/README for the modifications in sswitch.conf)
- 2. run "groupadd --extrausers foo"
+ 2. run "groupadd --extrausers foo" and verify "grep foo
/var/lib/extrausers/group"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
* low: this adds a new (optional) option which is off by default
** Description changed:
snapd needs the ability to call 'groupdel --extrausers foo' to clean up
after itself, but --extrausers is currently unsupported.
[Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
- 1. install the libnss-extrausers and configure it (see
/usr/share/doc/libnss-extrausers/README for the modifications in sswitch.conf)
+ 1. install the libnss-extrausers and add "extrauers" to the passwd and shadow
line (see /usr/share/doc/libnss-extrausers/README for the modifications in
sswitch.conf)
2. run "groupadd --extrausers foo" and verify "grep foo
/var/lib/extrausers/group"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
* low: this adds a new (optional) option which is off by default
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375
Title:
groupdel doesn't support extrausers
Status in snapd:
Triaged
Status in shadow package in Ubuntu:
Fix Released
Status in shadow source package in Xenial:
Fix Committed
Status in shadow source package in Bionic:
Fix Committed
Status in shadow source package in Disco:
Fix Committed
Bug description:
snapd needs the ability to call 'groupdel --extrausers foo' to clean
up after itself, but --extrausers is currently unsupported.
[Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
1. install the libnss-extrausers and add "extrauers" to the passwd and shadow
line (see /usr/share/doc/libnss-extrausers/README for the modifications in
sswitch.conf)
2. run "groupadd --extrausers foo" and verify "grep foo
/var/lib/extrausers/group"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
* low: this adds a new (optional) option which is off by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806076] Re: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii
** Changed in: unattended-upgrades (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1806076 Title: unattended-upgrade --help raises UnicodeEncodeError when stdout encoding is ascii Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Won't Fix Status in apt source package in Xenial: New Status in unattended-upgrades source package in Xenial: New Status in apt source package in Bionic: New Status in unattended-upgrades source package in Bionic: New Bug description: [Test Case] rbalint@yogi:~$ lxc launch ubuntu:18.04 bb-lp-1806076 Creating bb-lp-1806076 Starting bb-lp-1806076 rbalint@yogi:~$ lxc shell bb-lp-1806076 mesg: ttyname failed: No such device root@bb-lp-1806076:~# apt install -yqq language-pack-ru-base The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following additional packages will be installed: language-pack-ru The following NEW packages will be installed: language-pack-ru language-pack-ru-base 0 upgraded, 2 newly installed, 0 to remove and 7 not upgraded. Need to get 2310 kB of archives. After this operation, 11.8 MB of additional disk space will be used. Selecting previously unselected package language-pack-ru-base. (Reading database ... 28536 files and directories currently installed.) Preparing to unpack .../language-pack-ru-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru-base (1:18.04+20180712) ... Selecting previously unselected package language-pack-ru. Preparing to unpack .../language-pack-ru_1%3a18.04+20180712_all.deb ... Unpacking language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru (1:18.04+20180712) ... Setting up language-pack-ru-base (1:18.04+20180712) ... Generating locales (this might take a while)... ru_RU.UTF-8... done ru_UA.UTF-8... done Generation complete. root@bb-lp-1806076:~# env LANG=ru_RU unattended-upgrade --help | cat Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1983, in (options, args) = parser.parse_args() # type: ignore File "/usr/lib/python3.6/optparse.py", line 1387, in parse_args stop = self._process_args(largs, rargs, values) File "/usr/lib/python3.6/optparse.py", line 1427, in _process_args self._process_long_opt(rargs, values) File "/usr/lib/python3.6/optparse.py", line 1501, in _process_long_opt option.process(opt, value, values, self) File "/usr/lib/python3.6/optparse.py", line 785, in process self.action, self.dest, opt, value, values, parser) File "/usr/lib/python3.6/optparse.py", line 807, in take_action parser.print_help() File "/usr/lib/python3.6/optparse.py", line 1647, in print_help file.write(self.format_help()) UnicodeEncodeError: 'ascii' codec can't encode characters in position 126-133: ordinal not in range(128) root@bb-lp-1806076:~# env LANG=ru_RU.UTF-8 unattended-upgrade --help | cat Usage: unattended-upgrade [options] Options: -h, --helpshow this help message and exit -d, --debug print debug messages --apt-debug make apt/libapt print verbose debug messages -v, --verbose print info messages --dry-run Simulation, download but do not install --download-only Only download, do not even try to install. --minimal-upgrade-steps Upgrade in minimal steps (and allow interrupting with SIGTERM [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.6, the problem page at https://errors.ubuntu.com/problem/b3e3265e302351558260f54ae37c7b4c193dfc95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Also seen in: * https://errors.ubuntu.com/problem/936bb1c75c4efe018f968a5773b820bcf52c298a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1806076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
** Changed in: mysql-ocaml (Ubuntu) Status: New => In Progress ** Changed in: mysqltcl (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
** Also affects: isc-kea (Ubuntu) Importance: Undecided Status: New ** Changed in: isc-kea (Ubuntu) Status: New => In Progress ** Changed in: lyricue (Ubuntu) Status: New => In Progress ** Changed in: motion (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
The version in focal-proposed works well, thanks Christian! I hadn't anticipated the additional roadblocks so I really appreciate you pushing it forward nevertheless! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: Triaged Status in rsyslog source package in Disco: Triaged Status in rsyslog source package in Eoan: Triaged Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
** Package changed: ubuntu => systemd (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: New Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863228] [NEW] loginctl list-sessions shows ghost sessions that are never completely closed
You have been subscribed to a public bug: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re-logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- loginctl list-sessions shows ghost sessions that are never completely closed https://bugs.launchpad.net/bugs/1863228 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Edwin, Do you happen to notice any IPv6 or LLDP or other link-local traffic on the interfaces? (including backup interface). The MTR loss % is purely a capture of their packets xmitted and responses received, so for that UDP MTR test, this is saying that UDP packets were lost, somewhere. The NIC does not have any drops showing via ethtool -S stats but I'm hunting down which are the right pair of before/afters. Other than the tpa_abort counts, there were no errors that I saw. I can't tell what the tpa_abort means for the frame - is it purely a failure only to coalesce, or does it end up dropping packets at some point in that functionality? I'm assuming not, as whatever the reason, those would be counted as drops, I hope, and printed in the interface stats. I'll attach all the stats here once I get them sorted out, I thought I had a clean diff of before and after from the tester, but after looking through, I don't think the file I have is from before/after the mtr test, as there was negligible UDP traffic. I'll try and get clarification from the reporter. Note that when the provision of primary= is used to configure which interface is primary, and when the primary port is used as the active interface for the bond, no problems are seen (and that works deterministically to set the correct active interface). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error.
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
@ltrager I'd be happy to handle the patch for util-linux on Ubuntu E/F if that helps; just let me know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: New Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863186] Re: package sdl2-dev depends on outdated version of libpulse-dev
Please note that libsdl2-dev has an unversioned dependency on libpulse- dev. There seems to be a local version mismatch between the libpulse packages: “libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is installed”. Did you have the bionic-proposed repository enabled at some point but don't have it anymore? I think if you enabled the proposed updates then you might be able to install libpulse-dev again. ** Package changed: libsdl2 (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1863186 Title: package sdl2-dev depends on outdated version of libpulse-dev Status in pulseaudio package in Ubuntu: Incomplete Bug description: $ sudo apt install libsdl2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsdl2-dev : Depends: libpulse-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo aptitude install libsdl2-dev The following NEW packages will be installed: The following packages have unmet dependencies: libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is installed Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1863186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863186] [NEW] package sdl2-dev depends on outdated version of libpulse-dev
You have been subscribed to a public bug: $ sudo apt install libsdl2-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsdl2-dev : Depends: libpulse-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. $ sudo aptitude install libsdl2-dev The following NEW packages will be installed: The following packages have unmet dependencies: libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is installed Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is installed ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Incomplete -- package sdl2-dev depends on outdated version of libpulse-dev https://bugs.launchpad.net/bugs/1863186 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863189] Re: package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.
** Changed in: util-linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1863189 Title: package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in util-linux package in Ubuntu: Incomplete Bug description: I can't update my packages by using sudo apt-get update, because it fails to download some repositories. (Atingido:1 http://security.ubuntu.com/ubuntu eoan-security InRelease Atingido:2 http://br.archive.ubuntu.com/ubuntu eoan InRelease Obter:3 http://br.archive.ubuntu.com/ubuntu eoan-updates InRelease [97,5 kB] Obter:4 http://br.archive.ubuntu.com/ubuntu eoan-backports InRelease [88,8 kB] Obter:5 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages [210 kB] Obter:6 http://br.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages [167 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Ign:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata Ign:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons Ign:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons Ign:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata Ign:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons Ign:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons Ign:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Err:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 2801:82:80ff:8000::5 80] Hashes of expected file: - Filesize:73000 [weak] - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak] - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak] Release file created at: Thu, 13 Feb 2020 22:49:41 + Obter:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons [9.954 B] Err:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons Obter:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons [15,1 kB] Err:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons Obter:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata [26,2 kB] Err:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata Obter:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons [18,5 kB] Err:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons Obter:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons [22,9 kB] Err:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons Obter:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata [8.064 B] Err:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata File has unexpected size (8068 != 8064). Mirror sync in progress? [IP: 200.236.31.4 80] Hashes of expected file: - Filesize:8064 [weak] - SHA256:ec8750e513d95f057f05b2c0269f7c043db0ef78f9d1facca70260870c14440e - SHA1:b3548883a3b75fdf0d92dca2221bb63381fcecd1 [weak] - MD5Sum:835c424e73a6a3f4235535befe47ea27 [weak] Release file created at: Thu, 13 Feb 2020 22:50:01 + Baixados 186 kB em 4s (44,0 kB/s) Lendo listas de pacotes... Pronto E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/Components-amd64.yml.xz File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 2801:82:80ff:8000::5 80] Hashes of expected file: - Filesize:73000 [weak] - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak] - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak] Release file created at: Thu, 13 Feb 2020 22:49:41 + E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-48x48.tar.gz E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-64x64.tar.gz E: Falhou ao buscar
[Touch-packages] [Bug 1863189] Re: package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.
(falo português, se ajudar.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1863189 Title: package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in util-linux package in Ubuntu: Incomplete Bug description: I can't update my packages by using sudo apt-get update, because it fails to download some repositories. (Atingido:1 http://security.ubuntu.com/ubuntu eoan-security InRelease Atingido:2 http://br.archive.ubuntu.com/ubuntu eoan InRelease Obter:3 http://br.archive.ubuntu.com/ubuntu eoan-updates InRelease [97,5 kB] Obter:4 http://br.archive.ubuntu.com/ubuntu eoan-backports InRelease [88,8 kB] Obter:5 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages [210 kB] Obter:6 http://br.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages [167 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Ign:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata Ign:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons Ign:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons Ign:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata Ign:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons Ign:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons Ign:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Err:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 2801:82:80ff:8000::5 80] Hashes of expected file: - Filesize:73000 [weak] - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak] - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak] Release file created at: Thu, 13 Feb 2020 22:49:41 + Obter:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons [9.954 B] Err:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons Obter:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons [15,1 kB] Err:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons Obter:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata [26,2 kB] Err:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata Obter:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons [18,5 kB] Err:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons Obter:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons [22,9 kB] Err:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons Obter:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata [8.064 B] Err:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata File has unexpected size (8068 != 8064). Mirror sync in progress? [IP: 200.236.31.4 80] Hashes of expected file: - Filesize:8064 [weak] - SHA256:ec8750e513d95f057f05b2c0269f7c043db0ef78f9d1facca70260870c14440e - SHA1:b3548883a3b75fdf0d92dca2221bb63381fcecd1 [weak] - MD5Sum:835c424e73a6a3f4235535befe47ea27 [weak] Release file created at: Thu, 13 Feb 2020 22:50:01 + Baixados 186 kB em 4s (44,0 kB/s) Lendo listas de pacotes... Pronto E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/Components-amd64.yml.xz File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 2801:82:80ff:8000::5 80] Hashes of expected file: - Filesize:73000 [weak] - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak] - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak] Release file created at: Thu, 13 Feb 2020 22:49:41 + E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-48x48.tar.gz E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-64x64.tar.gz E: Falhou ao buscar
[Touch-packages] [Bug 1863189] Re: package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.
And if that works, please run sudo apt install -f to try to fix up packages (libblkid1 reported). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1863189 Title: package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in util-linux package in Ubuntu: Incomplete Bug description: I can't update my packages by using sudo apt-get update, because it fails to download some repositories. (Atingido:1 http://security.ubuntu.com/ubuntu eoan-security InRelease Atingido:2 http://br.archive.ubuntu.com/ubuntu eoan InRelease Obter:3 http://br.archive.ubuntu.com/ubuntu eoan-updates InRelease [97,5 kB] Obter:4 http://br.archive.ubuntu.com/ubuntu eoan-backports InRelease [88,8 kB] Obter:5 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages [210 kB] Obter:6 http://br.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages [167 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Ign:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata Ign:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons Ign:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons Ign:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata Ign:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons Ign:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons Ign:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Err:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 2801:82:80ff:8000::5 80] Hashes of expected file: - Filesize:73000 [weak] - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak] - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak] Release file created at: Thu, 13 Feb 2020 22:49:41 + Obter:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons [9.954 B] Err:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons Obter:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons [15,1 kB] Err:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons Obter:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata [26,2 kB] Err:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata Obter:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons [18,5 kB] Err:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons Obter:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons [22,9 kB] Err:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons Obter:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata [8.064 B] Err:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata File has unexpected size (8068 != 8064). Mirror sync in progress? [IP: 200.236.31.4 80] Hashes of expected file: - Filesize:8064 [weak] - SHA256:ec8750e513d95f057f05b2c0269f7c043db0ef78f9d1facca70260870c14440e - SHA1:b3548883a3b75fdf0d92dca2221bb63381fcecd1 [weak] - MD5Sum:835c424e73a6a3f4235535befe47ea27 [weak] Release file created at: Thu, 13 Feb 2020 22:50:01 + Baixados 186 kB em 4s (44,0 kB/s) Lendo listas de pacotes... Pronto E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/Components-amd64.yml.xz File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 2801:82:80ff:8000::5 80] Hashes of expected file: - Filesize:73000 [weak] - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak] - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak] Release file created at: Thu, 13 Feb 2020 22:49:41 + E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-48x48.tar.gz E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-64x64.tar.gz E: Falhou
[Touch-packages] [Bug 1863189] Re: package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.
Can you try sudo apt update again? It looks like a temporary issue in mirrors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1863189 Title: package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in util-linux package in Ubuntu: Incomplete Bug description: I can't update my packages by using sudo apt-get update, because it fails to download some repositories. (Atingido:1 http://security.ubuntu.com/ubuntu eoan-security InRelease Atingido:2 http://br.archive.ubuntu.com/ubuntu eoan InRelease Obter:3 http://br.archive.ubuntu.com/ubuntu eoan-updates InRelease [97,5 kB] Obter:4 http://br.archive.ubuntu.com/ubuntu eoan-backports InRelease [88,8 kB] Obter:5 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages [210 kB] Obter:6 http://br.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages [167 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Ign:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata Ign:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons Ign:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons Ign:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata Ign:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons Ign:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons Ign:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Err:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 2801:82:80ff:8000::5 80] Hashes of expected file: - Filesize:73000 [weak] - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak] - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak] Release file created at: Thu, 13 Feb 2020 22:49:41 + Obter:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons [9.954 B] Err:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons Obter:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons [15,1 kB] Err:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons Obter:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata [26,2 kB] Err:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata Obter:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons [18,5 kB] Err:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons Obter:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons [22,9 kB] Err:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons Obter:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata [8.064 B] Err:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata File has unexpected size (8068 != 8064). Mirror sync in progress? [IP: 200.236.31.4 80] Hashes of expected file: - Filesize:8064 [weak] - SHA256:ec8750e513d95f057f05b2c0269f7c043db0ef78f9d1facca70260870c14440e - SHA1:b3548883a3b75fdf0d92dca2221bb63381fcecd1 [weak] - MD5Sum:835c424e73a6a3f4235535befe47ea27 [weak] Release file created at: Thu, 13 Feb 2020 22:50:01 + Baixados 186 kB em 4s (44,0 kB/s) Lendo listas de pacotes... Pronto E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/Components-amd64.yml.xz File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 2801:82:80ff:8000::5 80] Hashes of expected file: - Filesize:73000 [weak] - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak] - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak] Release file created at: Thu, 13 Feb 2020 22:49:41 + E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-48x48.tar.gz E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-64x64.tar.gz E: Falhou ao buscar
[Touch-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-20.04 ** Changed in: pulseaudio (Ubuntu) Milestone: None => ubuntu-20.04 ** Also affects: libmtp (Ubuntu) Importance: Undecided Status: New ** Changed in: libmtp (Ubuntu) Milestone: None => ubuntu-20.04 ** Changed in: libmtp (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863239] [NEW] /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
Public bug reported: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. ** Affects: pulseaudio (Ubuntu) Importance: High Status: New ** Affects: systemd (Ubuntu) Importance: High Status: New ** Affects: udev (Ubuntu) Importance: High Status: New ** Description changed: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 + till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ + + The printer is the device /dev/bus/usb/001/063: + + till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb + Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. + Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera + Bus 001 Device 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor + Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in pulseaudio package in Ubuntu: New Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device
[Touch-packages] [Bug 1841783] Re: Update to 1.2.0?
** Changed in: speex (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to speex in Ubuntu. https://bugs.launchpad.net/bugs/1841783 Title: Update to 1.2.0? Status in speex package in Ubuntu: Triaged Status in speex package in Debian: New Bug description: The source was split in rc2, Debian didn't follow the change and we are in sync, do we want to update? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speex/+bug/1841783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841783] Re: Update to 1.2.0?
The Debian maintainer has not touched the package since 2014. Maybe Ubuntu should go ahead and update. ** Tags added: focal ** Bug watch added: Debian Bug tracker #949717 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949717 ** Also affects: speex (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949717 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to speex in Ubuntu. https://bugs.launchpad.net/bugs/1841783 Title: Update to 1.2.0? Status in speex package in Ubuntu: Triaged Status in speex package in Debian: Unknown Bug description: The source was split in rc2, Debian didn't follow the change and we are in sync, do we want to update? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speex/+bug/1841783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
Also, I even tried disabling the power saving feature
(i915.enable_psr=0) but it still seems to lock up or hang.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2
[Touch-packages] [Bug 1862865] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328142/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => New
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956]
[Touch-packages] [Bug 1862865] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328141/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on
[Touch-packages] [Bug 1862865] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328140/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for
[Touch-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
| [Fri Feb 14 18:55:37 2020] i915 :00:02.0: GPU HANG: ecode 9:1:0x,
hang on rcs0
| [Fri Feb 14 18:55:37 2020] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
| [Fri Feb 14 18:55:37 2020] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
| [Fri Feb 14 18:55:37 2020] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
| [Fri Feb 14 18:55:37 2020] The GPU crash dump is required to analyze GPU
hangs, so please always attach it.
| [Fri Feb 14 18:55:37 2020] GPU crash dump saved to /sys/class/drm/card0/error
| [Fri Feb 14 18:55:37 2020] i915 :00:02.0: Resetting rcs0 for hang on rcs0
| [Fri Feb 14 18:55:45 2020] i915 :00:02.0: Resetting rcs0 for hang on rcs0
So included saved crash dump from /sys/class/drm/card0/error.
** Attachment added: "/sys/class/drm/card0/error"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1862865/+attachment/5328143/+files/drm-error.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584]
[Touch-packages] [Bug 1862865] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328136/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0:
[Touch-packages] [Bug 1862865] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328138/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
[Touch-packages] [Bug 1862865] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328137/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0
[Touch-packages] [Bug 1862865] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328139/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0
[Touch-packages] [Bug 1862865] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328131/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for
[Touch-packages] [Bug 1862865] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328130/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
[Touch-packages] [Bug 1862865] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328135/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0
[Touch-packages] [Bug 1862865] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328132/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on
[Touch-packages] [Bug 1862865] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328133/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang
[Touch-packages] [Bug 1862865] PciMultimedia.txt
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328134/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
[Touch-packages] [Bug 1862865] Card0.Codecs.codec.2.txt
apport information
** Attachment added: "Card0.Codecs.codec.2.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328129/+files/Card0.Codecs.codec.2.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915
[Touch-packages] [Bug 1862865] Card0.Codecs.codec.0.txt
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328128/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915
[Touch-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
apport information
** Tags added: apport-collected focal
** Description changed:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:15 dharkan kernel: [71070.591932] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:17 dharkan kernel: [71072.575930] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:19 dharkan kernel: [71074.591922] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:21 dharkan kernel: [71076.575911] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:23 dharkan kernel: [71078.591901] i915 :00:02.0: Resetting
[Touch-packages] [Bug 1862865] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1862865/+attachment/5328127/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
This bug was fixed in the package curtin - 19.3-26-g82f23e3d-0ubuntu1 --- curtin (19.3-26-g82f23e3d-0ubuntu1) focal; urgency=medium * New upstream snapshot. - install-grub: refactor uefi partition/disk searching (LP: #1862846) - doc: update Canonical contributors URL [Paul Tobias] - block-discover: detect additional "extended" partition types in MBR (LP: #1861251) - vmtests: skip focal bcache tests due to kernel bug - net/deps.py: detect openvswitch cfg and install openvswitch packages - vmtest: collection of vmtest related fixes to make things triple green - clear-holders: umap the parent mpath to wipe the underlying partitions - vmtests: bump fixby date out and fix false positive when date passes (LP: #1855148) - vmtests: drop disco tests using a tool to automate the process -- Ryan Harper Thu, 13 Feb 2020 21:08:59 -0600 ** Changed in: curtin (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: New Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862437] Re: Ubuntu 16.10 & later, & derivatives do not query the assigned DNS server
We can see in your logs (thanks for all your effort BTW) that the failing cases
are exactly those which have:
...
Server: 127.0.0.53
Address: 127.0.0.53#53
...
That represents the switch to systemd-resolved.
It might be worth to check (and if you want report) your output of:
$ systemd-resolve --status
I guess we can already switch this bug from bind9 to systemd, or at
least add it.
Now one weakness of systemd-resolved that I've seen in several other bug
reports is that - IIRC- if you have multiple DNS servers it does "the first
wins".
So if you happen to have multiple DNS servers pushed via dhcp or other places
what could happen is that one answers "SERVFAIL" before the other one could
reply with a valid answer.
Is your setup using such a multi-dns scenario?
Info:
- There were some fixes in NM for that (bug 1624317) but I'm not sure if there
aren't ways to still hit this.
- There are many, but one related upstream issue (for some context) is
https://github.com/systemd/systemd/issues/6076
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/systemd/systemd/issues #6076
https://github.com/systemd/systemd/issues/6076
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1862437
Title:
Ubuntu 16.10 & later, & derivatives do not query the assigned DNS
server
Status in bind9 package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
Starting Ubuntu 16.10 resolution of LAN addresses fails. This name
resolution failure is evident in every post 16.0 Ubuntu & derivative
that I have tested. See below - which shows 16.04 resolves, 18.04
and Pop!_OS 19.04 fail, and other distros - Fedora 31, openSUSE Leap
15.1, and Debian GNU/Linux 10 (buster) - all resolve as expected.
== Test Case ==
$ name=$(hostnamectl | grep "Static hostname:" | cut -d: -f2 | xargs)
$ echo "${name}"
$ hostnamectl | grep System
$ hostnamectl | grep Kernel
$ nmcli dev show | grep DNS
$ nslookup "${name}"
== Additional Information ==
Operating System: Ubuntu 16.04.6 LTS
Kernel: Linux 4.4.0-170-generic
IP4.DNS[1]: 192.168.3.2
Server:127.0.1.1
Address: 127.0.1.1#53
Name: BGOWIKI01v
Address: 192.168.3.60
Operating System: Ubuntu 18.04.3 LTS
Kernel: Linux 4.15.0-72-generic
IP4.DNS[1]: 192.168.3.2
Server:127.0.0.53
Address: 127.0.0.53#53
** server can't find BGOWIKI01v: SERVFAIL
Operating System: Pop!_OS 19.04
Kernel: Linux 5.0.0-21-generic
IP4.DNS[1]: 192.168.3.2
Server:127.0.0.53
Address: 127.0.0.53#53
** server can't find BGOWIKI01v: SERVFAIL
Operating System: Fedora 31 (Workstation Edition)
Kernel: Linux 5.3.7-301.fc31.x86_64
IP4.DNS[1]: 192.168.3.2
Server:192.168.3.2
Address: 192.168.3.2#53
Name: BGOWIKI01v
Address: 192.168.3.60
Operating System: openSUSE Leap 15.1
Kernel: Linux 4.12.14-lp151.28.36-default
IP4.DNS[1]: 192.168.3.2
Server:192.168.3.2
Address: 192.168.3.2#53
Name: BGOWIKI01v
Address: 192.168.3.60
Operating System: Debian GNU/Linux 10 (buster)
Kernel: Linux 4.19.0-6-amd64
IP4.DNS[1]: 192.168.3.2
Server:192.168.3.2
Address: 192.168.3.2#53
Name: BGOWIKI01v
Address: 192.168.3.60
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsutils 1:9.11.3+dfsg-1ubuntu1.11
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: MATE
Date: Sat Feb 8 17:36:28 2020
InstallationDate: Installed on 2019-12-22 (47 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1862437/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
