Hi, using Buster, I have my /etc/default/keyboard set up like this: XKBOPTIONS="pc105" XKBLAYOUT="gb" XKBOPTIONS="ctrl:nocaps" BACKSPACE="guess" XKBVARIANT=""
I am using Fluxbox without any configuration. When I launch Fluxbox through GDM, my keyboard layout does not get applied. Inside fluxbox, in a terminal I run "setxkbmap -query": rules: evdev model: pc105 layout: us options: ctrl:nocaps As you can see, the XKBOPTIONS have been applied, but somehow the layout has not been applied, or has been overwritten. If I run "setxkbmap gb", the correct layout is applied for that X session. However, putting that command into .xsessionrc does NOT work -- even with that command in .xsessionrc, the layout is still 'us' after Fluxbox login. This behaviour is not restricted to gdm, it happens identically in slim and lightdm as well. However, this does NOT happen when I remove all display managers and use startx directly. When using startx, the correct keyboard layout is used. (No extra setxkbmap call is needed in .xinitrc, either, the settings from /etc/default/keyboard are working as expected). What could be the problem here? If this is a bug, it's difficult to know what it's even a bug with -- I can't identify a specific package that has the problem. It's not a problem with Fluxbox, either, because I get identical behaviour when using different WMs such as Xmonad. Thanks! -- David Banks <amoe...@gmail.com>