ksmserver crashed with SIGSEGV in <signal handler called>()

Bug #380256 reported by Daniel Hahler
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

After logging into KDE 4.3b1, the 4 desktops from the "pager" applet were not in the usual place, but spanned the whole width, i.e. they took up four times the usual height.
I've clicked into them, suddenly kwin took 100% cpu, and I had to kill the kwin process.

Don't know, if that's related though..

ProblemType: Crash
Architecture: i386
Date: Mon May 25 14:29:32 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/ksmserver
NonfreeKernelModules: nvidia
Package: kdebase-workspace-bin 4:4.2.85-0ubuntu6
ProcCmdline: ksmserver
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-5.6-generic
Signal: 11
SourcePackage: kdebase-workspace
StacktraceTop:
 ?? () from /usr/lib/libkdeinit4_ksmserver.so
 <signal handler called>
 __kernel_vsyscall ()
 select () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /usr/lib/libQtCore.so.4
Title: ksmserver crashed with SIGSEGV in <signal handler called>()
Uname: Linux 2.6.30-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse sambashare scanner src video

Revision history for this message
Daniel Hahler (blueyed) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:sighandler (sig=166181592) at ../../ksmserver/server.cpp:505
<signal handler called>
__kernel_vsyscall ()
select () from /lib/tls/i686/cmov/libc.so.6
QProcessManager::run (this=0x9e7bad8)

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.