Package: update-manager-gnome Version: 0.200.5-1 Severity: normal Once the update manager is done doing it's thing, it will sit there using 104% cpu usage waiting for me to click "close". The entire time it is using up 104% of my cpu resources waiting for input. This issue has not been in there for long, unless I've not noticed it previously. But it happens every single time that there is an update.
How I tell that it's done is, I watch the CPU frequency monitor applet, and once core 1 is at full clock and staying there, I know it's done updating. I doubt the system is supposed to eat up CPU cycles like crazy whilst waiting for input, so thus I have filed this bug. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages update-manager-gnome depends on: ii gconf2 2.32.4-1 GNOME configuration database syste ii gksu 2.0.2-5 graphical frontend to su ii python 2.6.6-14 interactive high-level object-orie ii python-dbus 0.84.0-1 simple interprocess messaging syst ii python-gconf 2.28.1-3 Python bindings for the GConf conf ii python-gobject 2.28.6-1 Python bindings for the GObject li ii python-gtk2 2.24.0-2 Python bindings for the GTK+ widge ii python-support 1.0.14 automated rebuilding support for P ii python-vte 1:0.28.1-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-g 0.76.7debian2+nmu1 manage the repositories that you i ii update-notifier 0.99.3debian9 Daemon which notifies about packag -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
