rhythmbox crashed with SIGSEGV in rb_sync_settings_sync_category()

[ikedagus]

Binary package hint: rhythmbox

Rythmbox crashed when I was trying to connect my phone to the laptop using "Media transfer" connection mode via the USB cable to listen to the music stored in a SD card in the phone. The app senses the connection and lists the phone as an "Unknown device" and after a few seconds it just crashes.

My phone info:
Brand: Nokia
Model: 5800 XpressMusic
Type: RM-356
Firmware version: 51.0.006

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: rhythmbox 0.13.1-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CrashCounter: 1
Date: Mon Sep 27 19:52:17 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Beta i386 (20100902.1)
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x79bf09 <rb_sync_settings_sync_category+41>: mov (%eax),%eax
 PC (0x0079bf09) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 rb_sync_settings_sync_category () from /usr/lib/librhythmbox-core.so.1
 rb_sync_state_update () from /usr/lib/librhythmbox-core.so.1
 ?? () from /usr/lib/librhythmbox-core.so.1
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in rb_sync_settings_sync_category()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #642508, 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.