update-manager fails to run (could be dbus?)

Bug #81802 reported by dr. gonzo
8
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
High
Michael Vogt

Bug Description

Binary package hint: update-manager

DISTRIBUTION VERSION/ARCH: Feisty on AMD64

PACKAGE VERSIONS:

update-manager : 0.53.3
dbus : 1.0.2-1ubuntu2

HOW TO REPRODUCE:

1. Go to System > Control Center > Update Manager
=> Nothing happens

2. Open console start update-manager =>
------------------------console output [start]--------------------------------
$ update-manager
Traceback (most recent call last):
  File "/usr/bin/update-manager", line 86, in <module>
    app = UpdateManager(data_dir)
  File "/usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py", line 300, in __init__
    self.setupDbus()
  File "/usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py", line 440, in setupDbus
    '/org/freedesktop/UpdateManagerObject')
  File "/var/lib/python-support/python2.5/dbus/_dbus.py", line 412, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 232, in __init__
    _dbus_bindings.UInt32(0))
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 171, in __call__
    reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UpdateManager was not provided by any .service files
--------------------------console output [end]------------------------------------

3. As root (or with sudo) update-manager _runs_ with this output to the console:
--------------------------console output [start]----------------------------------
# update-manager
warning: could not initiate dbus
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.

(synaptic:6087): libglade-WARNING **: Error loading image: Failed to open file '/usr/share/synaptic/glade/system-upgrade': No such file or directory

(synaptic:6087): libglade-WARNING **: could not convert string to type `GdkPixbuf' for property `pixbuf'

(synaptic:6087): libglade-WARNING **: Couldn't find image file: system-upgrade
current dist not found in meta-release file
------------------------------console output [end]--------------------------------------

DISCUSSION:

It seems that there is either something with the update-manager or dbus.
There is a mention of a missing dbus .service file for org.freedesktop.UpdateManager could that be the problem?

Revision history for this message
chantra (chantra) wrote :

I can reproduce this bug on my feisty box:
* as normal user: update-manager crashes
* using sudo update-manager works

Changed in update-manager:
status: Unconfirmed → Confirmed
Revision history for this message
Gerhard Zlabinger (gerhard-zlabinger) wrote :

I can confirm this as well. Running as user crashes, running as root it gives a "warning: could not initiate dbus", but then seems to work fine.

Revision history for this message
UBfusion (ubfusion) wrote :

All the past 10 daily builds of feisty amd64 desktop (in vmware) sufffer from both bugs and posted workarounds do not work for me. Today's crash report (20070128) follows:

~$ sudo update-manager
Password:
warning: could not initiate dbus
Unhandled exception in thread started by <bound method MetaRelease.download of <MetaRelease object (UpdateManager+MetaRelease+MetaRelease) at 0xf0a820>>
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/UpdateManager/MetaRelease.py", line 168, in download
    os.unlink(self.METARELEASE_FILE)
OSError: [Errno 2] No such file or directory: '/home/mits05/.update-manager/meta-release'

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

Thanks for your bugreport.

This should be fixed with the uplaod of 0.53.5. Please reopen if that does not fix the issue for you.

Cheers,
 MIchael

Changed in update-manager:
assignee: nobody → mvo
importance: Undecided → High
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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