Ubuntu
dbus package

Can't connect to d-bus after upgrading from Hardy to Lucid

Bug #551672 reported by Free Ekanayaka on 2010-03-30

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	dbus (Ubuntu)	Fix Released	Medium	Martin Pitt
	Lucid	Fix Released	Medium	Martin Pitt

Bug Description

Binary package hint: dbus

After upgrading from hardy to lucid, the old dbus-daemon process is still running and hasn't been replaced by the new one (this will effectively happen after the reboot). However before the system its reboot, any new process that needs to connect to d-bus will fail, because the path of dbus-daemon-launch-helper has changed.

Please include a symbolic link in the dbus package to fix this, like

/usr/lib/dbus-1.0/dbus-daemon-launch-helper -> /lib/dbus-1.0/dbus-daemon-launch-helper

In this way the old dbus-daemon process can still find the dbus-daemon-launch-helper binary.

Related branches

lp://staging/ubuntu/lucid/dbus

Revision history for this message

Free Ekanayaka (free.ekanayaka) wrote on 2010-03-30:

dbus-trace Edit (1.9 KiB, text/plain)

I'm attacching a traceback that shows the failure in more detail.

Changed in dbus (Ubuntu):
assignee:	nobody → Canonical Desktop Team (canonical-desktop-team)

Martin Pitt (pitti) on 2010-03-30

Changed in dbus (Ubuntu Lucid):
status:	New → In Progress
importance:	Undecided → Medium
assignee:	Canonical Desktop Team (canonical-desktop-team) → Martin Pitt (pitti)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2010-03-30:

This bug was fixed in the package dbus - 1.2.16-2ubuntu4

---------------
dbus (1.2.16-2ubuntu4) lucid; urgency=low

  * Add debian/dbus.links: provide a symlink for dbus-daemon-launch-helper's
    old location in /usr, to provide a more stable upgrade from Hardy. This
    can be dropped in Lucid+1. (LP: #551672)
-- Martin Pitt <email address hidden> Tue, 30 Mar 2010 16:28:07 +0200