rhythmbox crashed when playing from UbuntuOne store

Bug #951142 reported by Stefan Taferner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

Go into the Ubuntu One store.
Click the playback icon on any title.
Navigate to another title.
Click playback on that title.
Voila.

It should be reproducable, at least for me it happened twice in a row now.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.95.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 9 21:54:04 2012
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: rhythmbox
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=de_AT:de
 LANG=de_AT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f66e4428561: movdqu (%rdi),%xmm1
 PC (0x7f66e4428561) ok
 source "(%rdi)" (0x4024000000000018) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 PyString_FromString () from /usr/lib/libpython2.7.so.1.0
 ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
 PyEval_EvalFrameEx () from /usr/lib/libpython2.7.so.1.0
 PyEval_EvalCodeEx () from /usr/lib/libpython2.7.so.1.0
Title: rhythmbox crashed with SIGSEGV in PyString_FromString()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Stefan Taferner (taferner) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.