Thanks Bryce,
I did end up replacing the laptop, and it will be a little while before
I have access to the affected machine again (it now resides in the attic
at my parents' house!); however I'll be sure to file a bug report as
soon as I get there.
--
You received this bug notification because y
Well, I've just been in touch with Ajax.
I asked if he knew about any experimental thread-based branches:
"There's http://cgit.freedesktop.org/~ajax/xserver/log/?h=input-thread-v3 ,
which I haven't touched
in months. It's assuredly broken if you poke it hard enough."
I also asked if Wayland wou
In answer to post 310, Bryce, I'm sorry but there's a serious
misunderstanding of the issue in your post.
You state "hitting a key a second time (to fire a new up-key signal)
makes things work."
This is not the case for everyone affected, or for every instance of the
bug. The original poster, and
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 exper
Daniel - where you say that you can press any key to release the stuck
one - over the years the bug's behaviour has varied, in some versions of
Ubuntu I've been able to stop the repeting keypress by pressing another
key, in others not. At the moment I usually seem to be able to stop it
by pressing
This is a two-part reply to Bryce Harrington's comment #294.
1.) I really have to take issue with your statement that "it's a minor
annoyance (rather than an X lockup or crash)". When the key that gets
stuck is "Delete", for instance, this has the potential to wipe out
entire directories, and the
6 matches
Mail list logo
