Results 1 to 4 of 4
Hello there, I've managed to pin down a small problem with Mandrake 10.1 Official release - thought I'd share this with you. I've noticed over the past month or so ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 02-04-2005 #1
KDE mountwatcher - Problem app?
I've managed to pin down a small problem with Mandrake 10.1 Official release - thought I'd share this with you.
I've noticed over the past month or so that something was slowing down my system. I installed 'Runaway process catcher' applet (it just sits on your kicker as a 'smiley' icon)
Noticed that the application kded is the problem. This seems to be (or be
associated with) kde mountwatcher. I did a Ctrl+Esc. and saw that it was using 80-83 percent of user resources and 17% of total system resources.
That's more than X is using!
I've tried re-nicing the process - not sure if this has really helped. Sometimes Konqueror will crash or Unreal Tournament 2004 will slow down a lot. I'm convinced this is the reason. If I kill the process, the system complains, but things mysteriously start working as expected. Thanks for readingI am always doing that which I can not do, in order that I may learn how to do it. - Pablo Picasso
- 02-18-2005 #2
- Join Date
- Feb 2005
Re: KDE mountwatcher - Problem app?
Sorry, no solution from me. Just the same problem.
I am new to linux(for that matter any *x) and have no clue how to debug. But it is a very frustrating problem (I don't know how fingal finds it small For now, I am also resorting to killing the kded, but the system complains somethings and I fear something may break somewhere.
In any case, if anybody has a solution, please post.
- 02-18-2005 #3
- Join Date
- Mar 2003
Submit a bug report to Mandrake.
JeremyRegistered Linux user #346571
"All The Dude ever wanted was his rug back" - The Dude
- 02-21-2005 #4
Pleased to see that someone has already logged this as a bug on the Mandrake site. There's a lot of discussion about it and they posted a kludge/workaround as a temp solution. They said:
As a temporary workaround, you can start this "watchdog" script in your .xsession file in the background:
while true; do
load=`ps -C kded -o pcpu=`
# we are doing lexicographic comparison
# intentionally, it is not a bug
# It is a neat trick how to get around
# problems when $load is empty (no process running)
# and with ps returning floating point numbers (-gt takes only integers)
if [[ $load > "3.0" ]]; then
#echo "We have a cpu hog, restarting it."
kdeinit kded &> /dev/null &
#echo "Pausing before resuming watch."
As for me, I'll live with it for a while :oI am always doing that which I can not do, in order that I may learn how to do it. - Pablo Picasso