Author: branden
Date: 2004-03-19 00:27:06 -0500 (Fri, 19 Mar 2004)
New Revision: 1168
Modified:
trunk/debian/NEWS
trunk/debian/changelog
trunk/debian/local/FAQ
Log:
Add FAQ entry about the <LSGT> key problem.
Edit news item about the <LSGT> problem to tidy up the wording a little and
direct people to the FAQ for more information.
Modified: trunk/debian/NEWS
===================================================================
--- trunk/debian/NEWS 2004-03-19 04:13:39 UTC (rev 1167)
+++ trunk/debian/NEWS 2004-03-19 05:27:06 UTC (rev 1168)
@@ -16,11 +16,15 @@
keyboards compatible with these models) should ensure that their keyboard
is configured accordingly in the XF86Config-4 file, using the "pc102" or
"pc105" XkbModel instead of "pc101" or "pc104", respectively. If your
- keyboard has a "< >" key, you likely have a 102- or 105-key model. The
- "< >" may not work if you do not configure your keyboard model correctly.
- You can use "dpkg-reconfigure xserver-xfree86" to change this
+ 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.
+ See the Debian X FAQ at <http://people.debian.org/~branden/xsf/FAQ> or in
+ the file /usr/share/doc/xfree86-common/FAQ.gz after this upgrade is
+ complete for more information if you have problems with your keyboard.
+
-- Branden Robinson <[EMAIL PROTECTED]> Tue, 13 Jan 2004 20:46:02 -0500
xfree86 (4.2.1-11) unstable; urgency=medium
Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog 2004-03-19 04:13:39 UTC (rev 1167)
+++ trunk/debian/changelog 2004-03-19 05:27:06 UTC (rev 1168)
@@ -1,3 +1,11 @@
+xfree86 (4.3.0-8) unstable; urgency=low
+
+ * Add FAQ entry about the <LSGT> key problem. Edit news item about the
+ <LSGT> problem to tidy up the wording a little and direct people to the
+ FAQ for more information.
+
+ -- Branden Robinson <[EMAIL PROTECTED]> Fri, 19 Mar 2004 00:26:17 -0500
+
xfree86 (4.3.0-7) unstable; urgency=medium
* Urgency due to fix for FTBFS. Yes -- I too am begging for it to stop.
Modified: trunk/debian/local/FAQ
===================================================================
--- trunk/debian/local/FAQ 2004-03-19 04:13:39 UTC (rev 1167)
+++ trunk/debian/local/FAQ 2004-03-19 05:27:06 UTC (rev 1168)
@@ -77,6 +77,7 @@
*) How do I stop xdm from starting at boot?
*) How do I tell xdm to start the X server on a different virtual console?
*) How do I run an X client as root when the X session is run by a user?
+*) Why doesn't my "< >" key work?
*) Why doesn't my backspace, delete, or some other key work?
*) How do I change xterm's default terminal type or key bindings?
*) How do I keep my mouse from going crazy (or going away) when switching
@@ -701,6 +702,99 @@
instead; the EXAMPLES section of its manual page is instructive for the
most common tasks.
+*) Why doesn't my "< >" key work?
+
+[Thanks to Guillem Jover and Ingo Saitz for their assistance researching this
+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 "pc105"
+XkbModel instead of "pc101" or "pc104", respectively. U.S.-style PC keyboards
+do not have a "< >" key, it is this additional key that distinguishes a pc102
+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 the X
+server, either by using CTRL-ALT-BACKSPACE or by switching back to the virtual
+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 of mouse events), you will see something like
+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 the
+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.
+
+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 the
+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...".
+
*) Why doesn't my backspace, delete, or some other key work?
Unfortunately, there are many places where things can go wrong if you think
