rhythmbox crashed with SIGSEGV in start_thread()

[Aaron Bentley]

It crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: rhythmbox 2.97-1ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Thu Sep 13 17:35:00 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: rhythmbox /home/username/.gvfs/username\ on\ shorty/Downloads/The\ Doobie\ Brothers\ -\ Listen\ to\ the\ Music\ -\ The\ Very\ Best\ of\ the\ Doobie\ Brothers\ (1993)\ [V0]/The\ Doobie\ Brothers\ -\ Listen\ to\ the\ Music\ -\ The\ Very\ Best\ of\ the\ Doobie\ Brothers.m3u
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa9017ec0f7: mov (%rdx,%rbx,1),%rsi
 PC (0x7fa9017ec0f7) ok
 source "(%rdx,%rbx,1)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/librhythmbox-core.so.6
 ?? () from /usr/lib/librhythmbox-core.so.6
 ?? () from /usr/lib/librhythmbox-core.so.6
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 start_thread (arg=0x7fa87fd95700) at pthread_create.c:308
Title: rhythmbox crashed with SIGSEGV in start_thread()
UpgradeStatus: Upgraded to quantal on 2012-09-08 (5 days ago)
UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare

[Apport retracing service (apport)]

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 #1029333, 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.