Your message dated Fri, 21 May 2004 01:06:51 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#248564: xbase-clients: Alt key doesn't
work(alt-tab,ctrl-alt-f1,etc)
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 12 May 2004 02:25:49 +0000
>From [EMAIL PROTECTED] Tue May 11 19:25:49 2004
Return-path: <[EMAIL PROTECTED]>
Received: from rwcrmhc12.comcast.net [216.148.227.85]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BNjRN-0002lM-00; Tue, 11 May 2004 19:25:49 -0700
Received: from [127.0.0.1]
(pcp03723050pcs.potshe01.pa.comcast.net[68.34.173.225])
by comcast.net (rwcrmhc12) with ESMTP
id <2004051202251801400jv877e>; Wed, 12 May 2004 02:25:18 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Alexander Tait Brotman <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: xbase-clients: Alt key doesn't work(alt-tab,ctrl-alt-f1,etc)
Bcc: Alexander Tait Brotman <[EMAIL PROTECTED]>
X-Mailer: reportbug 2.58
Date: Tue, 11 May 2004 22:25:17 -0400
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.3 required=4.0 tests=BAYES_00,FORGED_YAHOO_RCVD,
HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
X-CrossAssassin-Score: 1
Package: xbase-clients
Version: 4.3.0.dfsg.1-1
Severity: normal
After upgrading today, the Alt modifier no longer seems to work. Pressing
Ctrl-Alt-F1 does not swtich to VT1, and Alt-Tab does not switch windows in
Sawfish. Ctrl-Alt-Bksp does shutdown the server. `xev` returns
XF86_Switch_VT_1 when i hit ctrl-alt-f1. I'm not sure where else to go to
figure out whats going on.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.5
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Versions of packages xbase-clients depends on:
ii cpp 4:3.3.3-2 The GNU C preprocessor (cpp)
ii libc6 2.3.2.ds1-12 GNU C Library: Shared libraries an
ii libdps1 4.3.0.dfsg.1-1 Display PostScript (DPS) client li
ii libexpat1 1.95.6-8 XML parsing C library - runtime li
ii libfontconfig1 2.2.2-2 generic font configuration library
ii libfreetype6 2.1.7-2 FreeType 2 font engine, shared lib
ii libice6 4.3.0.dfsg.1-1 Inter-Client Exchange library
ii libncurses5 5.4-3 Shared libraries for terminal hand
ii libpng12-0 1.2.5.0-6 PNG library - runtime
ii libsm6 4.3.0.dfsg.1-1 X Window System Session Management
ii libstdc++5 1:3.3.3-6 The GNU Standard C++ Library v3
ii libxaw7 4.3.0.dfsg.1-1 X Athena widget set library
ii libxcursor1 1.1.3-1 X cursor management library
ii libxext6 4.3.0.dfsg.1-1 X Window System miscellaneous exte
ii libxft2 2.1.2-6 FreeType-based font drawing librar
ii libxi6 4.3.0.dfsg.1-1 X Window System Input extension li
ii libxmu6 4.3.0.dfsg.1-1 X Window System miscellaneous util
ii libxmuu1 4.3.0.dfsg.1-1 lightweight X Window System miscel
ii libxpm4 4.3.0.dfsg.1-1 X pixmap library
ii libxrandr2 4.3.0.dfsg.1-1 X Window System Resize, Rotate and
ii libxrender1 0.8.3-7 X Rendering Extension client libra
ii libxt6 4.3.0.dfsg.1-1 X Toolkit Intrinsics
ii libxtrap6 4.3.0.dfsg.1-1 X Window System protocol-trapping
ii libxtst6 4.3.0.dfsg.1-1 X Window System event recording an
ii libxv1 4.3.0.dfsg.1-1 X Window System video extension li
ii xlibmesa-gl [libgl1] 4.3.0.dfsg.1-1 Mesa 3D graphics library [XFree86]
ii xlibmesa-glu [libglu1] 4.3.0.dfsg.1-1 Mesa OpenGL utility library [XFree
ii xlibs 4.3.0.dfsg.1-1 X Window System client libraries m
ii xlibs-data 4.3.0.dfsg.1-1 X Window System client data
ii zlib1g 1:1.2.1-5 compression library - runtime
-- no debconf information
---------------------------------------
Received: (at 248564-done) by bugs.debian.org; 21 May 2004 06:06:52 +0000
>From [EMAIL PROTECTED] Thu May 20 23:06:52 2004
Return-path: <[EMAIL PROTECTED]>
Received: from dhcp065-026-182-085.indy.rr.com (redwald.deadbeast.net)
[65.26.182.85]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BR3BE-0004Qq-00; Thu, 20 May 2004 23:06:52 -0700
Received: by redwald.deadbeast.net (Postfix, from userid 1000)
id 15F9D64375; Fri, 21 May 2004 01:06:52 -0500 (EST)
Date: Fri, 21 May 2004 01:06:51 -0500
From: Branden Robinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#248564: xbase-clients: Alt key doesn't
work(alt-tab,ctrl-alt-f1,etc)
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="JVTyp1F/hrbhzAAs"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
Mail-Copies-To: nobody
X-No-CC: I subscribe to this list; do not CC me on replies.
User-Agent: Mutt/1.5.6i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
VALID_BTS_CONTROL autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
X-CrossAssassin-Score: 2
--JVTyp1F/hrbhzAAs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
reassign 248564 xlibs
retitle 248564 xlibs: Alt key doesn't work(alt-tab,ctrl-alt-f1,etc)
thanks
On Tue, May 11, 2004 at 10:25:17PM -0400, Alexander Tait Brotman wrote:
> Package: xbase-clients
> Version: 4.3.0.dfsg.1-1
> Severity: normal
>=20
> After upgrading today, the Alt modifier no longer seems to work.
> Pressing Ctrl-Alt-F1 does not swtich to VT1, and Alt-Tab does not
> switch windows in Sawfish. Ctrl-Alt-Bksp does shutdown the server.
> `xev` returns XF86_Switch_VT_1 when i hit ctrl-alt-f1. I'm not sure
> where else to go to figure out whats going on.
Debian X Window System Frequently Asked Questions (FAQ) List
$Id: FAQ 1170 2004-03-21 20:09:00Z branden $
[...]
*) Why doesn't my "< >" key work?
[Thanks to Guillem Jover and Ingo Saitz for their assistance researching th=
is
entry.]
In XFree86 4.3.0, the stock configuration data for the X Keyboard Extension
(XKB) was overhauled. One of the few downsides to this much-needed update =
was
that the "< >" key commonly found on European keyboards stopped functioning.
Users of 102- or 105-key PC keyboards (as well as miniature and laptop
keyboards compatible with these models) should ensure that their keyboard is
configured accordingly in the XF86Config-4 file, using the "pc102" or "pc10=
5"
XkbModel instead of "pc101" or "pc104", respectively. U.S.-style PC keyboa=
rds
do not have a "< >" key, it is this additional key that distinguishes a pc1=
02
keyboard from a pc101 keyboard, and a pc105 keyboard from a pc104 keyboard.
If your keyboard has a "< >" key, you probably have a 102- or 105-key model.
The "< >" key may not work if you do not configure your keyboard model
correctly. You can use "dpkg-reconfigure xserver-xfree86" to change this
configuration parameter, or edit /etc/X11/XF86Config-4 directly.
If you have done this, or have already confirmed that your XkbModel is set =
to
"pc102" or "pc105" in the XF86Config-4 file, but your "< >" key *still*
doesn't work in X, then an X client is probably reconfiguring your keyboard
after the server starts.
To confirm this, start the X server in a way that bypasses all client-side
initialization, and use the xev program from the xbase-clients package to
determine whether your "< >" key works when the X server initially starts.
Here's one way to do it from a virtual console:
$ xinit /usr/bin/X11/xev -- :1 vt8 > /tmp/xev.out
This starts the X server using server number 1 (in case you already have a
session active on :0), on virtual console 8, and runs the xev client,
redirecting xev's output to a temporary file.
Move the mouse cursor into the white window, then press and release the "< =
>"
key. (There will be no visible response to your keystrokes.) Then kill th=
e X
server, either by using CTRL-ALT-BACKSPACE or by switching back to the virt=
ual
console from which you ran xinit, and typing CTRL-C.
Next, use your favorite pager program to view xev's output:
$ pager /tmp/xev.out
Near the end (after a whole lot of mouse events), you will see something li=
ke
this:
KeyRelease event, serial 28, synthetic NO, window 0x1a00001,
root 0x58, subw 0x0, time 19431502, (57,266), root:(553,290),
state 0x0, keycode 94 (keysym 0x3c, less), same_screen YES,
XLookupString gives 1 bytes: "<"
Note particularly the "keycode" and "keysym" information.
If, instead, you see something like this:
KeyRelease event, serial 28, synthetic NO, window 0x1e00001,
root 0x58, subw 0x0, time 20019010, (425,-87), root:(429,281),
state 0x0, keycode 94 (keysym 0x0, NoSymbol), same_screen YES,
XLookupString gives 0 bytes: ""
Then the X server is not starting with the correct keymap for your locale, =
and
you need to check your XF86Config-4 file again. You may have a subtle
problem, such as multiple keyboard input devices defined in the file (and t=
he
wrong one is being used), or the XF86Config-4 file may have been disregarded
in favor of a different configuration file. See the XF86Config-4(5x) manual
page for more information on these types of problems.
Also note that the XFree86 X server log file (such as /var/log/XFree86.0.lo=
g)
will not only tell you the name of the configuration file that was used, but
also what the X server thinks the keyboard configuration is.
If the X server can see your "< >" key when it starts this way, but not
normally, then you *do* have a problem with an X client changing it after t=
he
X server starts. Several X clients can do this, including:
* xmodmap
* setxkbmap
* the KDE Control Center
* the GNOME Control Center
The xmodmap client is deprecated for keyboard manipulation, but some people
still use it. The best way to see if it is running is to check the system'=
s X
session scripts as well as your own. E.g.:
$ grep -irs xmodmap /etc/X11/xkb $HOME/.xsession
The setxbdmap client is pretty straightforward, and can be searched for the
same way. Make sure it is not being invoked with the "-model pc101" "-model
pc104" arguments, for example. See setxkbmap(1x) for more information.
In KDE 3.2, the relevant Control Center menu is Regional & Accessibility ->
Keyboard Layout.
In GNOME 2.4, right-click the GNOME keyboard applet and select "Settings...=
".
[...]
Please re-open this bug if this does not rectify your problem. Even
though you didn't report a "< >" problem, the latter part of the above
troubleshooting procedure should apply.
--=20
G. Branden Robinson | Suffer before God and ye shall be
Debian GNU/Linux | redeemed. God loves us, so He
[EMAIL PROTECTED] | makes us suffer Christianity.
http://people.debian.org/~branden/ | -- Aaron Dunsmore
--JVTyp1F/hrbhzAAs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iEYEARECAAYFAkCtnHsACgkQ6kxmHytGonxScACgk3xjqqRQmNTdpYZmiyz/TLnG
zr8An0TO2YvCW4/PQ485knTRH+dj3OXU
=7UV5
-----END PGP SIGNATURE-----
--JVTyp1F/hrbhzAAs--
