ksmserver crashed with SIGSEGV in start_thread()

[errold32]

Binary package hint: kdebase-workspace

Tried to start two monitors with nvidia-settings. on restart, I observed a rainbow cloud of colors on one monitor, and a blank screen, with an x cursor on the other. I restored the xorg.conf backup, and am up and running again, with one monitor. This bug was reported on restart.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/ksmserver
NonfreeKernelModules: nvidia ath_hal
Package: kdebase-workspace-bin 4:4.2.2-0ubuntu2
ProcCmdline: ksmserver
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdebase-workspace
StacktraceTop:
 ?? () from /usr/lib/libkdeinit4_ksmserver.so
 ?? () from /usr/lib/libQtCore.so.4
 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
 clone () from /lib/tls/i686/cmov/libc.so.6
Title: ksmserver crashed with SIGSEGV in start_thread()
Uname: Linux 2.6.28-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:sighandler (sig=1)
<signal handler called>
__kernel_vsyscall ()
select () from /lib/tls/i686/cmov/libc.so.6
?? () from /usr/lib/libQtCore.so.4

[Jonathan Thomas (echidnaman)]

This is X crashing due to the nvidia graphics driver. (Taking down everything else with it)

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.