ubuntu-x-swat team mailing list archive

[Marcus Haslam <marcus.haslam@xxxxxxxxxxxxx>]

I'm out of the office until 1st August.

On 29 Apr 2011, at 14:12, james_mcl <124406@xxxxxxxxxxxxxxxxxx> wrote:

> Okay... that last point needed a comment of its own - now to look at  
> the
> other issues raised.
>
> 1.) "Touch base about this with Ajax to find if he has any  
> experimental branches, or if he knows if anyone else is working on  
> the problem, and how you can help." - It never occurred to me that  
> any experimental threaded branches might exist! I'll be in touch  
> with him, thanks for that.
> (Though, given the bug's intermittency, I don't think anyone's going  
> to have a reliable, repetitive test case as described - it'll be a  
> matter of seeing if intervals of x days pass without the symptom  
> recurring.)
>
> 2.) "Maybe Wayland will gain a better system for handling keyboard
> events" - Bryce, can you possibly supply the name of any particular  
> dev
> who would be in a position to know whether keyboard events in Wayland
> are being handled in a similar way to X? The possibility that this bug
> might survive all the way into X's successor is quite a horrific one!
>
> 3.) For other people who, like me, are trying Marius's workaround -  
> you
> should know that he had to file another bug, in that changing the
> keyboard delay setting in /etc/kbd/config had no effect (meaning,
> presumably, that he had to change it in the terminal every time he
> booted up.)
>
> (Actually, I'm noticing it seems to have created a new bug in my  
> case -
> pressing Enter once seems to be interpreted as pressing Enter several
> times on some occasions - although the key repeat stops by itself in
> less than a second.)
>
> 4.) Regarding post 313 - well, my keyboard certainly goes crazy daily,
> although I think this is probably true for most of us here. So I  
> guess I
> might have a "HW-specific oddity", though not one affecting my Hardy
> partition.
>
> So, to repeat my question in post 301, to file a new bug:
>
> "Would it be sufficient to run
>
> ubuntu-bug xorg
>
> referencing bug 124406, and then
>
> apport-collect (number of new bug)
>
> or is there any more information you would need that would not be
> supplied by this? (if so, please specify what this would be.)"
>
> 5.) In response to Post 310's assertions regarding the severity of the
> bug:
>
> "there could conceivably be some rare scenarios where this bug could
> cause some severe issue like a stuck delete key deleting files or
> whatnot"
>
> When the issue happens at least once daily, the question is not so  
> much
> whether this could be rare as how many days/weeks/months the user has
> before it happens - which eventually it must.
>
> And, for versions of the bug in which pressing another key doesn't  
> stop
> the repeating, it is *at least* as significant as the X crash/tie-dyed
> monitor, as the only way to resolve the issue is to hold down the  
> Power
> button.
>
> 6.) Thanks for your help Bryce!
>
> -- 
> You received this bug notification because you are a member of
> Papercutters, which is subscribed to One Hundred Paper Cuts.
> https://bugs.launchpad.net/bugs/124406
>
> Title:
>  Keyboard keys get stuck and repeat
>
> Status in GNU Emacs:
>  Invalid
> Status in One Hundred Paper Cuts:
>  Invalid
> Status in The Linux Kernel:
>  Confirmed
> Status in X.Org X server:
>  In Progress
> Status in “linux” package in Ubuntu:
>  Won't Fix
> Status in “xorg-server” package in Ubuntu:
>  Triaged
> Status in “linux” source package in Jaunty:
>  Won't Fix
> Status in “xorg-server” source package in Jaunty:
>  Invalid
> Status in Gentoo Linux:
>  New
>
> Bug description:
>  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 configuration is Feisty + Xgl + Compiz Fusion. My previous
>  configuration was Edgy + Xgl + Beryl, where this didn't happen.  
> Others
>  have reported the same problem without using either Xgl or Compiz.
>
>  The keyboard itself isn't the problem. When dual-booting to Windows,
>  everything works fine. Also, the problem happens with two different
>  keyboards (internal laptop, external USB).
>
>  My best guess is that the problem occurs at time of high system load.
>  Somehow during these times the key-release signal gets lost and the
>  key-press is repeated indefinitely. This happens more often with
>  Compiz configurations because Compiz tends to increase system load.  
> It
>  also happens more often with power-hungry apps like Firefox and
>  Acrobat Reader for similar reasons.
>
>  PS: When the keys would repeat all input devices would be locked up.
>  ie. mouse won't move, clicks don't do anything, keyboard presses  
> don't
>  register. Then when it becomes unstuck, the mouse moves around and
>  everything. Hope this helps.
>
>  See also this forum thread for other people with the same problem:
>  http://ubuntuforums.org/showthread.php?t=432057

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/124406

Title:
  Keyboard keys get stuck and repeat

To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/124406/+subscriptions