rhythmbox crashed with SIGSEGV in g_type_check_value_holds()

[penalvch]

Plugged in the following, opened rhythmbox, and then rhythmbox crashed.

Bus 005 Device 013: ID 05ac:129e Apple, Inc. iPod Touch 4.Gen
Version: 6.1.6 (10B500)
Model: MC544LL/A

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep 30 06:55:20 2014
ExecutablePath: /usr/bin/rhythmbox
ExecutableTimestamp: 1398725961
InstallationDate: Installed on 2014-06-21 (101 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
LogAlsaMixer:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [on]
ProcCmdline: rhythmbox
ProcCwd: /home/moniker
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f69da96ec3d <g_type_check_value_holds+61>: testb $0x8,0x16(%rbx)
 PC (0x7f69da96ec3d) ok
 source "$0x8" ok
 destination "0x16(%rbx)" (0x1f00000036) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 g_type_check_value_holds () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgpod.so.4
 itdb_parse () from /usr/lib/x86_64-linux-gnu/libgpod.so.4
 rb_ipod_db_new () from /usr/lib/rhythmbox/plugins/ipod/libipod.so
 ?? () from /usr/lib/rhythmbox/plugins/ipod/libipod.so
Title: rhythmbox crashed with SIGSEGV in g_type_check_value_holds()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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