rhythmbox crashed with SIGSEGV in PyString_FromString()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu One for Rhythmbox |
Invalid
|
Undecided
|
Unassigned | ||
rhythmbox (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I was browsing the ubuntu music store and the I wnt to the radio stations in rythmbox to lister to so online radio. I saw 100% cpu, rythmbox did not respond. Then the crash dialog appeared.
Rythmbox did not crash though. I clicked again on the station and it started paying.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.96-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu2
Architecture: amd64
Date: Thu Apr 12 12:20:28 2012
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcCmdline: rhythmbox
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f8513ec6361: movdqu (%rdi),%xmm1
PC (0x7f8513ec6361) ok
source "(%rdi)" (0x00000089) not located in a known VMA region (needed readable region)!
destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
?? () from /lib/x86_
PyString_
?? () from /usr/lib/
PyEval_EvalFrameEx () from /usr/lib/
PyEval_EvalCodeEx () from /usr/lib/
Title: rhythmbox crashed with SIGSEGV in PyString_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Changed in rhythmbox-ubuntuone: | |
assignee: | Ubuntu One Client Engineering team (ubuntuone-client-engineering) → nobody |
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 #926618, 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.