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

Bug #846303 reported by Wuthering Heights
156
This bug affects 35 people
Affects Status Importance Assigned to Milestone
unity-2d
Confirmed
Critical
Unassigned
unity-2d (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I actually logged in and am using normal Unity, not 2D, but this crash report popped up after I logged in.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-2d-panel 4.6.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
Date: Sat Sep 10 01:39:44 2011
ExecutablePath: /usr/bin/unity-2d-panel
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: unity-2d-panel
SegvAnalysis:
 Segfault happened at: 0x68e8f08: mov 0x4(%edi),%edx
 PC (0x068e8f08) ok
 source "0x4(%edi)" (0xe8985025) 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: Upgraded to oneiric on 2011-09-02 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Wuthering Heights (jaanisf) wrote :
Changed in unity-2d (Ubuntu):
status: New → Confirmed
Revision history for this message
PeteGordon (petegordon007) wrote :

I was using Ubuntu 2D but had logged out, switched to Ubuntu and logged in again. The error appeared the first time I opened the dash wit the super key.

Revision history for this message
MN (istheendnigh) wrote :

This occurred when I logged in, but I was using GNOME Shell, not Unity 2D.

Revision history for this message
Florin (tlenze) wrote :

This occurred when I logged into Ubuntu 2D.

Changed in unity-2d:
status: New → Confirmed
importance: Undecided → Critical
milestone: none → 4.8
Revision history for this message
Raza Rahil Hussain (razarahil) wrote :

Any patch of this error?

Revision history for this message
gl56720j (gl56720j) wrote :

Had this issue when using unity-2d and when using unity

Changed in unity-2d:
milestone: 4.8 → 4.10
Changed in unity-2d:
milestone: 4.10 → none
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.