[Bug 506977] Re: Xorg crashed with SIGSEGV in DamageUnregister() / VAuditF()

2010-01-15 Thread Bryce Harrington
** Summary changed: - Xorg crashed with SIGSEGV in DamageUnregister() + Xorg crashed with SIGSEGV in DamageUnregister() / VAuditF() -- Xorg crashed with SIGSEGV in DamageUnregister() / VAuditF() https://bugs.launchpad.net/bugs/506977 You received this bug notification because you are a member

[Bug 506977] Re: Xorg crashed with SIGSEGV in DamageUnregister() / VAuditF()

2010-01-15 Thread Bryce Harrington
I'm not 100% certain, but this bug report looks a heck of a lot like bug #506510, and I think it shares the same root cause. The problem is that error messages were being written to the log after the log file was closed, which causes a segfault in the signal handling code. I've corrected the

[Bug 506977] Re: Xorg crashed with SIGSEGV in DamageUnregister() / VAuditF()

2010-01-15 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg-server - 2:1.7.3.902-1ubuntu7 --- xorg-server (2:1.7.3.902-1ubuntu7) lucid; urgency=low * Update 100_rethrow_signals.patch: Don't log more error messages after the log has been closed, else it causes a SIGSEGV (signal 11) crash under