rhythmbox crashed with SIGSEGV in rhythmdb_entry_get_playback_uri()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This seems to be related to playing previews from Ubuntu One Music Store. I'll try to describe exactly what I do and experience.
I opened Rhythmbox and played a couple of locally installed songs. I then opened Ubuntu One Music Store and searched for Nellie McKay (which, sadly, I didn't find) and then for "Robert Normann", whom I did find. (!)
I chose the album called «Robert Normann - The Definitive Collection 1950 - 71, Vol 3» and clicked to play a preview of "Smålåt 2". Before it finished, I clicked to play the next song, «How high the moon» and then the Rhythmbox window immediately froze. I got a clickable-icon (pointing finger) and then the Apport dialog appeared.
This has happened before and the steps described above seems to reproduce it exactly every time. After asking to send this report, Rhythmbox closes immediately when I perform the above steps, so I guess the frozen window I experienced initially is related to that.
Also note that playing locally stored songs while a preview from U1MS is playing, causes the exact same result.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.96-0ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-21-generic x86_64
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
Date: Tue Apr 3 16:13:13 2012
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120125)
ProcCmdline: rhythmbox
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
Title: rhythmbox crashed with SIGSEGV in rhythmdb_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd 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 #951203, 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.