Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#78779 - [xkeyboard-config] Shift+letter not working with shift:both_capslock option
Attached to Project:
Arch Linux
Opened by Christoffer (Brott) - Wednesday, 14 June 2023, 19:31 GMT
Last edited by Toolybird (Toolybird) - Friday, 16 June 2023, 21:33 GMT
Opened by Christoffer (Brott) - Wednesday, 14 June 2023, 19:31 GMT
Last edited by Toolybird (Toolybird) - Friday, 16 June 2023, 21:33 GMT
|
DetailsDescription: Using the x11-keymap-options shift:both_capslock in 2.39 breaks the functionality where you hold right shift to write uppercase letters.
I disable caps lock with caps:none, and instead use shift:both_capslock, but this makes it so holding right shift to write uppercase letters do not work. Writing special symbols work fine, it's just the uppercase letters that do not work. It is also worth to note that in the previous version, 2.38, using rp:lalt_lshift_toggle option, lalt+lshift stopped working, but the reverse worked (lshift+lalt), and the 2.39 fixed that. But introduced the issue with shift:both_capslock. Additional info: * package version(s): 2.39 * config and/or log files etc.: attached * link to upstream bug report, if any Steps to reproduce: Use shift:both_capslock option. Upgrade to 2.39. Restart X. Hold right shift key to write uppercase letters, it will not work. Please let me know if I need to report this upstream instead. 
00-keyboard.conf
(0.4 KiB)
|
This task depends upon
Closed by Toolybird (Toolybird)
Friday, 16 June 2023, 21:33 GMT
Reason for closing: Upstream
Additional comments about closing: "I think this should be closed. Reading the upstream bug report, it is clear this is an intentional change which may or may not have unintended consequences. Two of my options want to take control over the same key, which is one of the issues."
Friday, 16 June 2023, 21:33 GMT
Reason for closing: Upstream
Additional comments about closing: "I think this should be closed. Reading the upstream bug report, it is clear this is an intentional change which may or may not have unintended consequences. Two of my options want to take control over the same key, which is one of the issues."
Comment by Andreas Radke (AndyRTR) -
Wednesday, 14 June 2023, 20:59 GMT
Yes, please report it upstream.
Comment by Christoffer (Brott) -
Thursday, 15 June 2023, 17:09 GMT
For reference, a bug report has been made: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/393