Bug#565462: update-manager-gnome: Same here, some more details

Enrico Zini enrico at enricozini.org
Sun Mar 20 17:01:18 UTC 2011


Package: update-manager-gnome
Version: 0.200.5-1
Severity: normal

Hello,

I see the same problem here. Some more details: ^C-ing update-manager while it's stuck at 100% CPU gives 
this backtrace:

# update-manager 
^CTraceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/GtkProgress.py", line 77, in update_func
    self._ui.update_package_list()
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 855, in update_package_list
    selected)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 381, in set_package_selection
    self.set_package_selection(sdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 383, in set_package_selection
    self.set_package_selection(rsdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 381, in set_package_selection
    self.set_package_selection(sdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 383, in set_package_selection
    self.set_package_selection(rsdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 381, in set_package_selection
    self.set_package_selection(sdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 381, in set_package_selection
    self.set_package_selection(sdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 383, in set_package_selection
    self.set_package_selection(rsdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 381, in set_package_selection
    self.set_package_selection(sdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 383, in set_package_selection
    self.set_package_selection(rsdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 383, in set_package_selection
    self.set_package_selection(rsdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 383, in set_package_selection
    self.set_package_selection(rsdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 381, in set_package_selection
    self.set_package_selection(sdep, selected=True, handled=h)
  File "/usr/lib/pymodules/python2.6/UpdateManager/Frontend/Gtk/ui.py", line 374, in set_package_selection
    h.append(pkg_info)
KeyboardInterrupt

And there is this in ~/.xsession-errors:

ERROR:dbus.proxies:Introspect error on :1.0:/org/freedesktop/UpdateManagerObject: dbus.exceptions.DBusException: 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.

This quite obviously makes update-manager completely useless. aptitude works fine and shows just about 60 
packages to upload: not a big deal of work. We're looking at a trivial 6.0->6.1 update.

After performing the update with aptitude, update-manager starts to work fine again, showing that there are 
no updates to perform.

The problem is made worse because when clicking on the update notification applet it takes a long while for 
update-manager to appear, so one clicks again, and again, and in the end one finds several update-manager 
windows running at 100% CPU. 'Force quit' from the window manager kills the UI but leaves one background 
process per window running at 100% CPU indefinitely, unless killed by root. You can see that this is an 
excellent way to send desktop users, and those providing support to them, down the road to madness and 
despair.


Cheers,

Enrico


-- System Information:
Debian Release: 6.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages update-manager-gnome depends on:
ii  gconf2                2.28.1-6           GNOME configuration database syste
ii  gksu                  2.0.2-5            graphical frontend to su
ii  python                2.6.6-3+squeeze5   interactive high-level object-orie
ii  python-dbus           0.83.1-1           simple interprocess messaging syst
ii  python-gconf          2.28.1-1           Python bindings for the GConf conf
ii  python-gobject        2.21.4+is.2.21.3-1 Python bindings for the GObject li
ii  python-gtk2           2.17.0-4           Python bindings for the GTK+ widge
ii  python-support        1.0.10             automated rebuilding support for P
ii  python-vte            1:0.24.3-2         Python bindings for the VTE widget
ii  update-manager-core   0.200.5-1          APT update manager core functional

update-manager-gnome recommends no packages.

Versions of packages update-manager-gnome suggests:
ii  software-properties-gtk    0.60.debian-3 manage the repositories that you i
ii  update-notifier            0.99.3debian8 Daemon which notifies about packag

-- no debconf information





More information about the pkg-gnome-maintainers mailing list