Bug 8572

Summary:	ISO_Level3_Shift bound to Mod1 and Mod5 with lv3:lalt_switch
Product:	xkeyboard-config	Reporter:	Denis Barbier <barbier>
Component:	doc	Assignee:	xkb
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	high
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	Suggested fix

Description Denis Barbier 2006-10-09 13:21:55 UTC

Hi,

there is another bug reported in
  http://lists.debian.org/debian-powerpc/2006/10/msg00117.html
namely that ISO_Level3_Shift is bound to Mod1 and Mod5 with
lv3:lalt_switch.
I believe that the attached patch fixes it.

Comment 1 Denis Barbier 2006-10-09 13:22:44 UTC

Created attachment 7310 [details] [review]
Suggested fix

Comment 2 Sergey V. Udaltsov 2006-10-09 14:30:50 UTC

This patch looks safe enough (and I will apply it) - but I am not convinced it
is going to help... Well, if it does - I'm happy.

Comment 3 Sergey V. Udaltsov 2006-10-09 14:35:13 UTC

Committed anyway.

Comment 4 Denis Barbier 2006-10-09 14:38:26 UTC

Sergey, you can easily test it: without the patch
  $ setxkbmap -layout us -option -option lv3:lalt_switch
  $ xmodmap -pm
  shift       Shift_L (0x32),  Shift_R (0x3e)
  lock        Caps_Lock (0x42)
  control     Control_L (0x25),  Control_R (0x6d)
  mod1        ISO_Level3_Shift (0x40),  Alt_L (0x7d),  Meta_L (0x9c)
  mod2        Num_Lock (0x4d)
  mod3
  mod4        Super_L (0x7f),  Hyper_L (0x80)
  mod5        ISO_Level3_Shift (0x40),  Mode_switch (0x5d),  ISO_Level3_Shift
(0x7c)
Then 3rd and 4th levels cannot be accessed within emacs.

Comment 5 Denis Barbier 2006-10-09 14:43:50 UTC

Sergey, the hidden attribute has been dropped by this patch for
symbols/level3(enter_switch), sorry.

Comment 6 Sergey V. Udaltsov 2006-10-09 14:51:34 UTC

Arrgh, emacs and other non-xkb-ers always get better of me. I just hate it;)
I'll fix the attribute think, no worries.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.