KDE4.0 (SuSE 11.0) has decided to start one ksnapshot after another.
Meanwhile 70 ksnapshots are running and the machine is blocked. I did not
tell KDE to do so.
What’s this?
C.N.Taur
C.N.Taur wrote:
> KDE4.0 (SuSE 11.0) has decided to start one ksnapshot after another.
> Meanwhile 70 ksnapshots are running and the machine is blocked. I did not
> tell KDE to do so.
>
> What’s this?
>
> C.N.Taur
Is it possible you have a stuck key? Press the “Print Screen” key (upper
right of keyboard, one of those three keys you’ve never -ever- pushed)
Ksnapshot is a pretty good system killer… My kitten (The brat!) likes to
stand on that button… and with 30keys/sec repeat rate… I found out that
my system can handle over 250 instances! Love him, but he’s a brat!
Loni
–
L R Nix
lornix@lornix.com
L R Nix wrote:
> C.N.Taur wrote:
>
>> KDE4.0 (SuSE 11.0) has decided to start one ksnapshot after another.
>> Meanwhile 70 ksnapshots are running and the machine is blocked. I did not
>> tell KDE to do so.
>>
>> What’s this?
>>
>> C.N.Taur
>
> Is it possible you have a stuck key? Press the “Print Screen” key (upper
> right of keyboard, one of those three keys you’ve never -ever- pushed)
>
> Ksnapshot is a pretty good system killer… My kitten (The brat!) likes to
> stand on that button… and with 30keys/sec repeat rate… I found out
> that
> my system can handle over 250 instances! Love him, but he’s a brat!
>
> Loni
>
Thank you. No it’s not a stuck key. Meanwhile I think, I located the source
of problem. I have a terminal window running bash. As soon as I hit the
cursor up key (repeat last command), ksnapshot starts. If I am not fast
enough to hit ‘close’ one ksnapshot is startet after the other.
C.N.Taur
C.N.Taur wrote:
> L R Nix wrote:
>
>> C.N.Taur wrote:
>>
>>> KDE4.0 (SuSE 11.0) has decided to start one ksnapshot after another.
>>> Meanwhile 70 ksnapshots are running and the machine is blocked. I did not
>>> tell KDE to do so.
>>>
>>> What’s this?
>>>
>>> C.N.Taur
>>
>> Is it possible you have a stuck key? Press the “Print Screen” key (upper
>> right of keyboard, one of those three keys you’ve never -ever- pushed)
>>
>> Ksnapshot is a pretty good system killer… My kitten (The brat!) likes to
>> stand on that button… and with 30keys/sec repeat rate… I found out
>> that
>> my system can handle over 250 instances! Love him, but he’s a brat!
>>
>> Loni
>>
> Thank you. No it’s not a stuck key. Meanwhile I think, I located the source
> of problem. I have a terminal window running bash. As soon as I hit the
> cursor up key (repeat last command), ksnapshot starts. If I am not fast
> enough to hit ‘close’ one ksnapshot is startet after the other.
> C.N.Taur
Ummm, that’s really odd!
So none of this starts until / unless you press the up-arrow key in the bash
terminal?
Is this consistant? Does this happen with ANY bash terminal you open? Can
you reproduce it at will (not that we WANT to…)
Loni
L R Nix
lornix@lornix.com
L R Nix wrote:
> C.N.Taur wrote:
>
>> L R Nix wrote:
>>
>>> C.N.Taur wrote:
>>>
>>>> KDE4.0 (SuSE 11.0) has decided to start one ksnapshot after another.
>>>> Meanwhile 70 ksnapshots are running and the machine is blocked. I did
>>>> not tell KDE to do so.
>>>>
>>>> What’s this?
>>>>
>>>> C.N.Taur
>>>
>>> Is it possible you have a stuck key? Press the “Print Screen” key
>>> (upper right of keyboard, one of those three keys you’ve never -ever-
>>> pushed)
>>>
>>> Ksnapshot is a pretty good system killer… My kitten (The brat!) likes
>>> to stand on that button… and with 30keys/sec repeat rate… I found
>>> out that
>>> my system can handle over 250 instances! Love him, but he’s a brat!
>>>
>>> Loni
>>>
>> Thank you. No it’s not a stuck key. Meanwhile I think, I located the
>> source of problem. I have a terminal window running bash. As soon as I
>> hit the cursor up key (repeat last command), ksnapshot starts. If I am
>> not fast enough to hit ‘close’ one ksnapshot is startet after the other.
>> C.N.Taur
>
> Ummm, that’s really odd!
>
> So none of this starts until / unless you press the up-arrow key in the
> bash terminal?
>
> Is this consistant? Does this happen with ANY bash terminal you open?
> Can you reproduce it at will (not that we WANT to…)
>
> Loni
Yes, I can reproduce it - as long as openSuse11 runs in native mode. If I
start it under XEN, this effect does not occur!
I open a terminal and press ‘cursor up’. At the same moment, I see the
startup icon of ksnapshot. According to my latest tests, this happens with
every cursor key, also with page up, page down, pos1, end, insert and
delete.
It doen not happen, if NumLock is off!
What is strange, too: All three LEDs (Num, Shift, Scroll) are on, when the
system comes up. IF I hit NumLock, Shift and Scroll LEDs go off, but Num
stays on.
C.N.Taur
C.N.Taur wrote:
> L R Nix wrote:
>
>> C.N.Taur wrote:
>>
>>> L R Nix wrote:
>>>
>>>> C.N.Taur wrote:
>>>>
>>>>> KDE4.0 (SuSE 11.0) has decided to start one ksnapshot after another.
>>>>> Meanwhile 70 ksnapshots are running and the machine is blocked. I did
>>>>> not tell KDE to do so.
>>>>>
>>>>> What’s this?
>>>>>
>>>>> C.N.Taur
>>>>
>>>> Is it possible you have a stuck key? Press the “Print Screen” key
>>>> (upper right of keyboard, one of those three keys you’ve never -ever-
>>>> pushed)
>>>>
>>>> Ksnapshot is a pretty good system killer… My kitten (The brat!) likes
>>>> to stand on that button… and with 30keys/sec repeat rate… I found
>>>> out that
>>>> my system can handle over 250 instances! Love him, but he’s a brat!
>>>>
>>>> Loni
>>>>
>>> Thank you. No it’s not a stuck key. Meanwhile I think, I located the
>>> source of problem. I have a terminal window running bash. As soon as I
>>> hit the cursor up key (repeat last command), ksnapshot starts. If I am
>>> not fast enough to hit ‘close’ one ksnapshot is startet after the other.
>>> C.N.Taur
>>
>> Ummm, that’s really odd!
>>
>> So none of this starts until / unless you press the up-arrow key in the
>> bash terminal?
>>
>> Is this consistant? Does this happen with ANY bash terminal you open?
>> Can you reproduce it at will (not that we WANT to…)
>>
>> Loni
> Yes, I can reproduce it - as long as openSuse11 runs in native mode. If I
> start it under XEN, this effect does not occur!
> I open a terminal and press ‘cursor up’. At the same moment, I see the
> startup icon of ksnapshot. According to my latest tests, this happens with
> every cursor key, also with page up, page down, pos1, end, insert and
> delete.
> It doen not happen, if NumLock is off!
> What is strange, too: All three LEDs (Num, Shift, Scroll) are on, when the
> system comes up. IF I hit NumLock, Shift and Scroll LEDs go off, but Num
> stays on.
>
> C.N.Taur
>
Ummmm, have you considered an Exorcism?
That’s really odd behavior! Works fine in xen, wonky in native.
Well, maybe start narrowing the culprits… is it possible to unplug and
replug your keyboard once you’re in native mode? Maybe the keyboard or driver
is being set up in an odd manner when not in xen mode?
Yup, I’m pulling at straws here. If anything, I’d have expected it to be the
other way around, xen being the bad guy.
I’m sorry, nothing else comes to mind.
Loni
L R Nix
lornix@lornix.com
I’ve actually run into this before.
Up in a terminal would register as PrintScreen.
Hold down Ctrl-Alt-Backspace or restart the computer to kill the Ksnapshot madness.
Now go back into KDE, and go into the Region settings, and change your keyboard layout.
enderandrew wrote:
>
> I’ve actually run into this before.
>
> Up in a terminal would register as PrintScreen.
>
> Hold down Ctrl-Alt-Backspace or restart the computer to kill the
> Ksnapshot madness.
>
> Now go back into KDE, and go into the Region settings, and change your
> keyboard layout.
>
>
Thank you for all the hints.
I think, KDE gets confused because it’s a notebook with keyboard and mouse
attached by USB. If I start it without external keyb/mouse, it works like
intended. But the NumLock LED is off, while NumLock is active, and the
mouse buttons are swapped.
Started with keyb/mouse attached, I get inverted LEDs, NumLock off and the
effects descibed.
Maybe someone writing the drivers could have an explanation.
C.N.Taur