dbus doesn't create socket after unclean shutdown

Bug #567193 reported by Michael Fritscher
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Lucid by Michael Fritscher

Bug Description

Binary package hint: dbus

after a crash or unclean shutdown, dbus pretends to start, but doesn't create its socket - which causes many faillures, e.g. networkmanager and Xorg (which start into the failsafe-mode, because gdm thinks that it has severe problems - the xorg-logs say only (EE) about the touchscreen, nothing that critical, a manual startx works fine in this situation)
A normal restart using e.g. strg+alt-entf fixes this problem.

I use current Ubuntu 10.4.

summary: - doesn't create socket after unclean shutdown
+ dbus doesn't create socket after unclean shutdown
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dbus (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.