kded4 and knotify4 eats 100% cpu

[oli z]

Description: Ubuntu Natty (development branch)
Release: 11.04

libknotifyconfig4:
  Installiert: 4:4.6.2-0ubuntu4
  Kandidat: 4:4.6.2-0ubuntu4
  Versionstabelle:
 *** 4:4.6.2-0ubuntu4 0
        500 http://de.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status

kdelibs-bin:
  Installiert: 4:4.6.2-0ubuntu4
  Kandidat: 4:4.6.2-0ubuntu4
  Versionstabelle:
 *** 4:4.6.2-0ubuntu4 0
        500 http://de.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status

dont know what i did, but its always the same when i logged in, after a few minutes my cpu fan starts making noise, thats why i take a look at top

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: kdelibs-bin 4:4.6.2-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Fri Apr 22 02:57:20 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/kdeinit4
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: kde4libs
UpgradeStatus: Upgraded to natty on 2011-04-21 (0 days ago)

[Hendrik van Wyk (tonberry)]

I am also affected on 32bit natty, although I only saw kded4 using 100% cpu and not knotify4.

[Ernst (ernst-blaauw)]

After I logout and login again, knotify4 takes all my CPU. Possible related Launchpad entries:
https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/685073
https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/755658

I'm running 64-bit and Ubuntu with the 'old' gnome2 interface, with radeon open source graphic drivers. I have KDE installed because of yakuake.

[Michael Uvarov (freeakk)]

I'm running 64-bit and Ubuntu with the unity interface, with fgrlx graphic drivers - and I have same situation.

[James (james-ellis-gmail)]

Happens for me Natty/KDE 4.6.3 - kded4 eats 100%+ CPU on resume from suspend

This bug on bugs.kde.org seems to match. I disabled Network Status, let's see if that works:

https://bugs.kde.org/show_bug.cgi?id=271645

at the moment kill -KILL <kded4 pid> resolves CPU usage and associated temperature

[Harald Sitter (apachelogger)]

Any news? might be related to bug #755608

[strav (strav)]

Here. Most of the time on resume from suspend, I'm seeing knotify4 eating 100% of my cpu ressource. Just to add some weight on this annoying bug.

Thanks.

[cefk (cfabik)]

Kubuntu 64bit - relatively fresh install with all current updates.
htop tells me, I got between 90% and 130% CPU-load (Core i7 930) for knotify4.
Mostly it keeps around 100%.

It might be a coincidence, but I seem to only get that, when I have an active internet-connection (or had one previously in the currently active session). Which means, that once the bug gets triggered, deactivating the network-interfaces via network-manager does not cause the effects of the bug to go away. That's, what makes me unsure, if this is a coincidence, or not.
Killing the process always works, though.

Hope this helps to shrink the possibilities, where the bug might be situated.

[Jorn Argelo (jorn-wcborstel)]

Just wanted to let you guys know that if you disable the sound notifications (system settings -> application and system notifications) the CPU consumption seems to go away. Running an strace on knotify4 reveals the following. Note that this is strace is done on Arch Linux and not on Ubuntu.

stat("/usr/share/alsa/alsa.conf", {st_mode=S_IFREG|0644, st_size=9030, ...}) = 0
open("/dev/snd/controlC0", O_RDONLY|O_CLOEXEC) = 24
fcntl(24, F_SETFD, FD_CLOEXEC) = 0
ioctl(24, SNDRV_CTL_IOCTL_CARD_INFO or UI_DEV_CREATE, 0x7fff04d10100) = 0
close(24) = 0
open("/dev/snd/controlC0", O_RDWR|O_CLOEXEC) = 24
fcntl(24, F_SETFD, FD_CLOEXEC) = 0
ioctl(24, SNDRV_CTL_IOCTL_PVERSION or USBDEVFS_CONTROL or USBDEVFS_CONTROL32, 0x7fff04d1046c) = 0
ioctl(24, SNDRV_CTL_IOCTL_CARD_INFO or UI_DEV_CREATE, 0x7fff04d10450) = 0
close(24) = 0
open("/etc/group", O_RDONLY|O_CLOEXEC) = 24
fstat(24, {st_mode=S_IFREG|0644, st_size=642, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f8dad020000
read(24, "root:x:0:root\nbin:x:1:root,bin,d"..., 4096) = 642
close(24) = 0
munmap(0x7f8dad020000, 4096) = 0
open("/dev/snd/controlC0", O_RDONLY|O_CLOEXEC) = 24
fcntl(24, F_SETFD, FD_CLOEXEC) = 0
ioctl(24, SNDRV_CTL_IOCTL_CARD_INFO or UI_DEV_CREATE, 0x7fff04d102a0) = 0
close(24) = 0
semget(0x56a4d5, 1, IPC_CREAT|0660) = 100335616
semctl(100335616, 0, IPC_STAT, 0x7fff04d10690) = 0
semctl(100335616, 0, IPC_SET, 0x7fff04d10690) = 0
semop(100335616, {{0, 0, 0}, {0, 1, SEM_UNDO}}, 2) = 0
shmget(0x56a4d5, 488, IPC_CREAT|0660) = 622592
shmat(622592, 0, 0) = ?
mlock(0x7f8dad020000, 488) = 0
shmctl(622592, IPC_STAT, 0x7fff04d10680) = 0
open("/dev/snd/controlC0", O_RDONLY|O_CLOEXEC) = 24
fcntl(24, F_SETFD, FD_CLOEXEC) = 0
ioctl(24, SNDRV_CTL_IOCTL_CARD_INFO or UI_DEV_CREATE, 0x7fff04d10180) = 0
close(24) = 0
open("/dev/snd/controlC0", O_RDWR|O_CLOEXEC) = 24
fcntl(24, F_SETFD, FD_CLOEXEC) = 0
ioctl(24, SNDRV_CTL_IOCTL_PVERSION or USBDEVFS_CONTROL or USBDEVFS_CONTROL32, 0x7fff04d1033c) = 0
ioctl(24, SNDRV_CTL_IOCTL_PCM_PREFER_SUBDEVICE, 0x7fff04d1035c) = 0
open("/dev/snd/pcmC0D0p", O_RDWR|O_APPEND|O_NONBLOCK|O_CLOEXEC) = -1 EINVAL (Invalid argument)
close(24) = 0
shmdt(0) = -1 EINVAL (Invalid argument)
shmdt(0x7f8dad020000) = 0
shmctl(622592, IPC_STAT, 0x7fff04d10690) = 0
semctl(100335616, 0, IPC_RMID, 0) = 0
read(8, 0x1a2dfe4, 4096) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=10, events=POLLIN}, {fd=12, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
read(8, 0x1a2dfe4, 4096) = -1 EAGAIN (Resource temporarily unavailable)
stat("/usr/share/alsa/alsa.conf", {st_mode=S_IFREG|0644, st_size=9030, ...}) = 0
open("/dev/snd/controlC0", O_RDONLY|O_CLOEXEC) = 24
fcntl(24, F_SETFD, FD_CLOEXEC) = 0
ioctl(24, SNDRV_CTL_IOCTL_CARD_INFO or UI_DEV_...

[Peter Maloney (peter-maloney)]

I had this problem today. For me, Dolphin was also taking 100% CPU. I killed the 3 processes, and the problem is gone (without having to log out and back in).

Last week I had a similar problem, when I put a USB stick in the computer and it started going unusably slow. I had to kill many kde processes, knotify, dolphin, and dbus daemon, and (since I killed plasma-desktop) log back in to fix it. The USB stick does not cause this problem today (but also the device notifier doesn't detect it today, but I can mount it from the command line).

[jhoechtl (johann-hoechtl)]

Concerning knotify4 eating excessive CPU cycles, albeit not 100%, please assign yourself to bug
https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/948427

Thank you!

[Harald Sitter (apachelogger)]

Thanks for taking the time to report this bug. 11.04 reached end of life on October 28, 2012.
Please see this document for currently supported Kubuntu releases:
https://wiki.kubuntu.org/Releases

Unfortunately this means that there will be no more bugfixes for 11.04. It is also recommended that you upgrade, if you have not already.

Please feel free to report any other bugs you may find, and thanks for your understanding.