plasma-desktop crashed with SIGSEGV when changing battery monitor settings

Bug #1028163 reported by johannes
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde-workspace (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

consistently crashes when right clicking on kde battery icon in system tray, click battery monitor setting , toggle check box show remain time for each battery, press apply , crash.

might be related that battery icon occasionally not updating correctly ( still showing full battery while nearly empty) possibly only after suspending (not confirmed)

seems to be relatively new issue , can't remember any problems on 12.04

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: plasma-desktop 4:4.8.90-0ubuntu3
Uname: Linux 3.5.0-999-generic x86_64
ApportVersion: 2.4-0ubuntu5
Architecture: amd64
Date: Mon Jul 23 23:43:36 2012
Disassembly: => 0x7fbc01047445: Cannot access memory at address 0x7fbc01047445
ExecutablePath: /usr/bin/plasma-desktop
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/bin/plasma-desktop --nocrashhandler
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbc01047445: Cannot access memory at address 0x7fbc01047445
 PC (0x7fbc01047445) ok
 SP (0x7fffcb95b198) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: kde-workspace
Stacktrace:
 #0 0x00007fbc01047445 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffcb95b198
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 5 (LWP 1449):
 #0 0x00007fbc010f7b03 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fbbd7111c60
Title: plasma-desktop crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-06-23 (30 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (process:2107): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
 (process:2107): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
 (process:2107): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
 (process:2107): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
 (firefox:5522): Gdk-WARNING **: Native Windows wider or taller than 65535 pixels are not supported

Revision history for this message
johannes (di) wrote :
Revision history for this message
johannes (di) wrote :

also attached kde backtrace , seems to be more useful

johannes (di)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007fbc01047445 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffcb95b198
StacktraceSource: #0 0x00007fbc01047445 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 5 (LWP 1449):
 #0 0x00007fbc010f7b03 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fbbd7111c60

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:

outdated debug symbol package for libcdparanoia0: package version 3.10.2+debian-10.1ubuntu1 dbgsym version 3.10.2+debian-10ubuntu1
outdated debug symbol package for module-init-tools: package version 3.16-1ubuntu3 dbgsym version 3.16-1ubuntu2
outdated debug symbol package for initscripts: package version 2.88dsf-13.10ubuntu13 dbgsym version 2.88dsf-13.10ubuntu11
outdated debug symbol package for plasma-widgets-addons: package version 4:4.8.90-0ubuntu1 dbgsym version 4:4.8.4-0ubuntu0.1

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
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.