rhythmbox crashed with SIGSEGV in sem_post@@GLIBC_2.1()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
automatic report
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-3-generic i686
ApportVersion: 2.12.1-0ubuntu2
Architecture: i386
Date: Fri Aug 23 12:15:50 2013
ExecutablePath: /usr/bin/rhythmbox
ExecutableTimes
MarkForUpload: True
ProcCmdline: rhythmbox
ProcCwd: /home/phoenix
SegvAnalysis:
Segfault happened at: 0xb736de15 <sem_post@
PC (0xb736de15) ok
source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
sem_post@
PyThread_
PyEval_ReleaseLock () from /usr/lib/
PyThreadState_
PyGILState_Release () from /usr/lib/
Title: rhythmbox crashed with SIGSEGV in sem_post@
UpgradeStatus: Upgraded to saucy on 2013-07-12 (41 days ago)
UserGroups: adm cdrom dip fuse lp lpadmin plugdev sambashare sudo vboxusers video www-data
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 #1199159, 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.