Hi Guru...
Did you ever find a solution to this?
I think I've experienced the same problem as you (flickering K menu),
although in my case it happened very rarely and took a while to debug it. Details...
- Dell Inspiron 9400 with Synaptics touchpad (I think the problem is unrelated to the touchpad though)
- Kubuntu 6.06 (Dapper)
I discovered that I could simulate the problem when it's not
occurring by holding down the 'page up' key while browsing the K menu.
This causes the top entry to be continually selected, with momentary selections of other items as you scroll up and down the menu. Is that the effect you see? When the problem is occurring, the screensaver also fails to kick in.
These two observations got me thinking that maybe something was
generating a stream of fake 'page up' (or similar) key events. The
flickering rate seems to be about the rate of key repeats, and it would
also explain the failure of the kde screensaver to kick in.
There should be a program called xev on your system (/usr/bin/xev in my
case), which will report X events to stdout.
I recently managed to get my system to misbehave, and sure enough, xev
reported an endless stream of these events...
KeyRelease event, serial 32, synthetic NO, window 0x800001,
root 0x135, subw 0x0, time 1024182509, (68,132), root
2342,161),
state 0x0, keycode 101 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
KeyPress event, serial 32, synthetic NO, window 0x800001,
root 0x135, subw 0x0, time 1024182509, (68,132), root
2342,161),
state 0x0, keycode 101 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
... indicating that X thinks that the 'keycode 101' key is being held
down. I can't get anything on my keyboard to produce that keycode, but
https://wiki.ubuntu.com/KubuntuLaptopKeycodes
suggests that it may be the 'brightness down' key combination (Fn+downarrow on this machine).
Ominously, the 'brightness up' key generates keycode 212, but the
'brightness down' key generates no keycode at all, but does change the
display brightness. My current suspicion is that maybe the 'brightness
down' key press does occasionally sneak through somehow and X fails to see the key-release event.
Since discovering this I haven't had any more problems - in my case the event storm seems to be cancelled by typing a few more keys. I'm curious as to where the actual bug lies (kernel or bios I suspect), but it's not a real problem for me now that I know what provokes it.
Anyway, run xev, hold the mouse cursor over the xev window and see what events are being generated.
Hope this helps.
cheers
David