[Bug 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so

2011-01-30 Thread Harry
** Package changed: xorg-server (Ubuntu Natty) = xserver-xorg-input- evdev (Ubuntu Natty) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709977 Title: Xorg crashed with SIGSEGV in RemoveDevice() -

[Bug 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so

2011-01-30 Thread Zuzkins
for the downgrading part: it really helps. Here is how i did it: wgetted the package from https://launchpad.net/ubuntu/+source/xserver- xorg-input-evdev/1:2.3.2-6ubuntu3b1/+buildjob/2109048 and sudo dpkg -i xserver-xorg-input-evdev_2.3.2-6ubuntu3b1_amd64.deb -- You received this bug

[Bug 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so

2011-01-30 Thread Jean-Baptiste Lallement
See bug 709977 for packages to test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709977 Title: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so --

[Bug 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so

2011-01-30 Thread Jean-Baptiste Lallement
Wrong pasting, the bug number is bug 709915 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709977 Title: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so --

[Bug 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so

2011-01-30 Thread Laurent Bigonville
I can also confirm that it works with 1:2.6.0-1ubuntu2~nopatch101 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709977 Title: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error

[Bug 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so

2011-01-30 Thread Kees Cook
Fixed for me with 1:2.6.0-1ubuntu2~nopatch101, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709977 Title: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in

[Bug 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so

2011-01-30 Thread Launchpad Bug Tracker
This bug was fixed in the package xserver-xorg-input-evdev - 1:2.6.0-1ubuntu2 --- xserver-xorg-input-evdev (1:2.6.0-1ubuntu2) natty; urgency=low * Disable patch 101-gestures.patch - Fix SIGSEGV in xserver. (LP: #709977) -- Bryce Harrington br...@ubuntu.com Sun, 30 Jan 2011

[Bug 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so

2011-01-30 Thread SheeEttin
I wrangled an unstripped version of evdev into my system and I managed a better backtrace (I'm coming from bug #709915): #0 0x7fbc7c69c39d in GrailOpen (pInfo=0x1ffce20) at ../../src/evdev-grail.c:268 #1 0x7fbc7c69a39d in EvdevProbe (drv=value optimized out, dev=value optimized out,

[Bug 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so

2011-01-29 Thread Jean-Baptiste Lallement
From the duplicates, only amd64 is affected. ** Summary changed: - Xorg crashed with SIGSEGV - segfault at 1010 error 4 in evdev_drv.so + Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so ** Changed in: xorg-server (Ubuntu Natty) Importance: High =

[Bug 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so

2011-01-29 Thread Harry
I very much doubt this is a bug in xorg-server (xserver 1.9 series). The crash ([ 11.710] segmentation fault at address 0x1010) happens very clearly with Nvidia graphics cards and with nvidia-current binary drivers. In fact with nvidia, the system will not even boot to gdm. Also using wireless