Bug#371870: xprint: all printer entries in mozilla are gone
Isn't the problem here that all the xprint stuff was removed from iceape? (See the discussion in bug report 301649 about this. If that's the reason, I suppose this bug should be re-filed against the mozilla transition package, for failing to add the printers to the proper configuration files for iceape. I have the same problem since upgrading from sarge to etch. I have searched the mozilla directories without success to try to find how to add printers manually. Maybe somebody who understands the inner workings of this system can figure out how to add printers to the browser. It would be *nice* if this were available as part of the edit preferences dialogs. -- A. T. Young -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335063: fonts.dir and fonts.scale files
(These 2 files are identical, so I'm sending just one.) 336 VeraMoBd.ttf -Bitstream-Bitstream Vera Sans Mono-bold-r-normal--0-0-0-0-m-0-adobe-standard VeraMoBd.ttf -Bitstream-Bitstream Vera Sans Mono-bold-r-normal--0-0-0-0-m-0-ascii-0 VeraMoBd.ttf -Bitstream-Bitstream Vera Sans Mono-bold-r-normal--0-0-0-0-m-0-iso10646-1 VeraMoBd.ttf -Bitstream-Bitstream Vera Sans Mono-bold-r-normal--0-0-0-0-m-0-iso8859-1 VeraMoBd.ttf -Bitstream-Bitstream Vera Sans Mono-bold-r-normal--0-0-0-0-m-0-iso8859-15 VeraMoBd.ttf -Bitstream-Bitstream Vera Sans Mono-bold-r-normal--0-0-0-0-m-0-iso8859-9 VeraMoBd.ttf -Bitstream-Bitstream Vera Sans Mono-bold-r-normal--0-0-0-0-m-0-microsoft-ansi VeraMoBd.ttf -Bitstream-Bitstream Vera Sans Mono-bold-r-normal--0-0-0-0-m-0-microsoft-cp1252 VeraMono.ttf -Bitstream-Bitstream Vera Sans Mono-medium-r-normal--0-0-0-0-m-0-adobe-standard VeraMono.ttf -Bitstream-Bitstream Vera Sans Mono-medium-r-normal--0-0-0-0-m-0-ascii-0 VeraMono.ttf -Bitstream-Bitstream Vera Sans Mono-medium-r-normal--0-0-0-0-m-0-iso10646-1 VeraMono.ttf -Bitstream-Bitstream Vera Sans Mono-medium-r-normal--0-0-0-0-m-0-iso8859-1 VeraMono.ttf -Bitstream-Bitstream Vera Sans Mono-medium-r-normal--0-0-0-0-m-0-iso8859-15 VeraMono.ttf -Bitstream-Bitstream Vera Sans Mono-medium-r-normal--0-0-0-0-m-0-iso8859-9 VeraMono.ttf -Bitstream-Bitstream Vera Sans Mono-medium-r-normal--0-0-0-0-m-0-microsoft-ansi VeraMono.ttf -Bitstream-Bitstream Vera Sans Mono-medium-r-normal--0-0-0-0-m-0-microsoft-cp1252 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-adobe-standard luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-ascii-0 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-iso10646-1 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-iso8859-1 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-iso8859-10 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-iso8859-13 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-iso8859-15 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-iso8859-16 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-iso8859-2 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-iso8859-3 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-iso8859-4 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-iso8859-9 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-microsoft-ansi luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-microsoft-cp1250 luxirb.ttf -bh-Luxi Serif-bold-r-normal--0-0-0-0-p-0-microsoft-cp1252 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-adobe-standard luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-ascii-0 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-iso10646-1 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-iso8859-1 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-iso8859-10 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-iso8859-13 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-iso8859-15 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-iso8859-16 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-iso8859-2 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-iso8859-3 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-iso8859-4 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-iso8859-9 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-microsoft-ansi luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-microsoft-cp1250 luxisbi.ttf -bh-Luxi Sans-bold-i-normal--0-0-0-0-p-0-microsoft-cp1252 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-adobe-standard luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-ascii-0 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso10646-1 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso8859-1 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso8859-10 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso8859-13 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso8859-15 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso8859-16 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso8859-2 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso8859-3 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso8859-4 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso8859-9 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-microsoft-ansi luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-microsoft-cp1250 luximr.ttf -bh-Luxi Mono-medium-r-normal--0-0-0-0-m-0-microsoft-cp1252 thrybi__.ttf -macromedia-Thryomanes-bold-i-normal--0-0-0-0-p-0-adobe-standard thrybi__.ttf -macromedia-Thryomanes-bold-i-normal--0-0-0-0-p-0-ascii-0 thrybi__.ttf -macromedia-Thryomanes-bold-i-normal--0-0-0-0-p-0-iso10646-1 thrybi__.ttf -macromedia-Thryomanes-bold-i-normal--0-0-0-0-p-0-iso8859-1 thrybi__.ttf -macromedia-Thryomanes-bold-i-normal--0-0-0-0-p-0-iso8859-10 thrybi__.ttf -macromedia-Thryomanes-bold-i-normal--0-0-0-0-p-0-iso8859-13 thrybi__.ttf -macromedia-Thryomanes-bold-i-normal--0-0-0-0-p-0-iso8859-15 thrybi__.ttf
Bug#335063: XF86Config-4 file
### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type man XF86Config-4 at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the ### BEGIN DEBCONF SECTION line above, and/or after the # ### END DEBCONF SECTION line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file? in /usr/share/doc/xfree86-common/FAQ.gz. Section Files # try commenting out the local server: # FontPath unix/:7100# local font server # if the local font server has problems, we can fall back on these # added by hand, June 14 2005: FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType FontPath /var/lib/defoma/x-ttcidfont-conf.d/dirs/CID FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi/:unscaled FontPath/usr/lib/X11/fonts/75dpi/:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/Speedo # FontPath /usr/lib/X11/fonts/100dpi # FontPath /usr/lib/X11/fonts/75dpi EndSection Section Module LoadGLcore Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadpex5 Loadrecord Loadspeedo Loadtype1 Loadvbe Loadxie EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout us Option AutoRepeat500 30 Option LeftAlt Meta Option RightAlt Meta Option RightCtl Control EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol ImPS/2 Option Buttons 5 Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option SendCoreEventstrue Option Device/dev/input/mice Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section Device Identifier ATI Rage 128 PF/PRO AGP 4x TMDS Driver r128 BusID PCI:1:0:0 # VideoRam 32768 Option UseFBDev false Option Display CRT EndSection Section Monitor Identifier ViewSonic M70 HorizSync 30-70 VertRefresh 50-160 Option DPMS EndSection Section Screen Identifier Default Screen Device ATI Rage 128 PF/PRO AGP 4x TMDS Monitor ViewSonic M70 DefaultDepth24 SubSection Display Depth 1 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 # Modes 1152x864 1024x768 800x600 640x480 Modes 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse InputDevice Generic Mouse EndSection Section DRI Mode0666 EndSection ### END DEBCONF SECTION -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL
Bug#335064: xbase-clients: mkfontscale installs faulty fonts.scale for ttf-bitstream-vera pkg.
Package: xbase-clients Version: 4.3.0.dfsg.1-14sarge1 Severity: important After installing the ttf-bitstream-vera font package, I find that X gives a could not init fontpath element error message for the TrueType fonts. This appears to be caused by faulty fonts.dir and fonts.scale files created in /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType directory; they have blanks instead of underscores in the XLFDs for the Bitstream fonts. The blanks make X barf when it tries to set up these fonts. I have inspected the defoma hintfile installed with the Bitstream package. It gives the font families as Bitstream-Vera-Sans, Bitstream-Vera-Serif, etc., which is (I think) reasonable. Probably the problem could be avoided for *this* font by changing the hyphens to underscores; but it seems to me the X utilities ought to be written to handle such cases gracefully, rather than making everybody who packages a font worry about replacing (normal) hyphens with (ugly) underscores in the defoma hintfiles. That's why I'm filing this bug against xutils (which provides mkfontdir) and xbase-clients (the package that provides mkfontscale). It may turn out that both these programs use some common xlib function to parse fontnames and font-family names, in which case this bug should be reassigned to the appropriate package. Note, by the way, that defoma's Defoma::Id module correctly handles these fonts, installing XLFD names with underscores in the /var/lib/defoma/x-ttcidfont-conf.d/id-cache file. A further complication is that Bug 219854 says that TrueType fonts should be using mkttfdir rather than mkfontdir, and that a bug report should be filed against font packages that violate this. This is evidently the case with the Bitstream font package; I see my system doesn't even have the fttools package installed, which should have been a dependency of the font package if it had used mkttfdir. It remains to be seen whether mkttfdir handles font-family names containing hyphens correctly -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages xbase-clients depends on: ii cpp4:3.3.5-3 The GNU C preprocessor (cpp) ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libdps14.3.0.dfsg.1-14sarge1 Display PostScript (DPS) client li ii libexpat1 1.95.8-3 XML parsing C library - runtime li ii libfontconfig1 2.3.1-2 generic font configuration library ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib ii libgcc11:3.4.3-13GCC support library ii libice64.3.0.dfsg.1-14sarge1 Inter-Client Exchange library ii libncurses55.4-4 Shared libraries for terminal hand ii libpng12-0 1.2.8rel-1PNG library - runtime ii libsm6 4.3.0.dfsg.1-14sarge1 X Window System Session Management ii libstdc++5 1:3.3.5-13The GNU Standard C++ Library v3 ii libxaw74.3.0.dfsg.1-14sarge1 X Athena widget set library ii libxcursor11.1.3-1 X cursor management library ii libxext6 4.3.0.dfsg.1-14sarge1 X Window System miscellaneous exte ii libxft22.1.7-1 FreeType-based font drawing librar ii libxi6 4.3.0.dfsg.1-14sarge1 X Window System Input extension li ii libxmu64.3.0.dfsg.1-14sarge1 X Window System miscellaneous util ii libxmuu1 4.3.0.dfsg.1-14sarge1 lightweight X Window System miscel ii libxpm44.3.0.dfsg.1-14sarge1 X pixmap library ii libxrandr2 4.3.0.dfsg.1-14sarge1 X Window System Resize, Rotate and ii libxrender10.8.3-7 X Rendering Extension client libra ii libxt6 4.3.0.dfsg.1-14sarge1 X Toolkit Intrinsics ii libxtrap6 4.3.0.dfsg.1-14sarge1 X Window System protocol-trapping ii libxtst6 4.3.0.dfsg.1-14sarge1 X Window System event recording an ii libxv1 4.3.0.dfsg.1-14sarge1 X Window System video extension li ii xfree86-common 4.3.0.dfsg.1-14sarge1 X Window System (XFree86) infrastr ii xlibmesa-gl [libgl 4.3.0.dfsg.1-14sarge1 Mesa 3D graphics library [XFree86] ii xlibmesa-glu [libg 4.3.0.dfsg.1-14sarge1 Mesa OpenGL utility library [XFree ii xlibs 4.3.0.dfsg.1-14sarge1 X Keyboard Extension (XKB) configu ii xlibs-data 4.3.0.dfsg.1-14sarge1 X Window System client data ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335063: xutils: mkfontdir installs faulty fonts.dir for ttf-bitstream-vera pkg.
Package: xutils Version: 4.3.0.dfsg.1-14sarge1 Severity: important After installing the ttf-bitstream-vera font package, I find that X gives a could not init fontpath element error message for the TrueType fonts. This appears to be caused by faulty fonts.dir and fonts.scale files created in /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType directory; they have blanks instead of underscores in the XLFDs for the Bitstream fonts. The blanks make X barf when it tries to set up these fonts. I have inspected the defoma hintfile installed with the Bitstream package. It gives the font families as Bitstream-Vera-Sans, Bitstream-Vera-Serif, etc., which is (I think) reasonable. Probably the problem could be avoided for *this* font by changing the hyphens to underscores; but it seems to me the X utilities ought to be written to handle such cases gracefully, rather than making everybody who packages a font worry about replacing (normal) hyphens with (ugly) underscores in the defoma hintfiles. That's why I'm filing this bug against xutils (which provides mkfontdir) and xbase-clients (the package that provides mkfontscale). It may turn out that both these programs use some common xlib function to parse fontnames and font-family names, in which case this bug should be reassigned to the appropriate package. Note, by the way, that defoma's Defoma::Id module correctly handles these fonts, installing XLFD names with underscores in the /var/lib/defoma/x-ttcidfont-conf.d/id-cache file. A further complication is that Bug 219854 says that TrueType fonts should be using mkttfdir rather than mkfontdir, and that a bug report should be filed against font packages that violate this. This is evidently the case with the Bitstream font package; I see my system doesn't even have the fttools package installed, which should have been a dependency of the font package if it had used mkttfdir. It remains to be seen whether mkttfdir handles font-family names containing hyphens correctly -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages xutils depends on: ii cpp4:3.3.5-3 The GNU C preprocessor (cpp) ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii xfree86-common 4.3.0.dfsg.1-14sarge1 X Window System (XFree86) infrastr ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296021: xbase-clients: xgamma fails,gives error message
Package: xbase-clients Version: 4.1.0-16woody5 Severity: normal xgamma's man page says it will show the current gamma value if no option is given with the -gamma flag. I was unable to get it to do this. Typing just xgamma with no arguments gave: Xserver is running an old XFree86-VidModeExtension version (0.8) Minimum required version is 2.0 Looks as if the clients are out of step with the server in woody. -- A. T. Young -- System Information Debian Release: 3.0 Kernel Version: Linux aty786 2.4.18-1-k7 #1 Wed Apr 14 19:20:42 UTC 2004 i686 unknown Versions of the packages xbase-clients depends on: ii cpp2.95.4-14 The GNU C preprocessor. ii debconf1.0.32 Debian configuration management system ii libc6 2.2.5-11.8 GNU C Library: Shared libraries and Timezone ii libdps14.1.0-16woody5 Display PostScript (DPS) client library ii libfreetype6 2.0.9-1FreeType 2 font engine, shared library files ii libncurses55.2.20020112a- Shared libraries for terminal handling ii libxaw74.1.0-16woody5 X Athena widget set library ii xlibmesa3 4.1.0-16woody5 XFree86 version of Mesa 3D graphics library ii xlibs 4.1.0-16woody5 X Window System client libraries ii xlibmesa3 4.1.0-16woody5 XFree86 version of Mesa 3D graphics library ^^^ (Provides virtual package libgl1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#181423: xbase-clients: X screws up keyboard rate in consoles
Package: xbase-clients Version: 4.1.0-16 Severity: normal I've noticed for some time now that after I've used X and then switch back to a console with ctrlaltFn, the keyboard rate and delay have been reset to Debian's default values (long delay, fast rep rate) instead of the IBM defaults that I prefer, and which I normally set up by using kbdrate from a console with no arguments. In my .xsession file, I *do* call xset r rate 250 11 to re-establish my preferred rate and delay. This makes the keyboard behave properly in an xterm or rxvt window; but it does not prevent X from messing up the consoles. Not understanding the insides of the X window system, I don't even know which client is likely to be the culprit here. For a while, I had the impression that things like netscape or ghostview were at fault, but test show that the keyboard is messed up by X as soon as it comes up, before I've entered any commands to X from the keyboard. It seems to me that even if X has to play with the keyboard for its own internal reasons -- something that does not seem logically necessary, but suppose it is -- then at least the use of the xset command ought to leave things in the intended state when I go back to a console. -- System Information Debian Release: 3.0 Kernel Version: Linux aty786 2.4.18-k7 #1 Sun Apr 14 13:19:11 EST 2002 i686 unknown Versions of the packages xbase-clients depends on: ii cpp2.95.4-14 The GNU C preprocessor. ii debconf1.0.32 Debian configuration management system ii libc6 2.2.5-11.2 GNU C Library: Shared libraries and Timezone ii libdps14.1.0-16 Display PostScript (DPS) client library ii libfreetype6 2.0.9-1FreeType 2 font engine, shared library files ii libncurses55.2.20020112a- Shared libraries for terminal handling ii libxaw74.1.0-16 X Athena widget set library ii xlibmesa3 4.1.0-16 XFree86 version of Mesa 3D graphics library ii xlibs 4.1.0-16 X Window System client libraries ii xlibmesa3 4.1.0-16 XFree86 version of Mesa 3D graphics library ^^^ (Provides virtual package libgl1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#181423: xbase-clients: X screws up keyboard rate in consoles
Package: xbase-clients Version: 4.1.0-16 Severity: normal I've noticed for some time now that after I've used X and then switch back to a console with ctrlaltFn, the keyboard rate and delay have been reset to Debian's default values (long delay, fast rep rate) instead of the IBM defaults that I prefer, and which I normally set up by using kbdrate from a console with no arguments. In my .xsession file, I *do* call xset r rate 250 11 to re-establish my preferred rate and delay. This makes the keyboard behave properly in an xterm or rxvt window; but it does not prevent X from messing up the consoles. Not understanding the insides of the X window system, I don't even know which client is likely to be the culprit here. For a while, I had the impression that things like netscape or ghostview were at fault, but test show that the keyboard is messed up by X as soon as it comes up, before I've entered any commands to X from the keyboard. It seems to me that even if X has to play with the keyboard for its own internal reasons -- something that does not seem logically necessary, but suppose it is -- then at least the use of the xset command ought to leave things in the intended state when I go back to a console. -- System Information Debian Release: 3.0 Kernel Version: Linux aty786 2.4.18-k7 #1 Sun Apr 14 13:19:11 EST 2002 i686 unknown Versions of the packages xbase-clients depends on: ii cpp2.95.4-14 The GNU C preprocessor. ii debconf1.0.32 Debian configuration management system ii libc6 2.2.5-11.2 GNU C Library: Shared libraries and Timezone ii libdps14.1.0-16 Display PostScript (DPS) client library ii libfreetype6 2.0.9-1FreeType 2 font engine, shared library files ii libncurses55.2.20020112a- Shared libraries for terminal handling ii libxaw74.1.0-16 X Athena widget set library ii xlibmesa3 4.1.0-16 XFree86 version of Mesa 3D graphics library ii xlibs 4.1.0-16 X Window System client libraries ii xlibmesa3 4.1.0-16 XFree86 version of Mesa 3D graphics library ^^^ (Provides virtual package libgl1)
