Bug 2213662

Summary:	gdm systemd unit fails on reboot
Product:	Red Hat Enterprise Linux 8	Reporter:	Orion Poplawski <orion>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	ASSIGNED ---	QA Contact:	Michal Odehnal <modehnal>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.8	CC:	hdegoede, rstrode, tpelka
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	rstrode: needinfo? (orion)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Orion Poplawski 2023-06-08 22:56:30 UTC

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.

Comment 1 Ray Strode [halfline] 2023-06-13 13:34:14 UTC

I think it just needs this fix:

https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/156

Comment 4 Ray Strode [halfline] 2023-07-14 14:45:38 UTC

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
?