found 375460 1:1.0.2-8
retitle 375460 server crash when the device configured as core pointer is a
keyboard
kthxbye
On Fri, Jun 30, 2006 at 13:34:20 +0200, Marcel Sebek wrote:
On Fri, Jun 30, 2006 at 12:44:45PM +0200, Michel Dänzer wrote:
The backtrace looks input related, and indeed,
On Thu, Feb 28, 2008 at 01:55:16PM +0100, Julien Cristau wrote:
found 375460 1:1.0.2-8
retitle 375460 server crash when the device configured as core pointer is a
keyboard
kthxbye
On Fri, Jun 30, 2006 at 13:34:20 +0200, Marcel Sebek wrote:
On Fri, Jun 30, 2006 at 12:44:45PM +0200,
On Thu, Jul 05, 2007 at 08:05:49PM +0200, Brice Goglin wrote:
On Wed, Jun 13, 2007 at 11:52:55AM +0200, Marcel Sebek wrote:
I can still reproduce the segfault when I set mouse event device to
the one used by keyboard or when I don't set the device at all.
When running latest
On Fri, Jul 06, 2007 at 01:54:13PM +0200, Brice Goglin wrote:
Marcel Sebek wrote:
Both gdb and output of this script attached.
[...]
Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8591]
1: [0xe420]
2: /usr/bin/X11/X(main+0x6bf) [0x80770af]
3:
On Wed, Jun 13, 2007 at 11:52:55AM +0200, Marcel Sebek wrote:
I can still reproduce the segfault when I set mouse event device to
the one used by keyboard or when I don't set the device at all.
When running latest xserver-xorg-core (1.3) and drivers ?
Could you catch a backtrace of the crash?
On Mon, May 28, 2007 at 11:35:31PM +0200, Brice Goglin wrote:
About a year ago, you reported a bug to the Debian BTS regarding Xserver
crashing because kernel 2.6.17 change numbering of input events. Did you
reproduce this problem recently? With latest xserver-xorg-core and other
Xorg packages
Hi,
About a year ago, you reported a bug to the Debian BTS regarding Xserver
crashing because kernel 2.6.17 change numbering of input events. Did you
reproduce this problem recently? With latest xserver-xorg-core and other
Xorg packages in unstable?
Thanks,
Brice
--
To UNSUBSCRIBE, email to
On Tue, 2006-06-27 at 16:25 +0200, Marcel Sebek wrote:
On Tue, Jun 27, 2006 at 11:38:15AM +0200, Michel Dänzer wrote:
On Mon, 2006-06-26 at 08:03 +0200, Marcel Sebek wrote:
This is the trace with ati driver. I also tried vesa, the trace also
started with xf86SigHandler+0x88 and
On Mon, 2006-06-26 at 08:03 +0200, Marcel Sebek wrote:
I upgraded kernel to 2.6.17 and xserver stopped working. I tried both
DRI enabled and disabled. I also tried disabling all modules and removing
all font directories, it didn't help.
The Xserver receives SIGSEG:
Backtrace:
0:
On Tue, Jun 27, 2006 at 11:38:15AM +0200, Michel Dänzer wrote:
On Mon, 2006-06-26 at 08:03 +0200, Marcel Sebek wrote:
I upgraded kernel to 2.6.17 and xserver stopped working. I tried both
DRI enabled and disabled. I also tried disabling all modules and removing
all font directories, it
Package: xserver-xorg
Version: 1:7.0.22
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
I upgraded kernel to 2.6.17 and xserver stopped working. I tried both
DRI enabled and disabled. I also tried disabling all modules and removing
all font directories, it didn't help.
I upgraded kernel to 2.6.17 and xserver stopped working.
Just for reference, I've upgraded to 2.6.17 but X is working same as it
did before (i810). I'm sorry I don't have a suggestion for fixing your
crash.
Drew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
12 matches
Mail list logo
