Hi Christian,
Never happens when is in suspend the computer. Allways happens while the computer is on, mostly while i am using it.
What I meant is if it happens after a suspend/resume cycle or not. I thought in some of the previous emails I read that, but perhaps I am confused with some other threads.
One important thing, this happen only this time. I try to open a PDF, and kpdf does not start, few hours after that i see the runaway again. Use KILL -TTIN, and the kpdf open the requested files (one hour after i require it)
The problem stems from the way kdesktop and kdesktop_lock interacts with each other and how this sometimes result in either kdesktop being blocked when it shouldn't (hence the TTIN unblock it) or kdesktop_lock not locking/screensaving the screen.
I didn't check the code, but the problem with kpdf is possibly related to kpdf doing some dcop call to kdesktop and waiting for the call to return. If kdesktop is blocked, the call is blocking. Once kdesktop is unblocked (with TTIN) then the pending call is performed and kpdf can proceed. Or it could be that you tried to click a pdf icon on the desktop when it was blocked, either way the action is performed after kdesktop works again.
Cheers Michele