emerged kcpuload-1.90-r2.ebuild, compiled successfully, but dumps on startup. bash-2.05a$ kcpuload & [2] 8655 bash-2.05a$ KCrash: crashing.... crashRecursionCounter = 2 KCrash: Application Name = kcpuload path = <unknown> pid = 8655 QMutex::~QMutex: destroy failure: Device or resource busy I'm not sure what device it's looking for. Stacktrace follows: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x41004ee9 in wait4 () from /lib/libc.so.6 #0 0x41004ee9 in wait4 () from /lib/libc.so.6 #1 0x4108250c in __check_rhosts_file () from /lib/libc.so.6 #2 0x402ff155 in KCrash::defaultCrashHandler () from /usr/kde/2/lib/libkdecore.so.3 #3 0x410915d4 in sigaction () from /lib/libpthread.so.0 #4 0x40f86818 in sigaction () from /lib/libc.so.6 #5 0x40551d0d in QWidget::create () from /usr/qt/2/lib/libqt-mt.so.2 #6 0x405f7b89 in QWidget::QWidget () from /usr/qt/2/lib/libqt-mt.so.2 #7 0x4026b980 in KApplication::init () from /usr/kde/2/lib/libkdecore.so.3 #8 0x4026b121 in KApplication::KApplication () from /usr/kde/2/lib/libkdecore.so.3 #9 0x08055b54 in strcpy () #10 0x40f75311 in __libc_start_main () from /lib/libc.so.6 Thanks, Kevin
The only device it should be opening is /proc/loadavg or some such. Do other cpu-usage displaying apps work, like the kicker ksysguard applet?
Well, there's always top, and others too. But if ksysguard works there's probably nothnig wrong with your /proc, it was unlikely anyway.It might not even be a device but a resource of some kind that it wants. Maybe you could try running it outside kde? You could also try sending a bugreport upstream, to the author.
Closing because it's old and there has been no further input.
