[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I can't test this reliably (as stated in the SRU description), but at least I can say I haven't seen it in the last 24h :-) I think this is on @gjolly to try to reproduce it in the mentioned azure test environment. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]:
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
FYI triggered again for me due to unattended upgrades. The time in the journal when things go down matches the unpack/configuee/install phase of - accountsservice:amd64 0.6.55-0ubuntu12~20.04.5 - libaccountsservice0:amd64 0.6.55-0ubuntu12~20.04.5 - dbus:amd64 1.12.16-2ubuntu2.1 I - again - had the usual suspect entries: systemd[1]: Starting Daily apt upgrade and clean activities... dbus-daemon[2266]: [system] Reloaded configuration dbus-daemon[2266]: Unknown group "power" in message bus configuration file systemd[1]: Reloading. systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated I didn't see anything in the log we didn't have before, but for completeness I'm attaching journal of the issue and a few hours before it ** Attachment added: "journal entries around the issues happening on unattended-upgrades" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+attachment/5541619/+files/fail-18Nov-6-24-07.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Incomplete Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Incomplete Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27
[Dx-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher
Since so many components are involved a fix/change might have been missed. And since I recently didn't hear anything about this otherwise rather hot bug I was giving focal a try. It turns out that this was indeed improved. Only the user of pkg:ifmail user fdt name "Fidonet" is still visible. All other formerly affected packages are good in Focal. I can't (without digging through history a lot) say what fixed that but I'll update the bug tasks accordingly. Setting Focal fixed and marking Bionic/Xenial as still affected releases. The backport tasks for those packages are incomplete thou as it is unclear which change in which package fixed it for Focal. Note: This is only speaking for the "default config" of Ubuntu Desktop as in 20.04 we know that certain environments will behave differently (e.g. KDE never was affected). ** Also affects: ifmail (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ceph (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: netqmail (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: sddm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ifmail (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ceph (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: netqmail (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: sddm (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: accountsservice (Ubuntu Xenial) ** No longer affects: accountsservice (Ubuntu Bionic) ** Changed in: ceph (Ubuntu Xenial) Status: New => Incomplete ** Changed in: ceph (Ubuntu Bionic) Status: New => Incomplete ** Changed in: ceph (Ubuntu) Status: Triaged => Fix Released ** No longer affects: ifmail (Ubuntu Xenial) ** No longer affects: ifmail (Ubuntu Bionic) ** No longer affects: lightdm (Ubuntu Xenial) ** No longer affects: lightdm (Ubuntu Bionic) ** Changed in: libvirt (Ubuntu) Status: Triaged => Fix Released ** Changed in: libvirt (Ubuntu Xenial) Status: New => Incomplete ** Changed in: libvirt (Ubuntu Bionic) Status: New => Incomplete ** Changed in: netqmail (Ubuntu Xenial) Status: New => Incomplete ** Changed in: netqmail (Ubuntu Bionic) Status: New => Incomplete ** Changed in: netqmail (Ubuntu) Status: Triaged => Fix Released ** No longer affects: sddm (Ubuntu Xenial) ** No longer affects: sddm (Ubuntu Bionic) -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher Status in accountsservice: Unknown Status in SDDM: Fix Released Status in accountsservice package in Ubuntu: Triaged Status in ceph package in Ubuntu: Fix Released Status in ifmail package in Ubuntu: Triaged Status in libvirt package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Triaged Status in netqmail package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Fix Released Status in ceph source package in Xenial: Incomplete Status in libvirt source package in Xenial: Incomplete Status in netqmail source package in Xenial: Incomplete Status in ceph source package in Bionic: Incomplete Status in libvirt source package in Bionic: Incomplete Status in netqmail source package in Bionic: Incomplete Bug description: Users that I have appended to the 'hidden-users' field in /etc/lightdm/users.conf are not actually hidden. They are still listed on the login screen and in Unity's user switching menu. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Fri Sep 23 11:44:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago) mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175 To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
The last two updates went smooth for me, not triggering it. I'm still too afraid to "just update while working" as I did in the past since it could drag things down thou :-/ I was feeling like this could be solved, but reading that Steve is also affected I'm worried that I might just not hit the same race/trigger by accident. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Confirmed Status in gnome-shell source package in Focal: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM,
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
I hit that again today on an upgrade. Network manager didn't come up again. Mai 20 11:04:46 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9491] caught SIGTERM, shutting down normally. Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9504] dhcp4 (enp0s31f6): canceled DHCP transaction Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9504] dhcp4 (enp0s31f6): state changed extended -> done Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9504] device (enp0s31f6): DHCPv4: trying to acquire a new lease within 90 seconds Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9733] dhcp4 (wlp4s0): canceled DHCP transaction Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9812] dhcp4 (wlp4s0): state changed bound -> done Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9813] device (wlp4s0): DHCPv4: trying to acquire a new lease within 90 seconds Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9817] device (p2p-dev-wlp4s0): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed') Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9825] device (strswanbr2-nic): released from master device strswanbr2 Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9829] device (strswanbr1-nic): released from master device strswanbr1 Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9831] device (veth47e5): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0047] device (virbr0-nic): released from master device virbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0050] device (vethcc7405c8): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0069] device (vetha09a9db4): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0077] device (veth754add92): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0094] device (vethc060f004): released from master device virbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0101] device (veth3152ecc9): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0109] device (vethb6dd0569): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1008] device (virbr0): bridge port vnet1 was detached Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1025] manager: NetworkManager state is now CONNECTED_SITE Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1030] device (virbr0): bridge port vnet0 was detached Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1629] exiting (success) Mai 20 11:04:47 Keschdeichel systemd[1]: NetworkManager.service: Succeeded. Mai 20 11:04:48 Keschdeichel nm-openvpn[847263]: SIGTERM[hard,] received, process exiting $ systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2020-05-20 11:04:47 CEST; 15min ago Docs: man:NetworkManager(8) Main PID: 1330 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 38269) Memory: 12.2M CGroup: /system.slice/NetworkManager.service But that still isn't the root cause. And before this plenty of things failed on GetNameOwner() in that sense it is similar to the former occurance. Mai 20 11:03:56 Keschdeichel systemd[1]: Reloading. Mai 20 11:03:56 Keschdeichel systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run> Mai 20 11:04:11 Keschdeichel tracker-store[976018]: OK Mai 20 11:04:11 Keschdeichel systemd[18845]: tracker-store.service: Succeeded. Mai 20 11:04:21 Keschdeichel systemd[1]: We couldn't coldplug machine-qemu\x2d13\x2dfocal.scope, proceeding anyway: Connection timed out Mai 20 11:04:46 Keschdeichel systemd[1]: We couldn't coldplug machine-qemu\x2d11\x2dbionic.scope, proceeding anyway: Connection timed out Mai 20 11:04:46 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Sure @seb128 - I'll let you know if it happens again (as I did a cleaning-reboot now). -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel ModemManager[1308]: Caught signal, shutting down... Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS
[Dx-packages] [Bug 1871538] Re: Gnome Shell crashed on background upgrade of accountsservice
> 1. Look in /var/crash for crash files and if found run: >ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. Again, they all seem to be prior or follow on issues, but they already have IDs in the error tracker. /var/crash/_usr_bin_gnome-clocks.1000.uploaded a615fed4-77d0-11ea-a806-fa163ee63de6 /var/crash/_usr_bin_konversation.1000.uploaded 0e56c64e-7976-11ea-ab51-fa163e983629 /var/crash/_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.uploaded 29cd6100-7976-11ea-a249-fa163e6cac46 They all show up in my personal error-list at: https://errors.ubuntu.com/user/350ea932144813c645983ba6ebba1ab8a271bbbcc08853010a42e92011f8802f77829fce9a7ad953c6c31a499d176f6312a0148c01ef7facaaa87be74566a786 -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: Gnome Shell crashed on background upgrade of accountsservice Status in accountsservice package in Ubuntu: Incomplete Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service:
[Dx-packages] [Bug 1871538] Re: Gnome Shell crashed on background upgrade of accountsservice
> could you add the journalctl log from that session, that might include some hints Sure attached here, you see in the initial report and the later comments the time indexes to look out for. Also FYI for the rtkit issue that you will see in there => bug 1871543 ** Attachment added: "journal-gnome-restarts.log" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+attachment/5349396/+files/journal-gnome-restarts.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: Gnome Shell crashed on background upgrade of accountsservice Status in accountsservice package in Ubuntu: Incomplete Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected
[Dx-packages] [Bug 1871538] Re: Gnome Shell crashed on background upgrade of accountsservice
> Also do you have any gnome-shell/gdm crash collected in /var/crash? No, just these: $ ll /var/crash/*.crash -rw-r- 1 paelzer whoopsie 3589735 Apr 6 08:34 /var/crash/_usr_bin_gnome-clocks.1000.crash -rw-r- 1 paelzer whoopsie 53170176 Apr 8 10:36 /var/crash/_usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 /var/crash/_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: Gnome Shell crashed on background upgrade of accountsservice Status in accountsservice package in Ubuntu: Incomplete Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from
[Dx-packages] [Bug 1871538] Re: Gnome Shell crashed on background upgrade of accountsservice
Another crash just happened: Apr 08 10:28:06 Keschdeichel systemd[1]: Reloading. Apr 08 10:28:06 Keschdeichel systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run> Apr 08 10:28:17 Keschdeichel dbus-daemon[1726352]: [session uid=1000 pid=1726352] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by '> Apr 08 10:28:17 Keschdeichel systemd[10683]: Starting Tracker metadata database store and lookup manager... Apr 08 10:28:17 Keschdeichel dbus-daemon[1726352]: [session uid=1000 pid=1726352] Successfully activated service 'org.freedesktop.Tracker1' Apr 08 10:28:17 Keschdeichel systemd[10683]: Started Tracker metadata database store and lookup manager. Apr 08 10:28:32 Keschdeichel systemd[1]: We couldn't coldplug machine-qemu\x2d4\x2df\x2drtkit.scope, proceeding anyway: Connection timed out Apr 08 10:28:32 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 10:28:32 Keschdeichel avahi-daemon[1726370]: Got SIGTERM, quitting. Apr 08 10:28:32 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 10:28:32 Keschdeichel ModemManager[1727115]: Caught signal, shutting down... Apr 08 10:28:32 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: Gnome Shell crashed on background upgrade of accountsservice Status in accountsservice package in Ubuntu: New Status in dbus package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]:
[Dx-packages] [Bug 1871538] Re: Gnome Shell crashed on background upgrade of accountsservice
Hi Daniel, none of the crashes that I had has the same signature as those that are reported on the dup. Furthermore as I outlined the crashes seem to be secondary issues after soemthing breaks and recycles gnome-shell. I'd ask for re-triage as that doesn't seem to be the same thing to me. ** This bug is no longer a duplicate of bug 1843982 Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: Gnome Shell crashed on background upgrade of accountsservice Status in accountsservice package in Ubuntu: New Status in dbus package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response
[Dx-packages] [Bug 1871538] [NEW] Gnome Shell crashed on background upgrade of accountsservice
Public bug reported: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel ModemManager[1308]: Caught signal, shutting down... Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe78:26c2. Apr 08 06:09:19 Keschdeichel systemd[1]: accounts-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group on interface strswanbr2.IPv4 with address 192.168.2.0. Apr 08 06:09:19 Keschdeichel systemd[1]: gdm.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Apr 08 06:09:19 Keschdeichel
[Dx-packages] [Bug 1826271] Re: virt-manager does not save preferences
Hi, I'm not at all an dconf expert. But after identifying that even base dconf-editor does not let you save things I think we can eliminate virt-manager from the equation. I have added a task to this bug for d-conf to get maintainers of that package to take a look. They might know where to look and after what. ** Also affects: d-conf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1826271 Title: virt-manager does not save preferences Status in d-conf package in Ubuntu: New Status in virt-manager package in Ubuntu: Incomplete Bug description: running Ubuntu 18.04.2 LTS with KDE Plasma 5.12.7 (Qt 5.9.5) after a recent discover software update virt-manager no longer saves preferences. preferences were correctly saved previously (march 2019 and earlier) /usr/bin/virt-manager edit -> preferences -> polling select poll disk i/o select memory stats close window virt-manager displays cpu usage only. on restart preferences have not been saved also, when starting vm's the virtual machine terminal is too small. previously (march 2019 and earlier) the vm terminals would 'remember' the window-size that had been made. something must be 'broken'. can't find virt-manager preferences in any text file to determine if the file is written-to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1826271/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher
Piorities are a bit odd, eventually all packages affected (low prio as they can't do much about it) actually depend on lightdm to resolve it (prio medium) which depends on accountsservive to implement some shell- filter feature (prio high). TL;DR as there was a lot of discussion up to now: - users need a way to be hidden other than "uid is low" - [1] outlines the place/feature we'd need to get back what we had in the past - [2] outlines that this is a regression and should be handled in lightdm/accountsservice and not all indirectly affected packages Note: the updated upstream bug is [3], but since this is still a semi-static list instead of detecting hidden shells as it did in the past it is not perfect for what would be needed. Furthermore nothing happened on this bug for quite some time. And finally due to being a semi-static list it is almost worse than the workaround of echo -e "[User]\nSystemAccount=true" > /var/lib/AccountsService/users/libvirt-qemu Which could at least be a per-package owned drop-in config. Once more I'd ask the Desktop Team to evaluate how this could be solved. At least Towards 20.04 we should get rid of this annoyance for users. Please let me know if: - there is any chance that we get a hidden-shell filtering into accountsservice that will fix all affected packages at once? OR - if this will not happen and affected packages are supposed to each use the drop-in config. Which means a denial of the argument that was made in [2] While I'd appreciate getting the right solution (accountsservice filters) we were stalled for too long to use the workaround solution by waiting for it to resolve. So I hope kicking this (once more) helps to at least get to some solution for the users. [1]: https://bugs.launchpad.net/accountsservice/+bug/857651/comments/73 [2]: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1667113/comments/23 [3]: https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/37 -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher Status in accountsservice: Unknown Status in SDDM: Unknown Status in accountsservice package in Ubuntu: Triaged Status in ceph package in Ubuntu: Triaged Status in ifmail package in Ubuntu: Triaged Status in libvirt package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in netqmail package in Ubuntu: Triaged Status in sddm package in Ubuntu: Fix Released Bug description: Users that I have appended to the 'hidden-users' field in /etc/lightdm/users.conf are not actually hidden. They are still listed on the login screen and in Unity's user switching menu. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Fri Sep 23 11:44:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago) mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175 To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher
The Dup 1667113 had tracked some more affected packages - since all are dupped on this bug here let me add those tasks here so that all component owners are aware. ** Also affects: ceph (Ubuntu) Importance: Undecided Status: New ** Also affects: ifmail (Ubuntu) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Also affects: netqmail (Ubuntu) Importance: Undecided Status: New ** Also affects: sddm (Ubuntu) Importance: Undecided Status: New ** Changed in: sddm (Ubuntu) Status: New => Fix Released ** Bug watch added: github.com/sddm/sddm/issues #816 https://github.com/sddm/sddm/issues/816 ** Also affects: sddm via https://github.com/sddm/sddm/issues/816 Importance: Unknown Status: Unknown ** Changed in: netqmail (Ubuntu) Status: New => Triaged ** Changed in: libvirt (Ubuntu) Status: New => Triaged ** Changed in: ifmail (Ubuntu) Status: New => Triaged ** Changed in: ceph (Ubuntu) Status: New => Triaged ** Changed in: ceph (Ubuntu) Importance: Undecided => Low ** Changed in: ifmail (Ubuntu) Importance: Undecided => Low ** Changed in: libvirt (Ubuntu) Importance: Undecided => Low ** Changed in: lightdm (Ubuntu) Importance: Low => Medium ** Changed in: netqmail (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher Status in accountsservice: Unknown Status in SDDM: Unknown Status in accountsservice package in Ubuntu: Triaged Status in ceph package in Ubuntu: Triaged Status in ifmail package in Ubuntu: Triaged Status in libvirt package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in netqmail package in Ubuntu: Triaged Status in sddm package in Ubuntu: Fix Released Bug description: Users that I have appended to the 'hidden-users' field in /etc/lightdm/users.conf are not actually hidden. They are still listed on the login screen and in Unity's user switching menu. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Fri Sep 23 11:44:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago) mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175 To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)
*** This bug is a duplicate of bug 857651 *** https://bugs.launchpad.net/bugs/857651 ** This bug has been marked a duplicate of bug 857651 Unable to hide users from login screen / user switcher -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1667113 Title: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types) Status in accountsservice package in Ubuntu: Confirmed Status in base-passwd package in Ubuntu: Invalid Status in ceph package in Ubuntu: Won't Fix Status in ifmail package in Ubuntu: Won't Fix Status in libvirt package in Ubuntu: Won't Fix Status in lightdm package in Ubuntu: Confirmed Status in netqmail package in Ubuntu: Won't Fix Status in sddm package in Ubuntu: Fix Released Bug description: "Technical" user libvirt Qemu appears in the list of user in Ligthdm, among the real regular users. It probably shouldn't ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libvirt-bin 2.5.0-3ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Feb 22 22:09:24 2017 InstallationDate: Installed on 2017-02-01 (21 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201) KernLog: SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp