Ubuntu

Overview
Code
Bugs
Blueprints
Translations
Answers

unity-2d-shell crashed with SIGSEGV

Reported by AutoMatriX on 2012-03-19

This bug report is a duplicate of: Bug #936560: unity-2d-shell crashed with SIGSEGV. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	unity-2d (Ubuntu)	New	Undecided	Unassigned

(?)

Bug Description

not a single cluel, I just closed banshee

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-2d-shell 5.6.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-13.56-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Mon Mar 19 18:01:03 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/unity-2d-shell
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110719.2)
ProcCmdline: unity-2d-shell
SegvAnalysis:
Segfault happened at: 0x6a2a25: testb $0x4,(%esi)
PC (0x006a2a25) ok
source "$0x4" ok
destination "(%esi)" (0x00080044) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity-2d
StacktraceTop:
?? () from /usr/lib/i386-linux-gnu/libQtDeclarative.so.4
?? () from /usr/lib/i386-linux-gnu/libQtDeclarative.so.4
?? () from /usr/lib/i386-linux-gnu/libQtDeclarative.so.4
?? () from /usr/lib/i386-linux-gnu/libQtDeclarative.so.4
?? () from /usr/lib/i386-linux-gnu/libQtScript.so.4
Title: unity-2d-shell crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-03-19 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags: Edit Tag help

AutoMatriX (wolfsnest) wrote on 2012-03-19:

Dependencies.txt Edit (6.0 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (114 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (3.7 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) wrote on 2012-03-19: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #936560, 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.