plasma-desktop crashed with SIGSEGV

Bug #955826 reported by Myriam Schweingruber
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kde-workspace (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Since the upgrade to KDE 4.8.1 in Precise plasma-desktop crashes on start. It has to be started manually every time

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plasma-desktop 4:4.8.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Thu Mar 15 08:48:10 2012
Disassembly: => 0x7f22065aa595: Cannot access memory at address 0x7f22065aa595
ExecutablePath: /usr/bin/plasma-desktop
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: /usr/bin/plasma-desktop --nocrashhandler
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f22065aa595: Cannot access memory at address 0x7f22065aa595
 PC (0x7f22065aa595) ok
 SP (0x7fffe60cd0e8) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: kde-workspace
Stacktrace:
 #0 0x00007f22065aa595 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffe60cd0e8
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 7 (LWP 24404):
 #0 0x00007f222590cd93 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7f21f68edc80
Title: plasma-desktop crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Myriam Schweingruber (myriam) wrote :
visibility: private → public
Jonathan Riddell (jr)
Changed in kde-workspace (Ubuntu):
milestone: none → ubuntu-12.04-beta-2
tags: added: kubuntu
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007f22065aa595 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffe60cd0e8
StacktraceTop: ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in kde-workspace (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libexiv2-11 version 0.22-oneiric~ppa2 required, but 0.22-2 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Philip Muškovac (yofel)
visibility: public → private
Revision history for this message
Myriam Schweingruber (myriam) wrote :

crash report from my /var/crash/ folder

Jonathan Riddell (jr)
visibility: private → public
Jonathan Riddell (jr)
Changed in kde-workspace (Ubuntu):
milestone: ubuntu-12.04-beta-2 → ubuntu-12.04
status: Invalid → Confirmed
Revision history for this message
Myriam Schweingruber (myriam) wrote :

Since then I installed anew and run the Quantal alpha packages, I haven't seen this happen (still have my old $HOME/.kde/ in case somebody is interested). AFAIAC this bug can be closed.

Changed in kde-workspace (Ubuntu):
status: Confirmed → 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.