Created attachment 1570504 [details] journalctl log file I've upgraded today 28->29->30 System is up2date. In 30 gnome-keyring-daemon cannot connect to dbus(-broker) after gdm login. However it's started, but chrome and shortcuts from gsd-media-keys do not work. I guess whatever uses gnome-keyring Not sure if the problem is with dbus or with gnome-keyring-daemon. If I open a terminal and: gnome-keyring-daemon -r then all seems to work, although I still get some error for dbus. I'm listing some of the most important part of the log file: May 18 16:36:29 client systemd[11487]: Starting D-Bus User Message Bus... May 18 16:36:29 client systemd[11487]: dbus-broker.service: Failed with result 'protocol'. May 18 16:36:29 client systemd[11487]: Failed to start D-Bus User Message Bus. May 18 16:36:29 client systemd[11487]: Starting D-Bus User Message Bus... May 18 16:36:29 client systemd[11487]: dbus-broker.service: Failed with result 'protocol'. May 18 16:36:29 client systemd[11487]: Failed to start D-Bus User Message Bus. May 18 16:36:29 client systemd[11487]: Starting D-Bus User Message Bus... May 18 16:36:29 client systemd[11487]: dbus-broker.service: Failed with result 'protocol'. May 18 16:36:29 client systemd[11487]: Failed to start D-Bus User Message Bus. May 18 16:36:29 client systemd[11487]: Starting D-Bus User Message Bus... May 18 16:36:29 client systemd[11487]: dbus-broker.service: Failed with result 'protocol'. May 18 16:36:29 client systemd[11487]: Failed to start D-Bus User Message Bus. May 18 16:36:29 client systemd[11487]: Starting D-Bus User Message Bus... May 18 16:36:29 client systemd[11487]: dbus-broker.service: Failed with result 'protocol'. May 18 16:36:29 client systemd[11487]: Failed to start D-Bus User Message Bus. May 18 16:36:29 client systemd[11487]: dbus-broker.service: Start request repeated too quickly. May 18 16:36:29 client systemd[11487]: dbus-broker.service: Failed with result 'protocol'. May 18 16:36:29 client systemd[11487]: Failed to start D-Bus User Message Bus. ay 18 16:36:29 client gnome-keyring-daemon[11514]: Gkm: using old keyring directory: /home/bilias/.gnome2/keyrings May 18 16:36:29 client gnome-keyring-daemon[11514]: Gkm: using old keyring directory: /home/bilias/.gnome2/keyrings May 18 16:36:29 client gnome-keyring-daemon[11514]: couldn't connect to dbus session bus: Could not connect: Connection refused May 18 16:36:29 client gnome-keyring-ssh.desktop[11650]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh May 18 16:36:29 client gnome-keyring-daemon[11514]: couldn't connect to dbus session bus: Could not connect: Connection refused May 18 16:36:29 client gnome-keyring-secrets.desktop[11653]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh May 18 16:36:29 client gnome-keyring-pkcs11.desktop[11652]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh May 18 16:36:50 client gnome-keyring-daemon[11514]: couldn't connect to dbus session bus: Could not connect: Connection refused May 18 16:36:50 client /usr/libexec/gdm-x-session[11525]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh after manual run: May 18 16:37:25 client gnome-keyring-daemon[12289]: Replacing daemon, using directory: /run/user/1000/keyring May 18 16:37:25 client gnome-keyring-daemon[12289]: Gkm: using old keyring directory: /home/bilias/.gnome2/keyrings May 18 16:37:25 client gnome-keyring-daemon[12289]: Gkm: using old keyring directory: /home/bilias/.gnome2/keyrings May 18 16:37:25 client /usr/libexec/gdm-x-session[11525]: dbus-daemon[11572]: [session uid=1000 pid=11572] Successfully activated service 'org.gnome.keyring' May 18 16:37:25 client gnome-keyring-daemon[12289]: couldn't register in session: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client regards, Giannis
Problem solved dbus-broker.service was disabled in --user unit-files systemctl --user enable dbus-daemon.service Don't know if it was disabled by me. I don't believe so because I'm not able to "disable" services in --user I can only "mask" them. This one was "disabled"
(In reply to Kapetanakis Giannis from comment #1) > Problem solved > dbus-broker.service was disabled in --user unit-files > > systemctl --user enable dbus-daemon.service > > Don't know if it was disabled by me. I don't believe so because I'm not able > to "disable" services in --user > I can only "mask" them. > > This one was "disabled" There were several buggy `dbus-broker` rpm-scriptlets during the F30 -> F31 transition, which might have left your system in such state. The current scriptlets should work. I will mark this bug as resolved, but please let me know if this still happens. Thanks a lot for the report! David
Well I'm on 31 now. System has no problem apart those continuous errors in every boot. Feb 23 08:28:30 systemd[1324]: Failed to start D-Bus User Message Bus. Feb 23 08:28:30 systemd[1324]: Failed to start D-Bus User Message Bus. Feb 23 08:28:30 systemd[1324]: Failed to start D-Bus User Message Bus. Feb 23 08:28:30 systemd[1324]: Failed to start D-Bus User Message Bus. Feb 23 08:28:30 systemd[1324]: Failed to start D-Bus User Message Bus. Feb 23 08:28:30 systemd[1324]: Failed to start D-Bus User Message Bus. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Feb 23 08:28:31 dbus-broker-launch[1362]: Activation request for 'org.a11y.atspi.Registry' failed. Don't know which is the correct way for those kind of services # systemctl -a|grep dbus dbus-broker.service loaded active running D-Bus System Message Bus dbus.socket loaded active running D-Bus System Message Bus Socket $ systemctl list-unit-files|grep dbus dbus-broker.service enabled dbus-daemon.service disabled dbus-org.bluez.service enabled dbus-org.freedesktop.hostname1.service static dbus-org.freedesktop.import1.service static dbus-org.freedesktop.locale1.service static dbus-org.freedesktop.login1.service static dbus-org.freedesktop.machine1.service static dbus-org.freedesktop.NetworkManager.service enabled dbus-org.freedesktop.nm-dispatcher.service enabled dbus-org.freedesktop.portable1.service static dbus-org.freedesktop.timedate1.service static dbus.service enabled dbus.socket enabled $ systemctl --user list-unit-files | grep dbus at-spi-dbus-bus.service static dbus-:1.29-org.a11y.atspi.Registry transient dbus-broker.service enabled dbus-daemon.service enabled dbus.service enabled gnome-session-restart-dbus.service static dbus.socket enabled $ systemctl --user -a|grep dbus at-spi-dbus-bus.service loaded active running Accessibility services bus dbus-:1.29-org.a11y.atspi.Registry loaded active running dbus-:1.29-org.a11y.atspi.Registry dbus-daemon.service loaded active running D-Bus User Message Bus gnome-session-restart-dbus.service loaded inactive dead Restart DBus after GNOME Session shutdown dbus\x2d:1.29\x2dorg.a11y.atspi.Registry.slice loaded active active dbus\x2d:1.29\x2dorg.a11y.atspi.Registry.slice dbus.socket loaded active running D-Bus User Message Bus Socket