Your message dated Mon, 30 Apr 2012 00:00:53 +0200
with message-id
<caknhny_cwny5qktfmrzr-qs_m+mgswnh5ffok6etzn8oean...@mail.gmail.com>
and subject line Re: Bug#659882: [apper] The check for new updates sometimes
uses the
has caused the Debian Bug report #659882,
regarding [apper] The check for new updates sometimes uses the 100% of a CPU
Core for a long time
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
659882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659882
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apper
Version: 0.7.0-1
Severity: normal
Many thanks to the maintainer who has worked on this beautiful package.
I have found a little bug:
When I do a checking for new updates sometimes, the daemon packagekitd,
uses the 100% of a CPU Core for a long time
The progress bar holds on 94% and the status message reports the word
"Terminato" but in meantime the process packagekitd is eating 100% of a CPU
I have tryed with
pkcon get-updates
who makes her work in a very short time; I think this is equivalent to
the GUI command who launch a check for new updates.
--- System information. ---
Architecture: i386
Kernel: Linux 3.2.4
Debian Release: wheezy/sid
500 testing ftp.it.debian.org
--- Package information. ---
Depends (Version) | Installed
============================================-+-=====================
packagekit (>= 0.6.18) | 0.7.2-3
kdebase-runtime | 4:4.6.5-1+b1
libc6 (>= 2.1.3) | 2.13-26
libdebconf-kde0 (>= 0.1+git20101209) | 0.1+git20110702-1
libgcc1 (>= 1:4.1.1) | 1:4.6.2-12
libkcmutils4 (>= 4:4.6.0) | 4:4.6.5-2+b1
libkdecore5 (>= 4:4.6.0) | 4:4.6.5-2+b1
libkdeui5 (>= 4:4.6.0) | 4:4.6.5-2+b1
libkemoticons4 (>= 4:4.6.0) | 4:4.6.5-2+b1
libkidletime4 (>= 4:4.6.0) | 4:4.6.5-2+b1
libkio5 (>= 4:4.6.0) | 4:4.6.5-2+b1
libkprintutils4 (>= 4:4.6.0) | 4:4.6.5-2+b1
libkutils4 | 4:4.6.5-2+b1
libpackagekit-qt2-2 | 0.7.2-3
libqt4-dbus (>= 4:4.6.1) | 4:4.7.4-2
libqt4-network (>= 4:4.5.3) | 4:4.7.4-2
libqt4-sql (>= 4:4.5.3) | 4:4.7.4-2
libqt4-svg (>= 4:4.5.3) | 4:4.7.4-2
libqt4-xml (>= 4:4.5.3) | 4:4.7.4-2
libqt4-xmlpatterns (>= 4:4.5.3) | 4:4.7.4-2
libqtcore4 (>= 4:4.7.0~beta1) | 4:4.7.4-2
libqtgui4 (>= 4:4.6.2) | 4:4.7.4-2
libsolid4 (>= 4:4.6.0) | 4:4.6.5-2+b1
libstdc++6 (>= 4.1.1) | 4.6.2-12
Recommends (Version) | Installed
======================================-+-===========
app-install-data | 2010.11.17
software-properties-kde | 0.76.7debian2+nmu2
Suggests (Version) | Installed
=================================-+-===========
debconf-kde-helper |
--- End Message ---
--- Begin Message ---
fixed 659882 0.7.4-2
thankyou
This issue should be fixed now. (it is still possible that it occurs
on machines with very low CPU speed).
If someone still has this issue, feel free to reopen the bug.
Cheers,
Matthias
--- End Message ---
