Description of problem: On reboot we are seeing: Jun 07 18:22:45 gdm[3311]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: GDBus.Error:org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus is shutting down. Jun 07 18:22:45 systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE Jun 07 18:22:45 systemd[1]: gdm.service: Failed with result 'exit-code'. Jun 07 18:22:45 systemd[1]: gdm.service: Triggering OnFailure= dependencies. Version-Release number of selected component (if applicable): gdm-40.0-27.el8.x86_64 How reproducible: Very frequently/all the time Expected results: No systemd unit failures Additional info: I don't think we are seeing this on current Fedora machines I know this seem nit-picky - but it clutters up tracking of service status on machines.
I think it just needs this fix: https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/156
So we actually already ship that patch in the build you're using. I'm not reproducing here, either. Can you set Enable=true in the [debug] of /etc/gdm/custom.conf, reboot, reproduce by rebooting again, and then attach the full, unfiltered output of journalctl -b -1 So we can see the shutdown messages from the reproducing reboot ?