KDE not responding to mouse clicks after a resume-from-ram

[Joe Emenaker <joe@emenaker.com>]

I'm using the hibernate script triggered from a lid-closed action to 
suspend my Inspiron 8600 to ram. This works fairly well, except...

...after about 3 or 4 sleep/resume cycles, the kbluetoothd stops 
recognizing any bluetooth adaptor (this isn't too annoying, but if it's 
related to the next problem, then I'll be happy if I can fix both) and 
after about 15 or so sleep/resume cycles, KDE stops responding to 
mouse-clicks. I can move the mouse cursor all over the screen... and I 
can switch to a text console and back to KDE, etc... but clicking 
doesn't do anything. I can't close windows, I can't move them, I can't 
launch anything with kicker, etc.

I haven't been able to find any factors (ie, length of time it has been 
sleeping, battery level at sleep or resume, location of laptop at sleep 
or resume, etc.) that seem to correlate with KDE becoming unresponsive.

Any ideas why this is happening?

- Joe

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature