ksmserver crashed with SIGSEGV in start_thread()

Bug #374985 reported by Rob A
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: kdebase-workspace

I just hit "CTRL-ALT-F1" to go to the console, and the whole KDE system crashed and sent me to a logon screen. When I hit ctrl-alt-F1 again, I got a have-redraw of my previous session, and no ability to do anything in the GUI, or change to any consoles, so I ahd to reboot.

rob@rob-kubuntu1:~$ sudo apt-cache policy kdebase-workspace
[sudo] password for rob:
kdebase-workspace:
  Installed: (none)
  Candidate: 4:4.2.2-0ubuntu2
  Version table:
     4:4.2.2-0ubuntu2 0
        500 http://us.archive.ubuntu.com jaunty/main Packages

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/ksmserver
Package: kdebase-workspace-bin 4:4.2.2-0ubuntu2
ProcCmdline: ksmserver
ProcEnviron:
 PATH=(custom, user)
 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-11-generic i686
UserGroups: adm admin audio cdrom dba dialout dip floppy fuse lpadmin plugdev pulse pulse-access pulse-rt src video

Revision history for this message
Rob A (docsmooth) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

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

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdebase-workspace (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.