Package: update-manager Severity: normal
Update manager seems to hog a single cpu at 100% at least for 30mins. Behavior first sighted at 29/Jun/11. Last thing the gui noted was that it would be fetching update notes. Sidenote: it would be wise if the network worker would spawn a seperate thread via fork() so even with an unresponsive network worker the gui could still be used (e.g. to quit it) IMHO this behavior is related to recent updates this month where no changelog could be fetched. Instead the gui produced a "could not fetch update information" (sort-of). -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
