http://bugs.winehq.org/show_bug.cgi?id=34485
Bug #: 34485 Summary: Sticky modifier keys Product: Wine Version: 1.7.0 Platform: arm64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winex11.drv AssignedTo: wine-bugs@winehq.org ReportedBy: sprog@online.ru Classification: Unclassified
From time to time the modifier keys are sticking in applications run by wine.
The problem follows the same pattern:
shift ctl or alt keys are getting stuck, to un-stuck them you have to press them again. It usually happens with Ctl and Alt keys.
It might have something to do with keyboard layouts changes.
The problem is there starting from wine 1.3, and it's still there with 1.7
http://bugs.winehq.org/show_bug.cgi?id=34485
--- Comment #1 from Igor Franchuk sprog@online.ru 2013-09-11 04:40:05 CDT --- I meant from wine 1.4, 1.3 was the last version of wine which worked with modifier keys well. Sorry.
http://bugs.winehq.org/show_bug.cgi?id=34485
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
--- Comment #2 from Austin English austinenglish@gmail.com 2013-09-11 12:39:01 CDT --- (In reply to comment #1)
I meant from wine 1.4, 1.3 was the last version of wine which worked with modifier keys well. Sorry.
Please run a regression test: http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=34485
--- Comment #3 from Igor Franchuk sprog@online.ru 2013-09-11 14:08:46 CDT --- I would love to be of assistance, but shortly after winetest64-latest.exe showed 5 failed test (about 30% of the progress bar) first KDE's KWIN 4.10.5 hung and then the linux box become unresponsive and I got to power it off. I'm running Gentoo amd64 with Preemptible Kernel. The system failure occurred shortly after d3d tests.
I'm not clear how to use regression tests to determine the problem with the sticky key.
Returning to the sticky meta keys the problem follows the pattern:
1. It always happens when a lot of applications are running, i.e. many tabs in a navigator, libre office, many, about 90 instances of different applications. (system load should be high)
2. If I'm connected to the linux box with XRDP - the problem occurs much more often.
3. It never happened with 1.3 but always happened with all the following releases
4. When meta key is stuck - native linux applications are not affected.
5. It looks like the problem has something to do with the language switch which is on Ctrl+Shift in my case. And Ctrl is the key that sticks most of the time.
KDE in my case is configured to keep individual language settings for each application running.
I understand this is not much, but may be someday it help to understand what's going on. It has something to do with the key press/release events, like release is lost by some reason.
Thanks a lot for all the hard work you do on WINE, it's a miracle what WINE can already do. This is the kind of application linux world needed the most.
(In reply to comment #2)
(In reply to comment #1)
I meant from wine 1.4, 1.3 was the last version of wine which worked with modifier keys well. Sorry.
Please run a regression test: http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=34485
--- Comment #4 from Austin English austinenglish@gmail.com 2013-09-11 17:32:54 CDT --- You don't need to run the wine unit tests to do a regression test. A regression test rebuilds wine several times to do a binary search for the problematic change that introduced your bug.
Please use the forums for help in running it.
http://bugs.winehq.org/show_bug.cgi?id=34485
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de Platform|arm64 |x86-64
https://bugs.winehq.org/show_bug.cgi?id=34485
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #5 from Austin English austinenglish@gmail.com --- (In reply to Austin English from comment #4)
You don't need to run the wine unit tests to do a regression test. A regression test rebuilds wine several times to do a binary search for the problematic change that introduced your bug.
Please use the forums for help in running it.
Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=34485
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Austin English austinenglish@gmail.com --- Closing.