rhythmbox crashed with SIGSEGV in oil_init()

[Shahar Or]

I put in my Cyanogenmod 10.2.0 Nexus 4 and try in Rhythmbox to go either to it's configuration or to 'sync' and boom.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.1-1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
Uname: Linux 3.13.0-6-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Feb 3 15:39:28 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2010-10-12 (1209 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/bin/rhythmbox
SegvAnalysis:
 Segfault happened at: 0x7f2d82d95071: mov 0x20(%rax),%rax
 PC (0x7f2d82d95071) ok
 source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/liboil-0.3.so.0
 oil_init () from /usr/lib/x86_64-linux-gnu/liboil-0.3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
Title: rhythmbox crashed with SIGSEGV in oil_init()
UpgradeStatus: Upgraded to trusty on 2013-10-26 (100 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lp lpadmin mythtv netdev plugdev sambashare sudo tape video www-data

[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 #1226807, 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.