Hi Toshiro, On Sat, Apr 07, 2007 at 01:11:47AM +0200, Raúl Sánchez Siles wrote: > Hello: > > Maybe a backtrace could be of help. Just follow the following procedure: > > 1- Repeat the problem, so you get the 100% cpu usage. > 2- Go to a console (graphical, text or remote) and after log in > issue: "gdb -p $(pidof kded)" > 3- Enable logging to a file: "set log on" > 4- Get a backtrace: "bt" > 5- Quit gdb: "quit" > > Note: on step 2 you would like to be on a writable path, e.g. $HOME or > /tmp, > since the gdb log file(gdb.txt) will be stored there. > > After this you could send the gdb log file: gdb.txt. >
Can you try this? Do you have any new information? Ana
