Package: pommed Version: 1.39~dfsg-2+b1 Severity: normal My system is a mid-2011 MBP. I'm leaving it booted for days, and noticed something rather odd, considering the little pommed supposedly does: pommed's cumulative time is awfully high.
Right now, on my system that has 9 days and 2 hours of uptime, the cumulative time of cpu used by pommed is 120 minutes. Relative to 9 days+, this is not very much, but still, when compared to the fact that Xorg, which does actively suck CPU at times, like when playing videos, which I did in the past 9 days, has a cumulative time of 127 minutes... I'm inclined to think there's something seriously wrong in pommed. Especially when there is a huge gap between cumulative time for pommed, and other daemons: - ibus-daemon: 25 minutes 24 seconds - /usr/share/ibus/ui/gtk/main.py: 13 minutes 45 seconds - ibus-x11: 12 minutes 38 seconds - dbus-daemon: 8 minutes 44 seconds - awesome: 6 minutes 10 seconds - NetworkManager: 5 minutes 53 seconds - pulseaudio: 5 minutes 46 seconds In fact, the cumulative time of all long-lived processes on my system, except pommed, Xorg and iceweasel, is 141 minutes, which is only 21 minutes more than pommed, for a whole lot of processes. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pommed depends on: ii eject 2.1.5+deb1+cvs20081104-11 ii libasound2 1.0.25-4 ii libaudiofile1 0.3.4-1 ii libc6 2.13-35 ii libconfuse0 2.7-4 ii libdbus-1-3 1.6.2-2 ii libpci3 1:3.1.9-5 Versions of packages pommed recommends: ii dbus 1.6.2-2 pommed suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
