[Bug 1615540] Re: Xorg crashes with modeset driver on kernel 4.8-rc3 with SIGABRT in OsAbort()

2018-05-07 Thread Daniel van Vugt
** Changed in: xorg-server (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615540 Title: Xorg crashes with modeset driver on kernel 4.8-rc3 with

[Bug 1615540] Re: Xorg crashes with modeset driver on kernel 4.8-rc3 with SIGABRT in OsAbort()

2016-10-08 Thread Rocko
I don't see this any more in 4.8-0 final. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615540 Title: Xorg crashes with modeset driver on kernel 4.8-rc3 with SIGABRT in OsAbort() To manage

[Bug 1615540] Re: Xorg crashes with modeset driver on kernel 4.8-rc3 with SIGABRT in OsAbort()

2016-10-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615540 Title:

[Bug 1615540] Re: Xorg crashes with modeset driver on kernel 4.8-rc3 with SIGABRT in OsAbort()

2016-08-22 Thread Rocko
I don't think this is a duplicate of https://bugs.launchpad.net/bugs/1543192. Although it triggers a crash at the same point, the underlying cause of this bug is an incompatibility between the modesetting driver and kernel 3.8-rc3. (Unless the underlying bug is in the kernel and it triggers the

[Bug 1615540] Re: Xorg crashes with modeset driver on kernel 4.8-rc3 with SIGABRT in OsAbort()

2016-08-22 Thread Apport retracing service
*** This bug is a duplicate of bug 1543192 *** https://bugs.launchpad.net/bugs/1543192 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1543192, so is being marked as such.