Dear Maintainer,

   * What led up to the situation?
	Using Debian stable 13.3 with Gnome
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
	Tried to write using the keyboard
   * What was the outcome of this action?
	Caps lock inverted
   * What outcome did you expect instead?
	Caps lock not inverted

Please see
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7508
and
https://gitlab.gnome.org/GNOME/mutter/-/issues/3340
as well as multiple other places where this bug has been reported

Apparently the issue is fixed upstream, but not backported.
However, backporting is imho extremely important as this breakage requires either rebooting
or manually going through multiple menus and clicking to fix.

Please backport the fix.

Thank you

Emil

Hi

Regarding https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126010

I was given feedback on the bug at #debian@OFTC and was suggested to link
the fixing commit.

Please see https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4546 for
the fix

You can of course also see the discussion mentioned before at
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7508
https://gitlab.gnome.org/GNOME/mutter/-/issues/3340

Given the support timelines for Trixie

Version Code Name Release Date End of Life (EOL) End of LTS End of ELTS
Status
13 Trixie 2025-08-09 2028-08-09 2030-06-30 2035-06-30 Current stable release

I urge the maintainers and release team to please backport the fix.

The issue is constant and happens all the time on my laptop and doesn't
require any configuration changes: merely installing a completely stock
Debian with Gnome results in the bug appearing basically immediately, by
just for example shutting the laptop lid and putting it to my backpack and
then taking it out.

It sucks that using my laptop with Debian requires starting with fixing key
inversion.

So please, please backport the fix.

Thank you,

Emil

Hi,

I'm having this bug too due to the use of ibus, and have been very
annoyed by it for a long time.

 From a quick look at the patch, it seems not trivially backportable as
the commit fixing it in mutter is after they have introduced
clutter_keymap_get_modifier_state(), trixie has separate
clutter_keymap_get_caps_lock_state() and
clutter_keymap_get_num_lock_state() functions.

Using clutter_keymap_get_modifier_state() in turn seems to require a
dependency on libxkbcommon which probably is considered too intrusive
for a stable update.

So, best changes would be if upstream backports it to a 48.x point
release of mutter.

Regards,
Daniel