I concluded that the description was related to the use of the
us+dvorak-alt-intl layout, and not to g-c-c setting incorrect options.
Observations from use of the us+intl layout:
Alternate Characters Key to None
--------------------------------
$ gsettings get org.gnome.desktop.input-sources xkb-options
['lv3:ralt_alt']
Right Alt according to xev: Alt_R
Alternate Characters Key to None + Compose key to Right Ctrl
------------------------------------------------------------
$ gsettings get org.gnome.desktop.input-sources xkb-options
['lv3:ralt_alt', 'compose:rctrl']
Right Alt according to xev: Alt_R
Right Ctrl according to xev: Multi_key
Alternate Charters Key to None + Compose key to Right Alt
---------------------------------------------------------
$ gsettings get org.gnome.desktop.input-sources xkb-options
['lv3:ralt_alt', 'compose:ralt']
Right Alt according to xev: Multi_key
I see only expected options and expected results. So please elaborate on
how you think that g-c-c behaves incorrectly, preferably with a
reproducible use case.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1969396
Title:
Can't use Right Alt as compose key with English (Dvorak, alt. intl.)
layout
Status in gnome-control-center package in Ubuntu:
Incomplete
Status in xkeyboard-config package in Ubuntu:
Confirmed
Bug description:
I noticed after upgrade from impish to jammy that my compose key is
not working correctly.
Going into gnome-control-center -> Keyboard, I see that 'Alternate
Characters Key' and 'Compose Key' are both set to Right Alt.
Setting Alternate Characters Key to None, and moving the Compose Key
setting around between different options (and then back to Right Alt),
the behavior of the Right Alt key is still AltGr and not Compose.
From xev:
KeyPress event, serial 37, synthetic NO, window 0x4000001,
root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617),
state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 37, synthetic NO, window 0x4000001,
root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617),
state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen
YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XFilterEvent returns: False
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-control-center 1:41.4-1ubuntu12
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon
znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 18 16:01:10 2022
InstallationDate: Installed on 2019-12-23 (847 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
