[Bug 521407] Re: dbus does not start after reboot

[Ubuntu QA's Bug Bot]

The attachment "dbus.conf.patch" of this bug report has been identified
as being a patch.  The ubuntu-reviewers team has been subscribed to the
bug report so that they can review the patch.  In the event that this is
in fact not a patch you can resolve this situation by removing the tag
'patch' from the bug report and editing the attachment so that it is not
flagged as a patch.  Additionally, if you are member of the ubuntu-
sponsors please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by
Brian Murray.  Please contact him regarding any issues with the action
taken in this bug report.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/521407

Title:
  dbus does not start after reboot

Status in “dbus” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: dbus

  I recently upgraded one Ubuntu box from Gutsy or Hardy to Jaunty.
  DBus no longer starts at boot.  This has two major symptoms:

  * The avahi daemon no longer starts, hence it's not possible to SSH in using a ".local" hostname (bug 519917).
  * GDM starts,  but the X server doesn't respond to keyboard or mouse input.  Ctrl+Alt+F1 to log in at the console also doesn't do anything.

  My workaround so far is to SSH in from another computer (using a
  fully-qualified hostname or IP address) and execute "/etc/init.d/dbus
  start ; /etc/init.d/gdm restart".  That sequence runs fine and solves
  the issues,  until reboot.

  # apt-cache policy dbus
  dbus:
    Instalados: 1.2.12-0ubuntu2.1
    Candidato: 1.2.12-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/521407/+subscriptions