Bug 179314

Summary: I am flooded by ksnapshot windows
Product: [Applications] ksnapshot Reporter: musetto <melchiade3>
Component: generalAssignee: Richard Moore <rich>
Status: RESOLVED DUPLICATE    
Severity: normal CC: uwolfer
Priority: NOR    
Version: 0.7   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description musetto 2009-01-01 23:21:29 UTC
Version:           0.7 (using 3.5.9, compiled sources)
Compiler:          Target: i586-manbo-linux-gnu
OS:                Linux (i686) release 2.6.24.7-desktop-2mnb

I have got 2 computers running Mandriva 2008.1 (Spring). The unpleasant event was experienced in both of them. Simply stated, if I press the "Stamp" button of my keyboard, the Knaspshot window appears and I can close it if I want. If I press up to 3 times in a short period of time the same "Stamp" button, 3 Ksnapshot windows appear as it is correctly assumed. But if I press 4 times in a short interval of time the "Stamp" button, something nasty happens. Ksnapshot is continuosly called and in a short period of time I am flooded with hundreds (up to 214 before I decided to unplug the power cord from my PC) of Ksnapshot instances. I can kill them as fast as I can but they will soon littering my screen again. Moreover, if I am quick enough to start the shotdown routine, the computer will more or less smoothly turn off (and at the successive I will find all the Knaspshot launched before the shotdown, e.g. 54 (!!)). If I am too slow, I will rapidly lose control of the PC as all its resources are drained by Ksnapshot windows and the only solution is to physically stop the computer by removing the power cord. I discovered this bug because the keyboard features the "Stamp" button very close to the "Backspace" button and so it happens to me that while trying to delete a word by clicking the "Backspace" button I end up clicking the "Stamp" button 3 or 4 (aargh: too much) times before realizing I am acting on the wrong button...
Comment 1 Urs Wolfer 2009-01-02 00:11:49 UTC

*** This bug has been marked as a duplicate of bug 166190 ***