plasma crashed with SIGSEGV

Bug #269893 reported by Rocco
16
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdebase-workspace

Crashed on logout and got notification when loggin in again.

ProblemType: Crash
Architecture: i386
Disassembly: 0xb7f29430:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/plasma
NonfreeKernelModules: nvidia
Package: kdebase-workspace-bin 4:4.1.1-0ubuntu5
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/plasma
ProcEnviron:
 SHELL=/usr/bin/tcsh
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
Signal: 11
SourcePackage: kdebase-workspace
Stacktrace: #0 0xb7f29430 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: plasma crashed with SIGSEGV
Uname: Linux 2.6.27-3-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy kqemu lpadmin netdev plugdev powerdev scanner uucp vboxusers video

Revision history for this message
Rocco (rocco) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in kdebase-workspace:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Harald Sitter (apachelogger) wrote :

Andreas, just out of curiosity: how can a bug have an importance if no one ever confirmed that the bug is actually valid?

Changed in kdebase-workspace:
importance: Medium → Undecided
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report didn't yield the required information. Please go ahead and submit a new crash report if it crashes again with the latest available version of the package if the crash happens again. Installing the kdebase-workspace-dbg package before the crash happens will help ensure that apport extracts the proper debug information. Thanks in advance for your cooperation and understanding.

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.