Bug#257515: lost my 'c' key in X
I would like to state that the same problem appears with the 'us'
layout and any of pc10{1,2,4,5} keyboards.
--
Please do not CC me when replying to lists; I read them!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' :proud Debian developer, admin, and user
`. `'`
`- Debian - when you have better things to do than fixing a system
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
signature.asc
Description: Digital signature
Bug#257515: lost my 'c' key in X
also sprach martin f krafft <[EMAIL PROTECTED]> [2004.07.23.0756 +0200]:
> I would like to state that the same problem appears with the 'us'
> layout and any of pc10{1,2,4,5} keyboards.
The update to xlibs -6 fixed this for me.
--
Please do not CC me when replying to lists; I read them!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' :proud Debian developer, admin, and user
`. `'`
`- Debian - when you have better things to do than fixing a system
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
signature.asc
Description: Digital signature
Time sensitive... refer to # J743241
Hello, Did you recieve my email from last week? I'm happy to tell you that you are approved for a home loan with a 2.89% rate. Your tracking number is # I5 101 202 You must visit the link below in 24 hrs to confirm your details. http://lendingneed.com/?partid=moffob Best Regards, Marcie Stiles General Manager Ameriqwest Financial
Bug#259754: xlibmesa-dri: [i830] crack-attack segfaults
Le mar 20/07/2004 à 09:04, Branden Robinson a écrit : > Please save the attached file and run it from a shell prompt to gather and > deliver some more information to us: > > $ ./xlibmesa-dri.bug > /tmp/output 3>&1 Please find it attached. I have also attached the valgrind output, and here is the backtrace with electric-fence loaded: Electric Fence 2.1 Copyright (C) 1987-1998 Bruce Perens. (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...Crack Attack! v1.1.9 by Daniel Nelson [aluminumangel.org], 2002 Program received signal SIGFPE, Arithmetic exception. [Switching to Thread 1078806560 (LWP 3339)] 0x40741310 in _mesa_test_os_sse_exception_support () from /usr/X11R6/lib/modules/dri/debug/i830_dri.so (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x403a33fc in memcpy () from /lib/tls/i686/cmov/libc.so.6 (gdb) bt #0 0x403a33fc in memcpy () from /lib/tls/i686/cmov/libc.so.6 #1 0x4069cb00 in texsubimage2d_unpack_ci8_direct (convert=0xbfffa7d0) at texutil_tmp.h:246 #2 0x4069d005 in convert_texsubimage2d_ci8 (convert=0xbfffa9a0) at texutil.c:672 #3 0x4069e2f6 in _mesa_convert_texsubimage1d (mesaFormat=1119153664, xoffset=1119153664, width=1119153664, format=805300618, type=5121, unpacking=0xbfffa9a0, srcImage=0x42b4ee00, dstImage=0x42b4ee00) at texutil.c:854 #4 0x4068f00d in _mesa_transfer_teximage (ctx=0x407d5538, dimensions=1, baseInternalFormat=6409, dstFormat=0x4077d500, dstAddr=0x42b4ee00, srcWidth=32, srcHeight=1, srcDepth=1, dstXoffset=0, dstYoffset=0, dstZoffset=0, dstRowStride=0, dstImageStride=0, srcFormat=6409, srcType=5121, srcAddr=0xbfffa9a0, srcPacking=0x407e88cc) at texstore.c:497 #5 0x4068f1a3 in _mesa_store_teximage1d (ctx=0x407d5538, target=1119153664, level=1119153664, internalFormat=6409, width=32, border=0, format=6409, type=5121, pixels=0xbfffa9a0, packing=0xbfffa9a0, texObj=0x42b48e50, texImage=0x42b4cfac) at texstore.c:680 #6 0x40683e35 in _mesa_TexImage1D (target=3552, level=0, internalFormat=6409, width=32, border=0, format=6409, type=5121, pixels=0x42b4ee00) at teximage.c:1574 #7 0x080626a3 in std::basic_stringbuf, std::allocator >::overflow () #8 0x080503cd in std::basic_stringbuf, std::allocator >::overflow () #9 0x080561f0 in std::basic_stringbuf, std::allocator >::overflow () #10 0x0804be96 in ?? () #11 0x4033c7da in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #12 0x4045dd84 in ?? () from /lib/tls/i686/cmov/libc.so.6 -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom ==3313== Memcheck, a memory error detector for x86-linux. ==3313== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward. ==3313== Using valgrind-2.1.1, a program supervision framework for x86-linux. ==3313== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward. ==3313== For more details, rerun with: -v ==3313== Crack Attack! v1.1.9 by Daniel Nelson [aluminumangel.org], 2002 ==3313== Warning: noted but unhandled ioctl 0x6448 with no size/direction hints ==3313==This could cause spurious value errors to appear. ==3313==See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==3313== Syscall param sigaction(act) contains uninitialised or unaddressable byte(s) ==3313==at 0x3C000C02: (within /lib/ld-2.3.2.so) ==3313==by 0x7: ??? ==3313== Address 0x4FFFE02C is on thread 1's stack ==3313== ==3313== Syscall param sigaction(act) contains uninitialised or unaddressable byte(s) ==3313==at 0x3C000C02: (within /lib/ld-2.3.2.so) ==3313==by 0x7F: ??? ==3313== Address 0x4FFFE02C is on thread 1's stack ==3313== ==3313== Invalid read of size 2 ==3313==at 0x3C777D55: sigfpe_handler (common_x86.c:123) ==3313==by 0x4FFFEFFF: ??? ==3313==by 0x3C777FEE: _mesa_init_all_x86_transform_asm (common_x86.c:355) ==3313==by 0x3C6E5E01: _math_init_transformation (m_xform.c:210) ==3313== Address 0x6E is not stack'd, malloc'd or free'd ==3313== ==3313== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==3313== Access not within mapped region at address 0x6E ==3313==at 0x3C777D55: sigfpe_handler (common_x86.c:123) ==3313==by 0x4FFFEFFF: ??? ==3313==by 0x3C777FEE: _mesa_init_all_x86_transform_asm (common_x86.c:355) ==3313==by 0x3C6E5E01: _math_init_transformation (m_xform.c:210) ==3313== ==3313== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 53 from 1) ==3313== malloc/free: in use at exit: 371286 bytes in 126 blocks. ==3313== malloc/free: 220 allocs, 94 frees, 390253 bytes allocated. ==3313== For a detailed leak analysis, rerun with: --leak-check=yes ==3313== For counts of detected errors, rerun with: -v VGA-compatible devices on PCI bus: :00:02.0 VGA compatible controller: Intel Corp. 82852/855GM
Bug#261081: xserver-xfree86: [radeon] dpms doesn't work with DVI radeon PCI card
Package: xserver-xfree86 Version: 4.3.0.dfsg.1-6 Severity: normal DPMS fails to work at all with a Radeon 7000 PCI DVI card. The xserver logs detect the ability to turn the monitor off & "xset q" shows that dmps is turned on, but "xset dpms force off" blanks the screen but doesn't turn off the TFT panel (a samsung SyncMaster 173T). cheers, Phil -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xfree86 /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx1 root root 20 2004-06-10 15:20 /etc/X11/X -> /usr/bin/X11/XFree86 -rwxr-xr-x1 root root 1745388 2004-07-07 16:07 /usr/bin/X11/XFree86 Contents of /var/lib/xfree86/XF86Config-4.roster: xserver-xfree86 VGA-compatible devices on PCI bus: :00:10.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] :01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200 AGP (rev 03) /etc/X11/XF86Config-4 does not match checksum in /var/lib/xfree86/XF86Config-4.md5sum. XFree86 X server configuration file status: -rw-r--r--1 root root 4028 2004-06-17 12:34 /etc/X11/XF86Config-4 Contents of /etc/X11/XF86Config-4: # XF86Config-4 (XFree86 X Window System server configuration file) # # This file was 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.) # # This file is automatically updated on xserver-xfree86 package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xfree86 # package. # # If you have edited this file but would like it to be automatically updated # again, run the following commands as root: # # cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom # md5sum /etc/X11/XF86Config-4 > /var/lib/xfree86/XF86Config-4.md5sum # dpkg-reconfigure xserver-xfree86 Section "Files" # FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these 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/CID" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "gb" Option "XkbOptions""altwin:meta_win" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/psaux" Option "Protocol" "PS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "SendCoreEvents""true" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Generic Video Card" Driver "radeon" # BusID "PCI:0:10:0" Option "EnablePageFlip""1" EndSection # EDID version 1 revision 3 Section "Monitor" # Block type: 2:0 3:fd # Block type: 2:0 3:fc Identifier "SyncMaster" VendorName "SAM" ModelName "SyncMaster" # Block type: 2:0 3:fd HorizSync 30-81 VertRefresh 56-75 # Max dot clock (video bandwidth) 140 MHz # Block type: 2:0 3:fc # Block type: 2:0 3:ff # DPMS capabilities: Active off:yes Suspend:no Standby:no Mode"1280x1024" # vfreq 60.020Hz, hfreq 63.981kHz DotClock108.00 HTimings1280 1328 1440 1688 VTimings1024 1025 1028 1066
Bug#261088: Suggestion: xkb rules for Thinkpad extra keys
Package: xlibs
Version: 4.3.0.dfsg.1-6
Severity: wishlist
Tags: patch
I have written a small set of xkb rules to enable the extra keys
on thinkpad laptops (keysyms 233 and 234). The rules implement
new keyboard model 'thinkpad'.
The files are available with a html README from
http://hile.dyndns.org/xkb-thinkpad.tgz
You can probably just run diff for the files under xkb directory,
the changes are quite trivial. It would be great if these configs
would end up being part of the packages and upstream.
There might be problems with the rules and the fact these rules
replace the pc101,pc102 and other 'model' parameters in XF86Config-4,
works for me at least with finnish keyboard.
I think my mapping of 'Prev/Next_Virtual_Screen' is good to not mix
the keys with any other, possibly used keys, and most likely map
nicely to the tasks most people would do with these keys now: I see
no other use for these keys except virtual desktop switching and
window moving.
*hile*
-- Package-specific info:
Keyboard-related contents of XFree86 X server log file
/var/log/XFree86.0.log:
(==) Using config file: "/etc/X11/XF86Config-4"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Internal LCD"
(**) | |-->Device "ATI Radeon Mobility 9000 M9"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "thinkpad"
(**) XKB: model: "thinkpad"
(**) Option "XkbLayout" "fi"
(**) XKB: layout: "fi"
(**) Option "XkbOptions" "ctrl:nocaps"
(**) XKB: options: "ctrl:nocaps"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Configured Mouse"
(**) |-->Input Device "Generic Mouse"
(WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/CID" does not exist.
--
(II) RADEON(0): Direct rendering enabled
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Keyboard "Generic Keyboard" handled by legacy driver
(**) Option "Protocol" "PS/2"
(**) Configured Mouse: Protocol: "PS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/psaux"
Keyboard-related contents of XFree86 X server log file
/var/log/XFree86.1.log:
(++) Using config file: "/etc/X11/XF86Config-4-fglrx"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "Generic Monitor"
(**) | |-->Device "ATI Radeon Mobility 9000 M9"
(**) |-->Input Device "Generic Keyboard"
(**) Option "XkbRules" "xfree86"
(**) XKB: rules: "xfree86"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "fi"
(**) XKB: layout: "fi"
(**) Option "XkbOptions" "ctrl:nocaps"
(**) XKB: options: "ctrl:nocaps"
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "Configured Mouse"
(**) |-->Input Device "Generic Mouse"
(WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/CID" does not exist.
--
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Keyboard "Generic Keyboard" handled by legacy driver
(**) Option "Protocol" "PS/2"
(**) Configured Mouse: Protocol: "PS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/psaux"
XFree86 X server log files on system:
-rw-r--r-- 1 root root 35228 2004-07-03 16:09 /var/log/XFree86.1.log
-rw-r--r-- 1 root root 163322 2004-07-23 18:12 /var/log/XFree86.0.log
Compiled XKB description for X server ":0.0":
xkb_keymap {
xkb_keycodes "xfree86+aliases(qwerty)" {
minimum = 8;
maximum = 255;
= 9;
= 10;
= 11;
= 12;
= 13;
= 14;
= 15;
= 16;
= 17;
= 18;
= 19;
= 20;
= 21;
= 22;
= 23;
= 24;
= 25;
= 26;
= 27;
= 28;
= 29;
= 30;
= 31;
= 32;
= 33;
= 34;
= 35;
= 36;
= 37;
= 38;
= 39;
= 40;
= 41;
= 42;
Bug#254923: xserver-xfree86: [keyboard] alt key not working
On Tue, Jul 20, 2004 at 02:08:29AM -0500, Branden Robinson wrote: > On Fri, Jul 16, 2004 at 04:38:56PM -0500, Pete Harlan wrote: > > On Mon, 12 Jul 2004 22:57:58 -0500, G. Branden Robinson wrote: > > > xfree86 4.3.0.dfsg.1-6 is now in unstable. Do they keys work for > > > you now? > > > > Yes, thank you, I no longer can reproduce the problem where the first > > use of Alt, Meta, etc. per login session is ignored. > > Excellent. Sadly, the problem returned, then went away, then returned, etc. A day or so after reporting its disappearance I saw the problem again, but so fleetingly I wondered if I had really pressed the modifier key. Yesterday it came back with a vengeance, but just when I was trying to isolate a test case it went away again. It returned this morning, but it's obviously intermittent. The behavior: I start X (with kdm or startx), open an xterm, hit ^D to close it and just get "d". As long as I keep the Ctrl key held down I can keep hitting "d" all I want and I get "d" etc. Then I release Ctrl, and the next ^D is interpreted properly. Same for Meta. > > I do still have the problem where in an xterm (but not an Emacs > > window) I have to press Alt+Windows to get the effect of Alt. This one is 100% reproducible. Thank you so much for all your hard work, --Pete
Bug#261104: xserver-xfree86: [radeon] 9600 Dual DVI - false-color display on secondary head
Package: xserver-xfree86 Version: 4.3.0.dfsg.1-6 Severity: normal Hi, on the secondary head of an Radeon 9600 Dual-DVI the colors are completely broken. Displays are 1600x1200 IBM L200p, both via DVI. Color example (Digicam 800x600 scaled) http://silicon-verl.de/home/flo/falsecolor_9600_dualdvi.jpg Its not a hardware problem as windows shows correct colors. Not only the colors are broken but also the hardware cursor on the secondary head. While snapping to window edges one should get a different cursor - Instead the cursor just jumps. Flo -- Package-specific info: Contents of /var/lib/xfree86/X.roster: xserver-xfree86 xserver-xfree86-dbg /etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum. X server symlink status: lrwxrwxrwx1 root root 20 Jul 15 02:27 /etc/X11/X -> /usr/bin/X11/XFree86 -rwxr-xr-x1 root root 1745388 Jul 7 17:07 /usr/bin/X11/XFree86 Contents of /var/lib/xfree86/XF86Config-4.roster: xserver-xfree86 xserver-xfree86-dbg VGA-compatible devices on PCI bus: :01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] :01:00.0 Class 0300: 1002:4150 /etc/X11/XF86Config-4 does not match checksum in /var/lib/xfree86/XF86Config-4.md5sum. XFree86 X server configuration file status: -rw-r--r--1 root root 3060 Jul 23 18:04 /etc/X11/XF86Config-4 Contents of /etc/X11/XF86Config-4: # 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 manual page. # (Type "man XF86Config" at the shell prompt.) Section "Files" #FontPath "unix/:7100"# local font server # if the local font server has problems, we can fall back on these 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 "ServerFlags" EndSection Section "Module" Load"ddc" Load"GLcore" Load"dbe" Load"dri" Load"extmod" Load"glx" Load"pex5" Load"record" Load"xie" Load"bitmap" Load"freetype" Load"speedo" Load"type1" Load"vbe" Load"int10" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc105" Option "XkbLayout" "de" Option "XkbVariant""nodeadkeys" Option "XkbRules" "xfree86" EndSection Section "InputDevice" Identifier "Mouse" Driver "mouse" Option "CorePointer" Option "SendCoreEvents""true" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "ATI-1.0" Driver "radeon" VendorName "ATI Technologies Inc" BoardName "RV350 AP [Radeon 9600]" BusID "PCI:1:0:0" #Option "RenderAccel" "on" #Option "MonitorLayout" "TMDS,TMDS" Screen 0 EndSection Section "Device" Identifier "ATI-1.1" Driver "radeon" VendorName "ATI Technologies Inc" BoardName "RV350 AP [Radeon 9600]" BusID "PCI:1:0:0" #Option "RenderAccel" "on" Screen 1 EndSection Section "Monitor" Identifier "L200p" HorizSync 31-75 VertRefresh 56-85 Option "DPMS" EndSection Section "Screen" Identifier "Screen0" Device "ATI-1.0" Monitor "L200p" DefaultDepth24 SubSection "Display" Depth 8 Modes "1600x1200" EndSubSection SubSection "Display" Depth 16 Modes "1600x1200" EndSubSection SubSection "Display" Depth 24 Modes "1600x1200" EndSubSection SubSection "Display" Depth 32 Modes "1600x1200" EndSubSection EndSection Section "Screen" Identifier "Screen
X Strike Force XFree86 SVN commit: r1685 - in trunk/debian: . local
Author: branden Date: 2004-07-23 15:10:06 -0500 (Fri, 23 Jul 2004) New Revision: 1685 Modified: trunk/debian/CHANGESETS trunk/debian/local/FAQ.xhtml Log: (cosmetic) Fix typo (thanks, Paul Gotch). Modified: trunk/debian/CHANGESETS === --- trunk/debian/CHANGESETS 2004-07-22 02:48:59 UTC (rev 1684) +++ trunk/debian/CHANGESETS 2004-07-23 20:10:06 UTC (rev 1685) @@ -13,7 +13,7 @@ 1606 Miscellaneous cosmetic fixes. -1607, 1608, 1624, 1626, 1627, 1636, 1651, 1654, 1663, 1664, 1675 +1607, 1608, 1624, 1626, 1627, 1636, 1651, 1654, 1663, 1664, 1675, 1685 Grab latest version of XTerm (#191) from Thomas Dickey's website. 1609 Modified: trunk/debian/local/FAQ.xhtml === --- trunk/debian/local/FAQ.xhtml2004-07-22 02:48:59 UTC (rev 1684) +++ trunk/debian/local/FAQ.xhtml2004-07-23 20:10:06 UTC (rev 1685) @@ -2626,7 +2626,7 @@ The workaround of using the MonitorLayout option simply forces the card into a particular mode so that it ignores whatever is -comming over DDC. +coming over DDC. I've heard that it is possible to damage the card with an incorrect MonitorLayout line, but I can't think of a physical
Bug#261150: default-x-display-manager asked at inflated priority
Package: xdm,gdm,kdm Severity: normal xdm, gdm, and kde all ask the shared/default-x-display-manager at high priority. Debconf policy is that high priority is for items that don't have a reasonable default. I think that as long as any of xdm, gdm, or kdm is the default, that qualifies as a reaonable default display manager; each of them is usable. If there's some alternatives-style ranking going on to rank more usable display managers higher and make them more likely to be the default, that's even better. Anyway, right now an install of debian with gdm and kdm asks which to use, even at high priority, and I think that's an unnecessary question to ask for a high priority install. -- see shy jo -- see shy jo signature.asc Description: Digital signature
Bug#246398: locales: LC_CTYPE defaults to non-installed en_US.UTF8
* Branden Robinson [2004-05-21 00:45:19-0500]
> On Tue, May 04, 2004 at 11:50:07AM -0700, Blars Blarson wrote:
[...]
> > I tracked down what is setting LC_CTYPE: /usr/X11R6/bin/uxterm
> > Sorry I didn't think to check outside of X before.
> >
> > There is even a comment about possibly not having a UTF8 enviornment
> > available. On Debian, it is possible to check /etc/locale.gen.
>
> That's not the right answer; I'm pretty sure the (GNU) C library
> supports function calls to inquire as to whether a given locale is
> supported.
>
> If some of those function calls are available in a simple shell utility,
> I'd be happy to patch the uxterm shell script accordingly. I might even
> be able to write it portably enough that it will be accepted upstream by
> Mr. Dickey.
There is the validlocale(8) utility in the base-config package and it is
currently used at the start of the second stage d-i installation to
validate the locale given (which comes from the debian-installer/locale
registery). Being a perl script, it uses the following standart call to
determine whether the locale exists:
my $loc = setlocale(LC_ALL, $LANG);
if ( ! $loc) {
print STDERR "locale '$LANG' not available\n";
[...]
I think it we could write a C version of validlocale, because it has a
fairly simple and well-defined interface, (and is already present in a
_base_ package.)
Regards,
--
roktas
signature.asc
Description: Digital signature
Bug#230787: xterm: dies when XIM is killed
On Sun, 18 Jul 2004, Thomas Dickey wrote:
When using kinput2 with xterm, if kinput2 is killed, xterm dies, too.
Very undesirable, as kinput2 needs to be restarted when its
configuration options are changed. GTK2 programs work fine with kinput2
restarts, so xterm should, too.
The current version of XTerm in Debian testing ("sarge") is XTerm #187
(2004-04-27).
Can you still reproduce this problem?
I tried to reproduce the problem today but could not. (If it's still a bug,
I'll need more information about the environment, procedure, etc).
This was harder to reproduce than I expected. I thought it'd always
happen, but that's not true (I just tried xterm briefly, noticed a
problem, and went back to using gnome-terminal). I haven't checked how XIM
works, but apparently you need to have sent some request to kinput2,
after which kinput2 has to die before responding, and *then* the client
application freezes. When I said xterm "dies", I was being unclear.. It
doesn't exit.
A way to reproduce this for all X apps I tested:
1. kill -STOP
2. freeze application xyzzy by causing it to use XIM
3a. if you still wish to use the app, kill -CONT
3b. otherwise, kill -9 . Prepare to kill -9 the app, too.
Nothing seems to help at this point. If you strace the app, you'll
see that it does selects, reads, etc. to get X events, but some of
those reads just return EAGAIN, even if that doesn't normally happen.
EAGAIN isn't supposed to be a fatal error, but a kill -9:ed process
won't ever be responding again, now will it? :-)
The difference between gnome-terminal and xterm is that it only takes one
keystroke in step 2 to temporarily freeze xterm, while gnome-terminal
requires pressing shift-space (the conversion mode switch key).
The way to freeze xterm without kill -STOPping kinput2:
1. Start kinput2.
2. Start a new xterm.
3. Type "kill " in the xterm and press enter.
4. If you're lucky (and I seem to always be), xterm is now permanently frozen.
Probably because of the final enter key press..
The right thing to do would IMHO be to fix XIM usage, or XIM itself if
this is an inherent problem, but I've no idea if this is feasible. At
least xterm is not alone in this. Not routing everything through XIM would
be one "solution", but is it really better than just saying "Don't Do
That, Then"? Dunno, really.. Would seem like an ugly workaround to me.
Programs just shouldn't freeze (semi)permanently if a XIM server dies or
is kill -STOPped. OTOH, XIM has its flaws, and some people are working on
a replacement.. (see iimf)
As you can avoid problems just by being careful to restart kinput2 from a
non-XIM-using terminal, this is just a mild annoyance. In any case, if it
isn't fixed in some fashion, it should probably be documented in the BUGS
section on the man page.
Bug#261163: xlibs-data: change sequences for KP_Delete for PL locales
Package: xlibs-data Version: 4.3.0.dfsg.1-6 Severity: normal Tags: l10n In Poland we use comma as decimal point. The numeric keypad Is commonly used for entering a lot of numeric data. Right now pressing delete key produces dot which is really useless here. It's common problem for newbies when they try using some office package and they cannot enter fractional numbers. There are dozen of post related to that on newsgroups and they always get answer like this: xmodmap -e "keycode 91 KP_Delet=comma" As you can see this is not user friendly setting, and even finding that solution in documentation may be really hard for newbies. I'm wondering why it wasn't reported to upstream. Maybe because it's hard to say who is "upstream"? - That's why I'm reporting it here. Please fix that at least in Debian. It's just small change somewhere around /usr/X11R6/lib/X11/locale/ (I guess) and gives big improvement for users. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.6-1-k7 Locale: LANG=pl_PL, LC_CTYPE=pl_PL -- no debconf information
Bug#261173: xset: print screen resolution
Package: xbase-clients Version: 4.3.0.dfsg.1-6 Severity: wishlist File: /usr/X11R6/bin/xset $ xset q could print screen resolution parameters, e.g., 800x600.
