ksmserver crashed with SIGSEGV in QString::operator=()

Bug #273036 reported by JRulez
14
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-workspace

My laptop went into hibernate after my battery was almost empty. When I started my laptop again I got this error.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/ksmserver
NonfreeKernelModules: nvidia
Package: kdebase-workspace-bin 4:4.1.1-0ubuntu5
ProcAttrCurrent: unconfined
ProcCmdline: ksmserver
ProcEnviron:
 PATH=/home/roel/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdebase-workspace
StacktraceTop:
 QString::operator= () from /usr/lib/libQtCore.so.4
 ?? () from /usr/lib/libQtCore.so.4
 QProcess::qt_metacall ()
 KProcess::qt_metacall ()
 QMetaObject::activate ()
Title: ksmserver crashed with SIGSEGV in QString::operator=()
Uname: Linux 2.6.27-2-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
JRulez (r-j-meeuws) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:QStringMatcher::QStringMatcher () from /usr/lib/libQtCore.so.4
?? () from /usr/lib/libQtCore.so.4
?? ()
QTimeLine::qt_metacall () from /usr/lib/libQtCore.so.4
?? () from /usr/lib/libQtCore.so.4

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Harald Sitter (apachelogger) wrote :

Did this ever happen again?
E.g. with KDE 4.1.2?

Changed in kdebase-workspace:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdebase-workspace:
status: Incomplete → Invalid
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.