#696651 doesn't load saved XKBOPTIONS

Package:
gdm3
Source:
gdm3
Description:
GNOME Display Manager
Submitter:
Date:
2012-12-25 17:03:06 UTC
Severity:
normal
#696651#5
Date:
2012-12-25 07:43:18 UTC
From:
To:
Hello,

today I had to write some "Merry Christmas" messages to my Esperantists friends
and.. I found out that my Multi_key didn't work anymore!

It is correctly set in /etc/default/keyboard (compose:rwin) -- and in fact
it worked, I hadn't changed anything -- but xev revealed that rwin actually
triggered:

  state 0x0, keycode 133 (keysym 0xffeb, Super_L), same_screen YES,

instead of the expected:

  state 0x40, keycode 133 (keysym 0xff20, Multi_key), same_screen YES,

After putting "keycode 133 = Multi_key" in ~/.xmodmap, and loading it, it
started working again, and xev shows the correct key being input.

I'm not sure whether this is the correct package to file this bug against,
please reassign as appropriate.

Dankegon,
David
#696651#10
Date:
2012-12-25 09:41:15 UTC
From:
To:
I don't think it's a bug in keyboard-configuration that its settings get
overridden by your desktop's.  Which is what I think happened here.

Cheers,
Julien
#696651#15
Date:
2012-12-25 09:59:21 UTC
From:
To:
I'm using XFCE, and it doesn't have a setting for Multi_key. It just uses X's,
AFAIK.

Kindly,
David
#696651#20
Date:
2012-12-25 13:34:01 UTC
From:
To:
David Paleino <dapal@debian.org> (25/12/2012):

What's your display manager, what's the output of “setxkbmap -print”
without the xmodmap thing in Xfce, and what's the output of the same
command in a bare X session (no X, no display manager, e.g. using:
startx /usr/bin/xterm -- :1)?

Mraw,
KiBi.
#696651#25
Date:
2012-12-25 16:59:49 UTC
From:
To:
reassign 696651 gdm3
found 696651 gdm3/3.6.1-2
thanks

Ah, there you go!

I used gdm3, and here's the output of setxkbmap -print:

xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+it+us:2+inet(evdev)"	};
	xkb_geometry  { include "pc(pc105)"	};
};

Then I switched to lightdm, and there you go:

xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include
"pc+it+inet(evdev)+level3(ralt_switch)+compose(lwin)+terminate(ctrl_alt_bksp)"	};
xkb_geometry  { include "pc(pc105)"	};
};

A bare X session, using xterm, also gives this last one output.
I guess the culprit is gdm3/experimental (which I was using) here -- bug
reassigned.

Thanks for your help,
David