Ubuntu
gnome-system-tools package

system dbus not started at boot

Bug #60219 reported by Mikko Virkkilä
4
Affects Status Importance Assigned to Milestone
gnome-system-tools (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

After installing edgy, the computer fails to start x. After starting gdm from the command line and logging in, I get some bug-buddy dialogs about crashing programs and a dialog without a title with the text:

"Internal error

failed to initialize HAL!"

Running `sudo hald --daemon=no --verbose=yes 2>&1 | tee hal.log` (just after booting, before doing anything manually) reveals that hald is exiting after some messages. Will attach log.

Revision history for this message
Mikko Virkkilä (virkkila) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

OK, the system dbus is not started for some reason, investigating in IRC.

Changed in hal:
status: Unconfirmed → Needs Info
Revision history for this message
Martin Pitt (pitti) wrote :

<mvirkkil> ls: /etc/rc2.d/*dbus*: No such file or directory
<mvirkkil> that whole direcotry is empty. rc2, that is

Revision history for this message
Martin Pitt (pitti) wrote :

So, something yet to be determined killed /etc/rc2.d/* symlinks.

Changed in dbus:
importance: Untriaged → Critical
Revision history for this message
Martin Pitt (pitti) wrote :

As discussed in IRC, this was due to a past bug in gnome-system-tools. To fix it for you, the following should suffice:

for i in `grep -l update-rc.d /var/lib/dpkg/info/*.postinst`; do i=`basename $i`; sudo dpkg-reconfigure ${i%.postinst}; done

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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