rhythmbox crashed with SIGSEGV in sem_post()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
When you try to run the aplication it don't start, it crashs.
via terminal it gives this errors:
:~$ rhythmbox
** (rhythmbox:7875): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(rhythmbox:7875): GLib-GObject-
Falha de segmentação (imagem do núcleo gravada)
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 29 22:53:32 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2012-04-30 (517 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: rhythmbox
SegvAnalysis:
Segfault happened at: 0x7fa9180821c0 <sem_post>: mov (%rdi),%eax
PC (0x7fa9180821c0) 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/
xmlCreateURLPa
?? () from /usr/lib/
Title: rhythmbox crashed with SIGSEGV in sem_post()
UpgradeStatus: Upgraded to saucy on 2013-09-11 (17 days ago)
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.