rhythmbox crashed with SIGSEGV in sem_post@@GLIBC_2.1()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Just crashed when logging in
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-4-generic i686
ApportVersion: 2.12.1-0ubuntu3
Architecture: i386
Date: Sat Aug 31 14:39:18 2013
ExecutablePath: /usr/bin/rhythmbox
ExecutableTimes
InstallationDate: Installed on 2013-08-29 (2 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130712)
MarkForUpload: True
ProcCmdline: rhythmbox /home/ablock/
ProcCwd: /home/ablock
SegvAnalysis:
Segfault happened at: 0xb73a8e15 <sem_post@
PC (0xb73a8e15) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.