Feisty: can't use dist-upgrader

Bug #103911 reported by cionci
16
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: update-manager

# sudo update-manager
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.

The last lines ("could not...") appear every time I click on the button that checks updates.
Ubuntu Feisty updated from Edgy.

update-manager 0.59.15

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

This message should be harmless.

Changed in update-manager:
importance: Undecided → Low
status: Unconfirmed → Confirmed
Revision history for this message
Ouroboros (francesca8810) wrote :

For the same error I can't update Edgy to Feisty

Revision history for this message
Michael Vogt (mvo) wrote :

@Ouroboros: what version of update-manager do you run? if you run 0.45.3, please upgrade to 0.45.4 or downgrade to 0.45.2

Revision history for this message
Ouroboros (francesca8810) wrote :

I downgraded and it's all ok...

Tnks

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

With package version 1:0.66 I'm getting:

could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/gnome-power-manager exited with status 0

Revision history for this message
Tyler Rick (tyler.rick) wrote :

I'm getting this error message too.

> gksudo "update-manager -d"
warning: could not initiate dbus
current dist not found in meta-release file

Synaptic says that I have update-manager version 0.59.23

Revision history for this message
Sebastian Heinlein (glatzor) wrote :

Please start update-manager without sudo or gksu. There is no dbus server running for the root user.

Changed in update-manager:
status: Confirmed → Invalid
Revision history for this message
Will Newton (will-newton) wrote :

The bug I reported, 127263, is clearly not a duplicate of this bug. The dbus message is fairly harmless but the meta-release info failure is not. Please see the analysis in 127263. I don't know how to make launchpad un-merge the bug reports unfortunately.

Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

Sorry, I got a bit mixed up, I'll fix the mess I made.

*This bug is for the harmless D-Bus message.
*Bug #127263 is for the dist-upgrader warning.

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

@Sebastian Heinlein:

You can see the dbus message after starting update-manager without sudo. Your press the "check" button, the message is shown in terminal and then you're asked for your password.

I've tested this against package version 1:0.67.

Here's my terminal output after pressing the "check" button and entering my password:

snifer@snifer-laptop:~$ update-manager
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/gnome-power-manager exited with status 0
current dist not found in meta-release file
current dist not found in meta-release file

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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