Bug 415995 - Cannot assign dead keys as global shortcuts
Summary: Cannot assign dead keys as global shortcuts
Status: RESOLVED UPSTREAM
Alias: None
Product: frameworks-kglobalaccel
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.64.0
Platform: Other Linux
: HI normal
Target Milestone: ---
Assignee: kdelibs bugs
URL: https://codereview.qt-project.org/c/q...
Keywords:
: 385823 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-01-08 10:59 UTC by Dennis Lichtenthäler
Modified: 2024-01-10 16:53 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In: Qt 6.6.0


Attachments
resulting shortcut after typing CTRL+circumflex (14.39 KB, image/png)
2020-01-08 10:59 UTC, Dennis Lichtenthäler
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Lichtenthäler 2020-01-08 10:59:21 UTC
SUMMARY
I installed yakuake and tried to set CTRL+circumflex as its global shortcut. When using the default German keyboard layout, it results in a weird, nonprintable character being set as the shortcut (I'll attach a screenshot) and the shortcut subsequently doesn't work.
If I switch the keyboard layout to the nodeadkeys variant, it works as expected but I lose the ability to type accented characters.

SOFTWARE/OS VERSIONS
Gentoo Linux
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version:  5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2
Comment 1 Dennis Lichtenthäler 2020-01-08 10:59:51 UTC
Created attachment 124966 [details]
resulting shortcut after typing CTRL+circumflex
Comment 2 Nate Graham 2020-05-07 14:33:17 UTC
*** Bug 420866 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2020-05-08 12:02:15 UTC
*** Bug 385823 has been marked as a duplicate of this bug. ***
Comment 4 Ahmed Z 2020-07-13 10:05:42 UTC
Hi,

I have a similar problem and did not want to create a duplicate.

I have a belgian keyboard and when I try to set Meta+é to move to virtual desktop 2. (you can see the layout on Wikipedia https://fr.wikipedia.org/wiki/Fichier:Belgian_keyboard_layout.png the button "é" is above A and Z)

It displays it as Meta+É (capital version).

I tried to use the shortcut and it is not detected even if I activate the caps lock to enter Meta+É.

(About System)
Operating System: Fedora 31
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.13.2
Kernel Version: 5.6.19-200.fc31.x86_64
OS Type: 64-bit


(About Kde in settings)
Version: 5.17.5
KDE Frameworks 5.70.0
Qt 5.13.2 (construit sur 5.13.2)
Le système de fenêtres xcb
Comment 5 Jeffrey Bouter 2020-07-22 11:23:37 UTC
The same seems to happen (on a 'regular' keyboard) when trying to set a shortcut that involves alt and shift.

E.g., I've set alt+shift+4 as my "Capture Entire Desktop", as this is the default on the Apple keyboard layout (and my mechanical keyboard mimics this keyboard shortcut on the screenshot button). It will show as Alt-Shift-$ in the settings, not react to the key being pressed at all.
Comment 6 Johannes 2022-01-09 18:28:04 UTC
I have the same issue. I wanted to do Alt+Shift+4 (actually Alt+Shift+ç) to move a window to the 4th virtual desktop, and this does not work. However, Alt+Shift+3 (actually Alt+Shift+*) works. I have done some research and it appears that it is all the keyboard shortcuts that involve accented chars. It does not have anything to do with the Alt+Shift combination, as Ctrl+é wouldn't work either.

Please fix that soon: on keyboard layouts that have many accented chars (due to the language), it makes annoyingly many keys that cannot be used for shortcuts.....
Comment 7 Johannes 2022-01-25 10:05:19 UTC
I have done some more research.

Ctrl+@, Ctrl+{, Ctrl+|, Ctrl+backslash, Ctrl+[, Ctrl+$, Ctrl+£, Ctrl+é, Ctrl+Shift+É, Alt+é, Alt+Shift+É all DON'T WORK when set from systemsettings. Tested both on my Swiss layout and a standard US layout.

On the contrary, Ctrl+*, Ctrl+", Ctrl+Shift+% do work.

An interesting point is that Ctrl+[ and Ctrl+] are attributed by default (it switches tabs). And in the default usage, they do work. But as soon as you try to re-attribute them in systemsettings, they don't work any more. 
The latter may be an interesting finding because it means that all these shortcuts **can** actually work, but perhaps the way they are registered when the user sets them is broken. All those shortcuts also work when you set them within an app; for instance, Ctrl+é works in Dolphin.  I tested all these on GNOME, both on X11 and Wayland, and there they work. 

Therefore, I believe that KDE only currently allows to set alphanumerical keys + a few others. It does not even have something to do with ASCII versus extended ASCII or UTF-8. Just possibly a bug in systemsettings.

This bug's title is thus not to the point. We should rename it to "Cannot assign global shortcuts using most keys besides A-Za-z0-9 and few others". 

Note that setting global keyboard shortcuts is typically what I do in the first 15 minutes after installing a distro, and my keyboard layout being not american, it has plenty of accented keys; this should thus be a priority in the sense of the "15-Minute Bug Initiative".
Comment 8 Johannes 2022-01-25 10:07:34 UTC
PS, I am not a developer, I cannot code a fix myself. Is there someone who can?
Comment 9 Andrey 2022-11-22 11:10:21 UTC
Does it work for wayland with KDE Qt patch collection?
Comment 10 Bug Janitor Service 2022-12-07 05:12:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Andrey 2022-12-07 09:59:45 UTC
(In reply to Andrey from comment #9)
> Does it work for wayland with KDE Qt patch collection?
Please note some distros apply the KDE Qt patches just partially. You have to make sure you have the patch needed in the first place: 
https://salsa.debian.org/qt-kde-team/qt/qtwayland/-/merge_requests/5#note_358911
Comment 12 Andrey 2022-12-08 15:58:07 UTC
For the dead keys, the fix is the same as for BUG 453661 and pending:
https://bugreports.qt.io/browse/QTBUG-108761

For other keys, the fix is already there, check your Qt:
https://bugreports.qt.io/browse/QTBUG-90611
Comment 13 Bug Janitor Service 2022-12-23 05:23:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 14 Bug Janitor Service 2023-01-07 05:26:00 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 15 Andrey 2023-02-03 18:04:13 UTC
(In reply to Dennis Lichtenthäler from comment #0)
> SUMMARY
> I installed yakuake and tried to set CTRL+circumflex as its global shortcut.
> When using the default German keyboard layout, it results in a weird,
> nonprintable character being set as the shortcut (I'll attach a screenshot)
> and the shortcut subsequently doesn't work.

Does German layout is the only layout configured in your system?
Comment 16 Andrey 2023-02-03 18:06:17 UTC
.
Comment 17 Dennis Lichtenthäler 2023-02-03 18:13:49 UTC
(In reply to Andrey from comment #15)
> Does German layout is the only layout configured in your system?

Yes, German was the only keyboard layout set.
Comment 18 Andrey 2023-02-03 18:20:04 UTC
Thanks.
FYI, you could workaround it by providing additional layout without dead keys.
That would work regardless actual layout currently in use, but needs Qt 6.6.0 as said in BUG 453661 (until we didn't backport the fix).
Comment 19 Andrey 2023-02-17 20:34:44 UTC
Originally reported problem will be fixed upstream as soon as https://codereview.qt-project.org/c/qt/qtbase/+/460924 is merged.
If others who reported here still experience their issues, please let me know.
It might be already fixed but just didn't arrive to the end users yet.
Comment 20 nathan67003 2024-01-06 02:59:21 UTC
I am *quite* uncertain where to ask this,
Comment 21 nathan67003 2024-01-06 03:01:43 UTC
I am *quite* uncertain where to ask this (please pardon my inexperience digging through bug databases) but it appears that, at first glance, this bug has been fixed. Is there any word on if the fix will be backported to the versions of the products used by Kubuntu 22.04 LTS?
Comment 22 Andrey 2024-01-06 15:11:46 UTC
(In reply to Andrey from comment #19)
> Originally reported problem will be fixed upstream as soon as
> https://codereview.qt-project.org/c/qt/qtbase/+/460924 is merged.
This should be merged.