I also hit this again in focal on 2020-06-25, with an update to systemd
245.4-4ubuntu3.1; I had previously updated dbus to 1.12.16-2ubuntu2.1 on
2020-06-17 without event. It's still an issue at least with updates to
systemd in focal.
Similar messages end up in the journal:
Jun 25 13:04:55 kryten dbus-daemon[1541]: Unknown group "power" in message bus
configuration file
Jun 25 13:04:55 kryten dbus-daemon[1541]: [system] Reloaded configuration
Jun 25 13:04:55 kryten dbus-daemon[1541]: Unknown group "power" in message bus
configuration file
Jun 25 13:04:55 kryten dbus-daemon[1541]: [system] Reloaded configuration
Jun 25 13:05:09 kryten dbus-daemon[1541]: Unknown group "power" in message bus
configuration file
Jun 25 13:05:09 kryten dbus-daemon[1541]: [system] Reloaded configuration
Jun 25 13:05:09 kryten dbus-daemon[1541]: Unknown group "power" in message bus
configuration file
Jun 25 13:05:09 kryten dbus-daemon[1541]: [system] Reloaded configuration
Jun 25 13:05:09 kryten dbus-daemon[1541]: Unknown group "power" in message bus
configuration file
Jun 25 13:05:09 kryten dbus-daemon[1541]: [system] Reloaded configuration
Jun 25 13:05:09 kryten dbus-daemon[1541]: Unknown group "power" in message bus
configuration file
Jun 25 13:05:09 kryten dbus-daemon[1541]: [system] Reloaded configuration
Jun 25 13:05:09 kryten dbus-daemon[1541]: Unknown group "power" in message bus
configuration file
Jun 25 13:05:09 kryten dbus-daemon[1541]: [system] Reloaded configuration
Jun 25 13:05:10 kryten dbus-daemon[1541]: Unknown group "power" in message bus
configuration file
Jun 25 13:05:10 kryten dbus-daemon[1541]: [system] Reloaded configuration
Jun 25 13:05:10 kryten dbus-daemon[1541]: Unknown group "power" in message bus
configuration file
Jun 25 13:05:10 kryten dbus-daemon[1541]: [system] Reloaded configuration
Jun 25 13:05:10 kryten dbus-daemon[1541]: Unknown group "power" in message bus
configuration file
Jun 25 13:05:10 kryten systemd[1]: Reloading.
Jun 25 13:05:11 kryten 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/dbus/system_bus_socket; please update
the unit file accordingly.
Jun 25 13:05:11 kryten systemd[1]: /lib/systemd/system/fancontrol.service:11:
PIDFile= references a path below legacy directory /var/run/, updating
/var/run/fancontrol.pid → /run/fancontrol.pid; please update the unit file
accordingly.
Jun 25 13:05:36 kryten systemd[1]: We couldn't coldplug
machine-qemu\x2d1\x2dkeybase\x2dbionic\x2damd64.scope, proceeding anyway:
Connection timed out
Jun 25 13:05:36 kryten dbus-daemon[1541]: [system] Reloaded configuration
Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=rtkit-daemon comm="systemd" exe="/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=switcheroo-control comm="systemd"
exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=polkit comm="systemd" exe="/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=colord comm="systemd" exe="/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Jun 25 13:05:36 kryten systemd[1]: NetworkManager.service: Unexpected error
response from GetNameOwner(): Connection terminated
Jun 25 13:05:36 kryten ModemManager[1689]: <info> Caught signal, shutting
down...
Jun 25 13:05:36 kryten thermald[1605]: [WARN]Terminating ...
Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=upower comm="systemd" exe="/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Jun 25 13:05:36 kryten audit[1541]: USER_AVC pid=1541 uid=105 auid=4294967295
ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system"
path="/org/freedesktop/NetworkManager"
interface="org.freedesktop.NetworkManager" member="CheckPermissions"
name=":1.9" mask="receive" pid=4082 label="bitlbee" pe>
exe="/usr/bin/dbus-daemon" sauid=105
hostname=? addr=? terminal=?'
Jun 25 13:05:36 kryten audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=accounts-daemon comm="systemd"
exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 25 13:05:36 kryten systemd[1]: udisks2.service: Unexpected error response
from GetNameOwner(): Connection terminated
Jun 25 13:05:36 kryten bluetoothd[1536]: Terminating
Jun 25 13:05:36 kryten systemd[1]: switcheroo-control.service: Unexpected error
response from GetNameOwner(): Connection terminated
Jun 25 13:05:36 kryten avahi-daemon[1535]: Got SIGTERM, quitting.
Jun 25 13:05:36 kryten systemd[1]: accounts-daemon.service: Unexpected error
response from GetNameOwner(): Connection terminated
Jun 25 13:05:36 kryten wpa_supplicant[1612]: nl80211: deinit
ifname=p2p-dev-wlp4s0 disabled_11b_rates=0
** Changed in: dbus (Ubuntu)
Status: Expired => Confirmed
** Changed in: dbus (Ubuntu Focal)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services down including gdm
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
