unity-2d-panel crashed with SIGSEGV in malloc()

Bug #855489 reported by James Gifford
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-2d (Ubuntu)
New
Undecided
Unassigned

Bug Description

updated 11.10 this morning, logged out and back into unity 2d and the launcher crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-panel 4.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CheckboxSubmission: e97468e43f98d94e22f6ea5c985b41fa
CheckboxSystem: 9c26adf6eed2f681ba41f94dd24c07e4
CrashCounter: 1
Date: Wed Sep 21 08:10:46 2011
ExecutablePath: /usr/bin/unity-2d-panel
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: unity-2d-panel
SegvAnalysis:
 Segfault happened at: 0x6abf08: mov 0x4(%edi),%edx
 PC (0x006abf08) ok
 source "0x4(%edi)" (0x220ecb0d) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 malloc () from /lib/i386-linux-gnu/libc.so.6
 qMalloc(unsigned int) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 QListData::detach(int) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
Title: unity-2d-panel crashed with SIGSEGV in malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
James Gifford (jamesgifford) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #854862, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-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.