[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#241537: xlibs: AltGr (AltRight) no longer recognized in many apps since upgrade to 4.3 from 4.2



Package: xlibs
Version: 4.3.0-7
Severity: normal

I'm runinng a Debian/Testing system as an X client.  As the X server, I
use Hummingbird Exceed 7.1 on a Win32 machine.

When I recently updated my X packages (mainly xlibs, xfree86-common, and
some X libs, I'm not using xserver-xfree86, as I'm using a separate X
server, see above) from 4.2 (don't remember the exact version) to
4.3.0-7 a few days ago, I suddenly lost the ability to use the AltGr
(AltRight) key in Mozilla and all Gnome apps I have tested.  But it
still works in XTerm, XEmacs, and all KDE apps I have tested, including
Konsole.  Alt (AltLeft) works nicely everywhere.

As a result, I cannot type some special characters on my German
keyboard in the affacted apps:  @, €, {, [, ], }, \, ~, |

As the only possibly relevant Gnome-related packages that I had upgraded
at the same time is gnome-session, I seriously doubt that it is a Gnome-
specific problem.

Within the X conglomerate, xlibs was the most relevant package I could
find, so I'm filing this bug report against xlibs in the hope that this
is correct.

I have only read bugs of the xfree86 source package that apply to at
least version 4.3.  My problem seems to be most similar to the following
bugs:

  * 234113: xlibs or xkb: no more pipe, tilde, ... (alt-gr ?) on ibook
  * 240351: xserver-xfree86: Alt-Gr does not work anymore

Running `xev` and pressing and releasing the AltGr key says:

| KeyPress event, serial 23, synthetic NO, window 0x5800001,
|     root 0x2b, subw 0x0, time 13602741, (863,943), root:(867,963),
|     state 0x0, keycode 97 (keysym 0xff7e, Mode_switch), same_screen YES,
|     XLookupString gives 0 bytes:  ""
|
| KeyRelease event, serial 23, synthetic NO, window 0x5800001,
|     root 0x2b, subw 0x0, time 13602814, (863,943), root:(867,963),
|     state 0x20, keycode 97 (keysym 0xff7e, Mode_switch), same_screen YES,
|     XLookupString gives 0 bytes:  ""

Running `setxkbmap -print` says (nova.mehnle.net being the Win32
machine running Hummingbird Exceed):

| XKB extension not present on nova.mehnle.net:0

Running `xkbwatch` says:

| Fatal Error:      Server doesn't support a compatible XKB
|                   Exiting

This is probably due to Hummingbird Exceed not supporting any XKB stuff.

It all worked fine before the update from 4.2 to 4.3, and I'm at a total
loss as to the problem's possible reason.  If you need any additional
data, feel free to ask!


-- Package-specific info:
No XFree86 X server log files found.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (600, 'testing'), (90, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

Versions of packages xlibs depends on:
ii  libice6                       4.3.0-7    Inter-Client Exchange library
ii  libsm6                        4.3.0-7    X Window System Session Management
ii  libx11-6                      4.3.0-7    X Window System protocol client li
ii  libxext6                      4.3.0-7    X Window System miscellaneous exte
ii  libxft1                       4.3.0-7    FreeType-based font drawing librar
ii  libxi6                        4.3.0-7    X Window System Input extension li
ii  libxmu6                       4.3.0-7    X Window System miscellaneous util
ii  libxmuu1                      4.3.0-7    lightweight X Window System miscel
ii  libxp6                        4.3.0-7    X Window System printing extension
ii  libxpm4                       4.3.0-7    X pixmap library
ii  libxrandr2                    4.3.0-7    X Window System Resize, Rotate and
ii  libxt6                        4.3.0-7    X Toolkit Intrinsics
ii  libxtrap6                     4.3.0-7    X Window System protocol-trapping
ii  libxtst6                      4.3.0-7    X Window System event recording an
ii  xlibs-data                    4.3.0-7    X Window System client data

-- no debconf information



Reply to: