Bug 1653692

Summary:	Boot stuck, no graphical DM, no TTY
Product:	[Fedora] Fedora	Reporter:	Yann Droneaud <yann>
Component:	dbus	Assignee:	Colin Walters <walters>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	amigadave, gwync, john.j5live, lpoetter, mclasen, rhughes, rstrode, sandmann, tgunders, walters
Target Milestone:	---
Target Release:	---
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:	2018-11-30 14:44:00 UTC	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 Yann Droneaud 2018-11-27 12:16:45 UTC

After latest updates, boot is stuck with the following messages on the console:

[FAILED] Failed to listen on D-Bus System Message Bus Socket.
See 'systemctl status dbus.socket" for details
[DEPEND] Dependency failed for Login Service
[DEPEND] Dependency failed for GNOME Display Manager
[OK] Started Hold until boot process finishes up.

There's no virtual TTY available, so I had to enable systemd debug shell.

journalctl -b reports:

systemd[1]: dbus.socket: Socket service dbus.service not loaded, refusing
systemd[1]: Failed to listen on D-Bus System Message Bus Socket.


systemctl status dbus.socket reports:

dbus.socket - D-Bus System Message Bus Socket
  Loaded: loaded (/usr/lib/systemd/system/dbus.socket; enabled; vendor preset: enabled)
  Active: inactive (dead)
  Listen: /run/dbus/system_bus_socket (Stream)

Comment 1 Tom Gundersen 2018-11-27 12:57:46 UTC

What version of dbus-broker is this?

Comment 2 Yann Droneaud 2018-11-27 13:02:47 UTC

(In reply to Tom Gundersen from comment #1)
> What version of dbus-broker is this?

dbus-broker-16-6.fc30
dbus-daemon-1.12.10-9.fc30
dbus-1.12.10-9.fc30

Comment 3 Yann Droneaud 2018-11-27 13:09:41 UTC

(In reply to Yann Droneaud from comment #2)
> (In reply to Tom Gundersen from comment #1)
> > What version of dbus-broker is this?
> 
> dbus-broker-16-6.fc30

systemctl status dbus-broker reports that:

 dbus-broker.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
   Docs: man:dbus-broker-launch(1)

Comment 4 Yann Droneaud 2018-11-27 13:29:21 UTC

Perhaps it's a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1653371

Comment 5 Yann Droneaud 2018-11-27 13:37:56 UTC

(In reply to Yann Droneaud from comment #4)
> Perhaps it's a duplicate of
> https://bugzilla.redhat.com/show_bug.cgi?id=1653371

But must probably https://bugzilla.redhat.com/show_bug.cgi?id=1653059

Comment 6 Yann Droneaud 2018-11-27 15:05:13 UTC

I've install dbus-broker-16-7.fc30, but doesn't change anything.

According to systemctl status:

dbus.socket is in error
dbus-daemon.service is disabled (with vendor preset enabled)
dbus-broker.service is disabled (with vendor preset disabled)

Comment 7 Yann Droneaud 2018-11-28 15:01:27 UTC

I've upgraded to dbus-broker-16-8.fc30, same behavior, no dbus daemon activated.

Comment 8 Gwyn Ciesla 2018-11-30 14:44:00 UTC


*** This bug has been marked as a duplicate of bug 1653059 ***