update-manager crashed in feisty (TypeError: exceptions must be strings, classes, or instances, not type)

Bug #79274 reported by Rikard Nordgren
154
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pyrex (Ubuntu)
Fix Released
High
Michael Vogt
update-manager (Ubuntu)
Fix Released
High
Michael Vogt

Bug Description

Binary package hint: update-manager

I started the upgrade manager after recieving a notification. It crashed.

Revision history for this message
Rikard Nordgren (rikard-nordgren) wrote :
Revision history for this message
Rikard Nordgren (rikard-nordgren) wrote :

It crashes everytime I try to start it. I run amd64 feisty.

Revision history for this message
Damaraland (damaraland) wrote :

I have the same problem

ville palo (vi64pa)
Changed in update-manager:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Charlotte Curtis (c-f-curtis) wrote :

Same here

Revision history for this message
Ryan Stonecipher-Fisher (ryan-stonecipher-fisher) wrote :

Trying to launch update manager from the gnome control center results in a crash. The panel tray icon for appears after running "sudo aptitude update" in a console, however it fails to launch update manager as well.

This machnei was installed using a herd 1 server install CD followed by installing ubuntu-desktop using apt-get in late November.

Revision history for this message
Marco Paulo Martins Sousa (marcomsousa) wrote :

the problem is probably related to the new python2.5

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :

Same problem here.

Why is status only Medium? It seems pretty serious that the software update tool does not work. Perhaps Medium is the default and somebody needs to bump this up to Severe-as-Hell? :-)

Revision history for this message
ville palo (vi64pa) wrote :

Changed importance as critical

Changed in update-manager:
importance: Medium → Critical
Revision history for this message
Nicolas DERIVE (kalon33) wrote :

Same problem. It occurs when launching the new update-manager (0.53.1), for me from the control center and from the console. I confirm the Marco Paulo Martins Sousa's hypothesis that it could came from python, because of the console output it gave me :

nicolas@spiralo-vertigo:~$ update-manager
Introspect error: The name org.freedesktop.UpdateManager was not provided by any .service files
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 443, in setupDbus
    iface.bringToFront()
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 25, in __call__
    ret = self._proxy_method (*args, **keywords)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 102, in __call__
    reply_message = self._connection.send_with_reply_and_block(message, timeout)
  File "dbus_bindings.pyx", line 455, in dbus_bindings.Connection.send_with_reply_and_block
TypeError: exceptions must be strings, classes, or instances, not type

I saw the same kind of problem (which is ever reported) with cohoba-applet.

Revision history for this message
Håkan Hagman (hhagman) wrote :

Same problem

Revision history for this message
tokj (tokj-deactivatedaccount) wrote :

*** Marked bug #78871 as duplicate of this ***

Revision history for this message
Julien Lavergne (gilir) wrote :

Same problem here, and I have the same message when I launch gnome-app-install (https://bugs.launchpad.net/ubuntu/+source/gnome-app-install/+bug/79154)

I'm pretty sure it's python2.5. Reassigne to python ?

Revision history for this message
Julien Lavergne (gilir) wrote :

Hmm maybe not, update-manager seems ok with sudo. It's work but there is another message :
warning: could not initiate dbus
current dist not found in meta-release file

Thanks qxov for the idea.

Revision history for this message
Julien Lavergne (gilir) wrote :

From bug 79076
"
Re: Update-manager crash from Marco Paulo Martins Sousa at 2007-01-13 16:13:53 CET

This isn't a duplicate because broken packages can't crash the update-manager

But the origin of this problem is here:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/78929
"

Sorry for spam, trying to regroup bugs/comments reports

Revision history for this message
Bryce Harrington (bryce) wrote :

I am experiencing this same problem; running it through Gnome Control Center leads to a crash similar to what's been reported. However, running it from the commandline via `sudo update-manager` works without issue, except for the following warnings printed on the console:

warning: could not initiate dbus
current dist not found in meta-release file

Revision history for this message
miked (miked11) wrote : Re: update-manager crashed in feisty herd2

i386 alternative install cd also
there was python updates in the 18 updates downloaded today, but same problem.

Revision history for this message
Michael Vogt (mvo) wrote : Re: update-manager crashed in feisty

This is actually a problem with missing support for python2.5. This breaks python-dbus and that breaks update-manager and g-a-i.

Changed in pyrex:
status: Unconfirmed → Confirmed
Revision history for this message
Michael Vogt (mvo) wrote :

This problem should (hopefully) be fixed when python-dbus 0.71-3ubuntu1 enters the archive.

Please confirm if that fixes the problem.

Thanks,
 Michael

Changed in pyrex:
assignee: nobody → mvo
status: Confirmed → Fix Committed
Changed in update-manager:
assignee: nobody → mvo
importance: Critical → High
status: Confirmed → In Progress
Revision history for this message
Владимир Крылов (s6numid) wrote : Re: [Bug 79274] Re: update-manager crashed in feisty

but when it must happen?

2007/1/16, Michael Vogt <email address hidden>:
>
> This problem should (hopefully) be fixed when python-dbus 0.71-3ubuntu1
> enters the archive.
>
> Please confirm if that fixes the problem.
>
> Thanks,
> Michael
>
> ** Changed in: pyrex (Ubuntu)
> Assignee: (unassigned) => Michael Vogt
> Status: Confirmed => Fix Committed
>
> ** Changed in: update-manager (Ubuntu)
> Importance: Critical => High
> Assignee: (unassigned) => Michael Vogt
> Status: Confirmed => In Progress
>
> --
> update-manager crashed in feisty
> https://launchpad.net/bugs/79274
>

Revision history for this message
blitze (blitze) wrote : Re: update-manager crashed in feisty

Having the same problem here.
Feisty 64 Dist-upgraded 16/1 11.10pm EST Australia.

Looking forward to seeing this fixed as Updater has been broken for a week or more now.

Revision history for this message
Marco Paulo Martins Sousa (marcomsousa) wrote :

I update to python-dbus 0.71-3ubuntu1, and is not fixed...:

See log:
Introspect error: The name org.freedesktop.UpdateManager was not provided by any .service files
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 443, in setupDbus
    iface.bringToFront()
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 25, in __call__
    ret = self._proxy_method (*args, **keywords)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 102, in __call__
    reply_message = self._connection.send_with_reply_and_block(message, timeout)
  File "dbus_bindings.pyx", line 455, in dbus_bindings.Connection.send_with_reply_and_block
TypeError: exceptions must be strings, classes, or instances, not type

Revision history for this message
Marco Paulo Martins Sousa (marcomsousa) wrote :

erm, sorry. I update now, and it's work very well.

Fixed

Changed in update-manager:
status: In Progress → Fix Released
Revision history for this message
Jan-Erik van de Pol (pollypicasso-deactivatedaccount) wrote :

I can only update with the terminal now and for me it isn't fixed. I run feisty and the problem came with the dist-upgrade / new control center.
That is the same time the music in my notebook stops! I have no sound at all since the upgrade :s

Revision history for this message
Pingswept (brandon-stafford) wrote :

Also crashes for me, but works when I right-click on the orange notification icon and select "Install all updates." It has crashed twice and then worked with the right-click both times.

Michael Vogt (mvo)
Changed in pyrex:
status: Fix Committed → Fix Released
importance: Undecided → High
Revision history for this message
Владимир Крылов (s6numid) wrote :

after upgrade upgrade-manager doesn't crash.

Revision history for this message
leo.lsdb (leo-lsdb) wrote : Re: [Bug 79274] Re: update-manager crashed in feisty

On mar, 2007-01-16 at 16:27 +0000, Владимир Крылов wrote:
> after upgrade upgrade-manager doesn't crash.
>

 Same for me :)

Revision history for this message
Jan-Erik van de Pol (pollypicasso-deactivatedaccount) wrote : Re: update-manager crashed in feisty

I'm a newbie with ubuntu and my English isn't very well.

Sorry that I don't understand directly what I most do but yes after the upgrade update-manager doesn't crash any more.

Now I only have ('t seems) one problem: I have no sound after the dist-upgrade which came with the update notifier. Can I report it as a bug? before it works.

thanks for help till now!

Revision history for this message
Marco Paulo Martins Sousa (marcomsousa) wrote :

>I'm a newbie with ubuntu and my English isn't very well.
>
>Sorry that I don't understand directly what I most do but yes >after the upgrade update-manager doesn't crash any more.
>
>Now I only have ('t seems) one problem: I have no sound after >the dist-upgrade which came with the update notifier. Can I >report it as a bug? before it works.
>
>thanks for help till now!

Yes you can, but here? no. Put in the the binary package that have this bug..
And here isn't the best place to discust this. use the forums.

Revision history for this message
Phil Mullarkey (phil-mullarkey) wrote :

I updated feisty today with all the new python packages and my update-manager crashes too!

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

@Phil Mullarkey: do you have the latest python-dbus package? does it still crash with it?

Revision history for this message
Foffa (fredrik-and) wrote : Re: [Bug 79274] Re: update-manager crashed in feisty

The bug seems to be solved with new python package.

Revision history for this message
Phil Mullarkey (phil-mullarkey) wrote : Re: update-manager crashed in feisty

Just had another update for python-dbus tonight and update-manager seems fine now. Cheers!

Revision history for this message
BrettLee (brett-brown) wrote :

I'm fixed. Update did the trick for me.

Revision history for this message
Nicolas DERIVE (kalon33) wrote :

Yes, seems to be really fixed. Thanks Michael for the patch and the upload.

Revision history for this message
UBfusion (ubfusion) wrote :

It does not seem to be fixed in 20070123 amd64 desktop iso installation (in vmware).

After installing all the 37 updates, the bug persists for me.
Running update-manager in a root terminal gives:

warning: could not initiate dbus
Unhandled exception in thread started by <bound method MetaRelease.download of <MetaRelease object (UpdateManager+MetaRelease+MetaRelease) at 0xf19910>>
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: '/root/.update-manager/meta-release'

Should I file this as a new bug ?

Revision history for this message
John Vivirito (gnomefreak) wrote :

UBfusion what version of update-manager is it? and what version of python-dbus. Also can you attach the crashreport.

Changed in update-manager:
status: Fix Released → Needs Info
Revision history for this message
UBfusion (ubfusion) wrote :

update-manager is 0.53.3
python-dbus is 0.71.3ubuntu1

It seems that more precisely this is bug #81220 so I posted the crash log there too.

Revision history for this message
sardion (ubuntu-sardion) wrote :

Also still having this problem. Xubuntu (feisty)

update-manager 0.53.3
python-dbus 0.80.1-1

Works fine with sudo but not as regular user.

Error reads as follows:

[d@wizardry:~]% update-manager
Traceback (most recent call last):
  File "/usr/bin/X11/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

When run as sudo/root:

warning: could not initiate dbus

Revision history for this message
Sebastian Breier (tomcat42) wrote :

Can we close this? I haven't seen this bug in ages (u-m 0.57.2).

Revision history for this message
leo.lsdb (leo-lsdb) wrote : Re: [Bug 79274] Re: update-manager crashed in feisty (TypeError: exceptions must be strings, classes, or instances, not type)

On jeu, 2007-02-15 at 14:02 +0000, Sebastian Breier wrote:
> Can we close this? I haven't seen this bug in ages (u-m 0.57.2).
>

 I think yes :)
Thanks for your job !

Revision history for this message
Sebastian Breier (tomcat42) wrote :

I didn't fix it, but thanks to the actual person who did. I'm closing it.

Changed in update-manager:
status: Needs Info → Fix Released
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.