rhythmbox crashed with SIGSEGV in sem_post()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
...
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Fri Oct 4 12:55:55 2013
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2013-07-05 (90 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: rhythmbox
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=sv
PATH=(custom, no user)
LANG=sv_SE.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f9ae96411c0 <sem_post>: mov (%rdi),%eax
PC (0x7f9ae96411c0) ok
source "(%rdi)" (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 () at ../nptl/
PyThread_
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
Title: rhythmbox crashed with SIGSEGV in sem_post()
UpgradeStatus: Upgraded to saucy on 2013-07-06 (89 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
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 #1198375, 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.