New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shift button does not work as expected #113
Comments
Also |
I hope you managed to solve this issue. Tried to reproduce it on Linux Mint 19.3 Cinnamon with your steps but the issue doesn't happen here. Closing this here also considering its age. If you still have this issue you can reopen this issue. Please then add your current Linux Mint version and desktop environment. |
To reopen should I create new one or just write here? Problem still exists on Linux Mint 19.3
|
Task back switching hot key also still does not work: |
I meant are you using Cinnamon, MATE or Xfce. |
Cinammon |
Did you mean in your first post with "For example change keyboard layout: SHIFT+ALT" that you set the keyboard shortcut for changing keyboard layout to just modifier keys shift+alt? As a test I set the keyboard shortcut to launch the terminal to shift+alt. If I press alt first then shift, hold both down, then also press tab, a terminal opens after pressing down shift and the task list pops up when hitting tab and starts moving in reverse on hitting tab again. So that triggers both shortcuts. If I first press shift then alt, the terminal doesn't pop up and task list works as expected. If I press alt + shift + tab at exactly the same time then hold down alt + shift a terminal also doesn't pop up and task list works as expected. This is the same across Linux Mint 19.3 Cinnamon and Xfce. MATE won't let users set a shortcut of just modifier keys. I can't say if this worked differently on 18.3 but I think this should be expected behavior. I mean, when you set the shortcut for something to just modifier keys shift+alt, any other keyboard shortcut including those modifier keys will also trigger that shortcut if you don't press the non-modifier key of the other keyboard shortcut at exactly the same time. Several workarounds:
|
At 17.3 Cinnamon that works without any workaround. |
For point 1, I didn't know that option was there. Thanks for showing where to find it. With that I was also able to reproduce the issue on Linux Mint 19.3 MATE. So this doesn't look to be tied to desktop environment but probably X server (which is common across all three). For point 2, that's also unassigned here in 19.3 Cinnamon. If I set the layout switch to Alt+Shift as you showed where to do the workaround I mentioned before doesn't work. Whether I press Alt+Shift at same time, Alt first then Shift or Shift then Alt, the layout is always switched regardless of at same time or afterwards pressing Tab. I further tried to reproduce this on a different distro, using Gnome 3.34. Sorry to report but setting layout switcher to Alt+Shift there in the same layout options menu also break Shift+Alt+Tab and I can no longer cycle backwards through open windows with that set (unsetting a shortcut for layout switcher make cycle backwards work again). Back to Linux Mint 19.3 Cinnamon: I could set a different shortcut for cycle backwards. I set cycle to Ctrl+Tab, cycle backwards to Shift+Ctrl+Tab and layout switch to Alt+Shift and that plays nice together. I get that you want it to work like it did on 17.3 but this is not something that can be fixed here, if it can be fixed at all. It not working as you say it did before is not due to change in desktop environment but some other underlying component. X server seems likely. |
Probably this issue should be cross reported to |
Now I've got exactly the same issue but with Alt+Shift. Shift+Alt works fine, but it really is uncomfortable. |
When I upgrade from 18.3 to 19.1 and use combinations of keys SHIFT + ...
For example change keyboard layout: SHIFT+ALT
shift is not taken into account when typing.
How to reproduce:
:
, but instead you get;
(unexpected)D
, but instead you getd
(unexpected)D
Now it is as expected.The text was updated successfully, but these errors were encountered: