Your message dated Mon, 6 Mar 2023 15:26:24 +0100
with message-id <[email protected]>
and subject line Re: Bug#1032347: gnome-control-center: Keyboard settings:
disabling the 'Compose Key' is not persisted in user dconf settings
has caused the Debian Bug report #1032347,
regarding gnome-control-center: Keyboard settings: disabling the 'Compose Key'
is not persisted in user dconf settings
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1032347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032347
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-control-center
Version: 1:43.4.1-1
Severity: normal
Dear Maintainer,
The 'Keyboard' panel in gnome-control-center allows configuration of 'Special
Character Entry' keys, and on my system this currently displays two entries:
- Alternative Characters Key (value: Disabled)
- Compose Key (value: Left Super)
Updating these values takes effect during the current gnome-shell session, and
when the keys are given assignments, those assignments are correctly persisted
across sessions.
However: in the particular case of disabling the 'Compose Key' (which has a
non-empty default), the setting is not persisted.
To explain another way: although disabling the 'Compose Key' using the keyboard
panel takes effect in the current session, it is restored to the default value
('Left Super' in this case) after the user logs out and logs back in.
This seems to be because when the 'Compose Key' is disabled, there is no
configuration entry for it written to the user's relevant dconf entry, which
is '/org/gnome/desktop/input-sources/xkb-options'.
As a workaround it is possible to use the 'dconf' command-line interface to
configure an empty mapping for the compose key:
$ dconf write /org/gnome/desktop/input-sources/xkb-options "['compose:none']"
This may be an upstream issue and I plan to report it there if & when it is
confirmed.
Thanks,
James
--- End Message ---
--- Begin Message ---
On 2023-03-06 14:56, James Addison wrote:
On Mon, 6 Mar 2023 13:40:30 +0100, Gunnar wrote:
So what is it on your system which causes 'compose:lwin' to be set
behind the scenes? Since I can't reproduce the issue, I doubt it
is gnome-control-center.
Thanks for reconfirming. I now believe (and have updated upstream)
that the cause was a 'XKBOPTIONS="compose:lwin"' entry in the
'/etc/default/keyboard' file.
Thanks for letting us know that. And as far as I know that's expected
behavior, i.e. if you set XKBOPTIONS in /etc/default/keyboard, the
values are automatically imported (by something...) to the user dconf
file at login.
Removing the XKBOPTIONS line produces the results I expected:
disabling the compose key takes effect within both the current
session and subsequent GNOME login sessions.
I'll continue to investigate the cause;
At some point of time, when configuring the keyboard configuration on
the system level, you apparently set that value. To see how it could
happen, you can run:
sudo dpkg-reconfigure keyboard-configuration
it is OK to close this bug if you like.
Done.
--
Cheers,
Gunnar
--- End Message ---
