could not initiate dbus

Bug #123429 reported by Wousser
This bug report is a duplicate of:  Bug #103911: Feisty: can't use dist-upgrader. Edit Remove
4
Affects Status Importance Assigned to Milestone
Software Updater
New
Undecided
Unassigned

Bug Description

$ update-manager
No updates are shown.

$ sudo update-manager
warning: could not initiate dbus
current dist not found in meta-release file

$ sudo update-manager -d
warning: could not initiate dbus
current dist not found in meta-release file
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #103911 and is being marked as such. Please look at the other bug report to see if there is any information missing that you can add or to see if there is a work around. Feel free to continue to report any other bugs you may find.

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

Other bug subscribers

Remote bug watches

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