You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have posted the following issue to MATE and later found out that this is caused by mintmenu:
I have noticed an issue that some of my keyboard shortcuts do not always register. I use two keyboard layouts that I switch between and I found out that it only happens when I'm switched to the other keyboard layout and when the shortcut uses super as a modifier.
I thought that the particular layout might be the issue, but I have tested that this happens regardless of what the other layout is. The only thing that matters is the index of the layout in the layouts dialog. The shortcuts work when the layout in use is the layout that's listed on the first position in the layouts dialog. If the selected layout is a layout that is listed second, third, ... in the list of layouts, the keyboard shortcuts do not work. If I move the layout to the top, the shortcuts start working on that layout and stop working on the one that is now second.
I also thought that the issue might have something to do with using Super+Space as the key combination to switch layouts, but I have tried other combinations and this happens regardless.
Expected behaviour
Keyboard shortcuts using Super as a modifier work regardless of the chosen layout
Actual behaviour
Keyboard shortcuts using Super as a modifier only work if the selected layout is listed on the first place in the keyboard layouts dialog
Steps to reproduce the behaviour
Have a keyboard shortcut that uses Super as a modifier, for example Super+Up to maximize a window
Open Keyboard preferences and navigate to the Layouts dialog
Add another layout to have at least two, for example English and German, such that English is listed first and German second
Switch to English layout
Pressing Super+Up maximizes the window as intended
Switch to German layout
Pressing Super+Up does nothing
Now use the 'Move up' button to reorder the layouts such that German is listed first and English second
Switch to German layout
Pressing Super+Up maximizes the window as intended
Switch to English layout
Pressing Super+Up does nothing
MATE general version
MATE 1.24.0
Package version
1.24.0-2 (mintmenu version is 6.1.4)
Linux Distribution
Linux Mint MATE 20.2 Uma, but had the same issue in 20.1
The text was updated successfully, but these errors were encountered:
I have posted the following issue to MATE and later found out that this is caused by mintmenu:
I have noticed an issue that some of my keyboard shortcuts do not always register. I use two keyboard layouts that I switch between and I found out that it only happens when I'm switched to the other keyboard layout and when the shortcut uses super as a modifier.
I thought that the particular layout might be the issue, but I have tested that this happens regardless of what the other layout is. The only thing that matters is the index of the layout in the layouts dialog. The shortcuts work when the layout in use is the layout that's listed on the first position in the layouts dialog. If the selected layout is a layout that is listed second, third, ... in the list of layouts, the keyboard shortcuts do not work. If I move the layout to the top, the shortcuts start working on that layout and stop working on the one that is now second.
I also thought that the issue might have something to do with using Super+Space as the key combination to switch layouts, but I have tried other combinations and this happens regardless.
Expected behaviour
Keyboard shortcuts using Super as a modifier work regardless of the chosen layout
Actual behaviour
Keyboard shortcuts using Super as a modifier only work if the selected layout is listed on the first place in the keyboard layouts dialog
Steps to reproduce the behaviour
MATE general version
MATE 1.24.0
Package version
1.24.0-2 (mintmenu version is 6.1.4)
Linux Distribution
Linux Mint MATE 20.2 Uma, but had the same issue in 20.1
The text was updated successfully, but these errors were encountered: