*** This bug is a duplicate of bug 194214 ***
https://bugs.launchpad.net/bugs/194214
This bug has been open for eight months, a lot of folks have complained, and
nothing has been done.
What's going on? What do we have to do to get someone's attention?
Guy
--
Keyboard keys get stuck and
** Summary changed:
- Keyboard keys stuck using Feisty + Xgl + Compiz Fusion
+ Keyboard keys get stuck and repeat (Feisty)
** Description changed:
Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often
get 'stuck' and continue being 'clicked' even after they are physically
** Summary changed:
- Keyboard keys get stuck and repeat (Feisty)
+ Keyboard keys get stuck and repeat (Feisty, Gutsy)
** Description changed:
Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often
get 'stuck' and continue being 'clicked' even after they are physically
For me the problem started when I upgraded from Edgy to Feisty on
22/6/07. Before that I was running the latest Edgy kernel, whatever it
was.
Right now I'm running:
Linux thinkpad 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686
GNU/Linux
--
Keyboard keys stuck using Feisty + Xgl +
Several people confirmed the problem who aren't using compiz fusion.
** Changed in: Ubuntu
Status: Invalid = New
--
Keyboard keys stuck using Feisty + Xgl + Compiz Fusion
https://bugs.launchpad.net/bugs/124406
You received this bug notification because you are a member of Ubuntu
Bugs,
Someone reported the same problem and he's not using compiz. He is using
fglrx, as am I. So I'm reopening. In the forums he says:
thomascj: I'm having the exact same problem, and I'm not running xgl,
or compiz fusion. I am, however, running fglrx. Turning off keyboard
repeat fixed it -- but I do
Public bug reported:
Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often
get 'stuck' and continue being 'clicked' even after they are physically
released. For example when clicking Alt-F4, sometimes it gets stuck so
all the windows are closed instead of just one.
My
Public bug reported:
Binary package hint: vncserver
When running vncserver, the startup script should be ~/.vnc/xstartup
according to the documentation.
Instead, vncserver runs /etc/X11/Xsession and completely ignores
xstartup.
** Affects: vnc (Ubuntu)
Importance: Undecided
This happens to me as well. I'm running Edgy on a thinkpad laptop with a
Radeon 9600-based card. Using the 'radeon' driver, external VGA works
fine, but DVI doesn't work. When using fglrx, everything works fine.
Another thing that may be related:
cat /proc/acpi/ibm/video
shows dvi: disabled
