rhythmbox crashed with SIGSEGV in g_str_hash()

[Brian Dunnette]

connected iPad 2 and clicked "Sync with Library" (~10 GB music selected for sync)

iPad Properties window shows that it will also sync 18.4 EB (!?) of "Other"

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.96-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Thu Apr 12 09:28:01 2012
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: /usr/bin/rhythmbox
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb737be3a <g_str_hash+10>: movzbl (%ecx),%edx
 PC (0xb737be3a) ok
 source "(%ecx)" (0x00001000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 g_str_hash () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_hash_table_lookup () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libgpod.so.4
 ?? () from /usr/lib/libgpod.so.4
 itdb_write () from /usr/lib/libgpod.so.4
Title: rhythmbox crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm disk sudo

[Apport retracing service (apport)]

StacktraceTop:
 g_str_hash (v=0x1000) at /build/buildd/glib2.0-2.32.0/./glib/ghash.c:1730
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x1000, hash_table=0x9d178250) at /build/buildd/glib2.0-2.32.0/./glib/ghash.c:401
 g_hash_table_lookup (hash_table=0x9d178250, key=0x1000) at /build/buildd/glib2.0-2.32.0/./glib/ghash.c:1074
 ?? ()
 ?? ()

[Walter Garcia-Fontes (walter-garcia)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]