Don't fail if dbus is not running
Bug #388623 reported by
Michael Biebl
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
packagekit (Ubuntu) |
Fix Released
|
Medium
|
James Westby |
Bug Description
If dbus is not running (e.g. in my karmic chroot environment), I get this nasty error message on each apt operation:
# apt-get update
...
Failed to open connection to "system" message bus: Failed to connect to socket /var/run/
E: Problem executing scripts APT::Update:
E: Sub-process returned an error code
A simple fix is, to check if dbus is running in /etc/apt/
Trivial patch is attached
Related branches
Changed in packagekit (Ubuntu): | |
status: | Triaged → Fix Committed |
To post a comment you must log in.
Hi,
Thanks for the patch, I'll try and include this in the next upload.
Thanks,
James