unity-panel-service crashed with SIGSEGV

Bug #749368 reported by Daniël Sonck
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: unity

I can reproduce the crash:

I installed indicator-sysmonitor (0.2-1) ppa:alexeftimie/ppa
Under preferences I chose 'Use this command:' with command 'cat /proc/meminfo'

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Sun Apr 3 15:50:58 2011
Disassembly: => 0x7f2f6b54bd81: Cannot access memory at address 0x7f2f6b54bd81
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InstallationMedia_: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InstallationMedia__: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
LocalLibraries: /usr/local/lib/libEGL.so.1.0
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
ProcVersionSignature_: Ubuntu 2.6.38-7.39-generic 2.6.38
ProcVersionSignature__: Ubuntu 2.6.38-7.39-generic 2.6.38
SegvAnalysis:
 Segfault happened at: 0x7f2f6b54bd81: Cannot access memory at address 0x7f2f6b54bd81
 PC (0x7f2f6b54bd81) ok
 SP (0x7fffd1d19fe0) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: unity
Stacktrace:
 #0 0x00007f2f6b54bd81 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffd1d19fe0
StacktraceTop: ?? ()
Title: unity-panel-service crashed with SIGSEGV
UpgradeStatus: Upgraded to natty on 2011-03-31 (2 days ago)
UserGroups: adm cdrom dialout lpadmin mythtv plugdev pulse-access sambashare sudo
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu1

Revision history for this message
Daniël Sonck (daniel-sonck) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (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 an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libglib2.0-bin: installed version 2.28.4-0ubuntu2, latest version: 2.28.5-0ubuntu1
libudev0: installed version 166-0ubuntu6, latest version: 167-0ubuntu1
tzdata: installed version 2011d-1, latest version: 2011e-1
unity-dbg: installed version 3.8.2-0ubuntu1, latest version: 0.2.46-0ubuntu5
libgtk2.0-common: installed version 2.24.3-0ubuntu5, latest version: 2.24.4-0ubuntu1
libglib2.0-data: installed version 2.28.4-0ubuntu2, latest version: 2.28.5-0ubuntu1
libglib2.0-0: installed version 2.28.4-0ubuntu2, latest version: 2.28.5-0ubuntu1
libgtk2.0-0-dbg: installed version 2.24.3-0ubuntu5, latest version: 2.24.4-0ubuntu1
libgtk2.0-bin: installed version 2.24.3-0ubuntu5, latest version: 2.24.4-0ubuntu1
udev: installed version 166-0ubuntu6, latest version: 167-0ubuntu1
libgtk2.0-0: installed version 2.24.3-0ubuntu5, latest version: 2.24.4-0ubuntu1
libglib2.0-0-dbg: installed version 2.28.4-0ubuntu2, latest version: 2.28.5-0ubuntu1

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
Revision history for this message
Laryllan (laryllan) wrote :

I had the same crash while opening CCSM and looking through various plugins.

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.