Your message dated Tue, 29 Aug 2023 13:26:31 +0200 with message-id <[email protected]> and subject line Re: Bug#1040802: xkb-data: Breaks altgr in Norwegian layout has caused the Debian Bug report #1040802, regarding xkb-data: Breaks altgr in Norwegian layout 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.) -- 1040802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040802 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: xkb-data Version: 2.38-2 Severity: serious Justification: makes a subset of systems effectively unusable X-Debbugs-Cc: none, Tollef Fog Heen <[email protected]> With commit 0fb34101788d84e9a1d98b3730cc7b9295e0f19b in xkeyboard-config, `group(alts_toggle)` changed behaviour in a way such that the right alt no longer generates altgr. This is very problematic with keyboard layouts such as Norwegian where that is required to type @ (altgr-2) or $ (altgr-4). setxkmap no -print on my system outputs: xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+no+inet(evdev)+level3(ralt_switch)+compose(caps)+group(alts_toggle)" }; xkb_geometry { include "pc(pc105)" }; }; which includes the problematic toggle. I don't know if the right fix is to revert the relevant commit (reintroducing the problem in https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/316) or something else, but the current way it works is not great. Happy to help debug this further, let me know what I can provide. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
--- End Message ---
--- Begin Message --- Closing this bug, since the problem apparently was related to the user configuration.
--- End Message ---
