Banshee.exe crashed with SIGSEGV in _Unwind_ForcedUnwind()

Bug #981928 reported by Sascha
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
New
Undecided
Unassigned

Bug Description

1) Ubuntu 12.04 LTS Beta 2 (nightly build)

2) banshee 2.4.0-1ubuntu3

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: banshee 2.4.0-1ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu3
Architecture: i386
Date: Sat Apr 14 23:27:41 2012
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120327.1)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued
SegvAnalysis:
 Segfault happened at: 0xaa9cbb19: cmpw $0xb858,(%edx)
 PC (0xaa9cbb19) ok
 source "$0xb858" ok
 destination "(%edx)" (0xa84f2628) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: banshee
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libgcc_s.so.1
 ?? () from /lib/i386-linux-gnu/libgcc_s.so.1
 _Unwind_ForcedUnwind () from /lib/i386-linux-gnu/libgcc_s.so.1
 _Unwind_ForcedUnwind () from /lib/i386-linux-gnu/libpthread.so.0
 __pthread_unwind () from /lib/i386-linux-gnu/libpthread.so.0
Title: Banshee.exe crashed with SIGSEGV in _Unwind_ForcedUnwind()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Sascha (skbierm-deactivatedaccount) wrote :
Revision history for this message
Sascha (skbierm-deactivatedaccount) wrote :

On banshee 2.4.0-1ubuntu3 I didn't get the bug anymore in 3 days, so I guess it is fixed.

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 this software better. This particular crash has already been reported and is a duplicate of bug #959958, 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
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.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.