Johan Walles wrote: > found 410696 2:1.1.1-19 > thanks > > Backtrace: > 0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4354] > 1: [0xb7fe2420] > 2: /usr/bin/X(Dispatch+0x81) [0x8086b91] > 3: /usr/bin/X(main+0x489) [0x806e699] > 4: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7de9ea8] > 5: /usr/bin/X(FontFileCompleteXLFD+0xa9) [0x806d9d1]
Since you reproduced this bug a couple times with several versions of the X server, do you have any idea how we could try to reproduce it for sure? Also, I don't see in the BTS that you ever tried a more recent X server. 1.1.1 is actually pretty outdated nowadays. The latest upstream (1.3-rc2) is currently in experimental, you could eventually try it (xserver-xorg-core 2:1.2.99.902-1). If you don't like testing a release candidate X server, the previous stable one (1.2.0, the official server of Xorg 7.2) has been in experimental for a while earlier. You could grab it from: http://snapshot.debian.net/archive/2007/03/03/debian/pool/main/x/xorg-server/xserver-xorg-core_1.2.0-6_i386.deb Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]