Bug 391469 - ctrl problem
Summary: ctrl problem
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.12.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-06 15:38 UTC by dutchkind
Modified: 2021-03-19 23:59 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dutchkind 2018-03-06 15:38:54 UTC
Ever since the upgrade from kde4 to plasma 5 I have this weird ctrl key problem. On my wife's desktop the ctrl key is often activated without touching it resulting in zooming in or out of web pages, unwanted pasting and many other ctrl related stuff. I replaced the keyboard for a new one but it is still doing it.

On both my own laptop I noticed that the ctrl would behave in a reversed way from the desktop; very often it is not detected, so for locking my screen for example I have to hit often ctrl-alt-L a few times before the screen locks.

I don't know if anybody else has experienced this and was reluctant to report this because it is such a vague thing, hardly repeatable, because it is not all  the time. But what I do know is that before plasma 5 I never had this problem and would appreciate a fix.

I switched of ctrl-scroll zoom in firefox but couldn't find a way to switch this off for everything. Any help appreciated.
Comment 1 Christoph Feck 2018-03-30 12:18:42 UTC
Could you please test with 'xev' if the key is indeed working reliably?
Comment 2 dutchkind 2018-03-30 14:12:17 UTC
I tested with xev and it consistently shows the correct key press and release.

Btw, when it all started I bought a new keyboard of a well-known brand and the same problem persisted, so this xev output doesn't surprise me, it must be somewhere else having to do with the way plasma receives the key input
Comment 3 Justin Zobel 2020-11-30 00:53:59 UTC
Thanks for the report. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 4 dutchkind 2020-12-01 13:10:40 UTC
(In reply to Justin Zobel from comment #3)
> Thanks for the report. Can you please test and confirm if this issue is
> still occurring or if this bug report can be marked as resolved.
> 
> I've set the bug status to "needsinfo" pending your response, please change
> back to "reported" or "resolved" when you respond, thanks.

It is still showing the same problem. It is kind of weird because it only happens on that desktop, other laptops with Opensuse and Plasma behave normal
Comment 5 Justin Zobel 2020-12-01 21:48:33 UTC
This one is really strange. I'm not sure where to go from here, hopefully, someone with higher technical expertise can assist.
Comment 6 David Edmundson 2020-12-01 23:35:12 UTC
Please test in openbox/gnome instead of plasma on that machine.

On X11, no plasma code is involved in getting from input events to client. Only XServer and the receiving client. At most we configure keyboard layouts. 

I can't think of anything that could be us.
Comment 7 dutchkind 2020-12-02 11:42:43 UTC
I have tried in the past with Mate desktop but since it's an older pc it's not used that much anymore and its happening only once in a while so I couldn't reproduce it just now. I would say to leave it as is, its not worth the effort to try to resolve this, maybe it was coincidence when KDE5 came around and it was cause by something else in the system. Thanks anyway.
Comment 8 Nate Graham 2021-03-19 23:59:25 UTC
You're welcome. Sorry we couldn't figure this one out. For what it's worth, I might suggest that it's a hardware problem, or at least a hardware quirk. I used to have a laptop that would do this very same thing, but with the arrow keys: one of them would sometimes become "virtually" stick in the down position until you physically pushed it. Other people online reported the same issue; it was simply a defect of the hardware.