Related, dangerous KDE bugs

[The Beatles]

Scenario 1: You hit a key in an application, then something else gains focus. You switch back to your app only to find it's been receiving that key continuously. Example: start kspaceduel and keee the 'down' key held down. Alt-Tab away, let go of the down key, and switch back. It's still firing happily.

Scenario 2: You make a keystroke but something else starts using the CPU and your process is left unattended to. Your process gets CPU back again but also a lot of keystrokes as if you had continually been pressing the key combination at the time. Example: start searching in firefox, but Gmail decides to fetch new mail, nothing appears as you type. When your thread gets control again you see something like 'fedora kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkde'. Example 2, much worse: start firefox, hit Ctrl-T to open a new tab. It decides that opening a tab is a lot of effort. In the meanwhile, KDE is still happily sending it 't'-s. When the first tab renders, it starts opening up 54 (or whatever your number is) tabs. You hit Ctrl-W, iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiit st arts to close (the above is a blasted symptom of what is happening, I swear it wasn't planned), the same thing happens and it closes everything you had open...

Stable is certainly not a word I'd use to describe KDE. Maybe I'll just switch back to XFCE and just use kdesktop. So far xfwm4 has /never/ had these kinds of problems.

[The Beatles]

It seems it is restricted to RedHat kernels. Maybe XFCE didn't produce this because I didn't use it enough on Fedora.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=76959#c5

[Devari]

Well, to be fair to KDE, both of us are using older versions, correct?

But, aside from that... I haven't had any of these problems... What version are you using?

[The Beatles]

Got it...
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"

Uncomment that last line in xorg.conf and restart X. Trying now.

[Devari]

Right! Forgot that you are on Fedora, not MDK.

[The Beatles]

Confirming that that indeed solves the problem, for certain.

[The Beatles]

...and of course, as good practices demand, a reboot broke the fragile wireless...

[The Beatles]

Addendum, wireless fixed. I merely had to remind iwconfig that the key was restricted (this is NOT NOT NOT in the man pages, a friend told me off the grapevine) by typing iwconfig eth1 key restricted <key> then just ifup'ing eth1. So that works. Now how will I configure that to connect to the best network when even scanning doesn't work?