rhythmbox crashed with SIGSEGV in rb_sync_settings_sync_category()

Bug #642508 reported by chest069
128
This bug affects 24 people
Affects Status Importance Assigned to Milestone
Rhythmbox
Expired
Critical
rhythmbox (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

I was trying to open my media device.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: rhythmbox 0.13.1-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Sep 18 23:00:51 2010
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: rhythmbox
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x7ffe3c15691c <rb_sync_settings_sync_category+28>: mov (%rax),%rdi
 PC (0x7ffe3c15691c) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 rb_sync_settings_sync_category (settings=0x0, category=0x7ffe3c1e444a "music") at rb-sync-settings.c:170
 build_sync_itinerary (state=0x4e77660) at rb-sync-state.c:296
 rb_sync_state_update (state=0x4e77660) at rb-sync-state.c:379
 impl_constructed (object=0x4e77660) at rb-sync-state.c:464
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in rb_sync_settings_sync_category()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

Revision history for this message
chest069 (chest069) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 rb_sync_settings_sync_category (settings=0x0,
 rb_sync_state_update (state=0x4e77660)
 impl_constructed (object=0x4e77660)
 g_object_newv (object_type=<value optimized out>,
 g_object_new_valist (object_type=65905440,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=631038

visibility: private → public
Changed in rhythmbox (Ubuntu):
status: New → Triaged
Changed in rhythmbox:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
Enkouyami (furyhamster) wrote :

I had the same problem in 12.04 Alpha 2. Also, before that happened, I added the lyrics, sharing, and maybe another plugin and got a bug message. It didn't apply to any of the available choices and I clicked cancle; there was an error that didn't noticeably affect anything.

Revision history for this message
Bram Schellen (bram-schellen) wrote :

This bug happend when I plugged my Samsung Galaxy S2 into my Ubuntu notebook. Both Banshee and Rhythmbox Grey-out and it looks like there waiting for someting. Rhythmbox also crashes.

Revision history for this message
Lars Falk-Petersen (julenissen) wrote :

Samsung Galaxy S2 here as well. Maybe it's the phone.. =)

Revision history for this message
tictactoe (xavier-garel) wrote :

Also the bug occured with my Galaxy S2 :(

Ubuntu 12.04 AMD64

Revision history for this message
Aleksi Kinnunen (aleksi-kinnunen) wrote :

I had this when using Nokia N8 + Ubuntu 12.04 i386.

Revision history for this message
Carl Andrew Stevenson (vulcanfusion) wrote :

Archos 80g Tablet with Ice cream Sandwich plugged in as a media device!

Revision history for this message
Sparhawk (sparhawkthesecond) wrote :

I managed to plug in my Samsung S3, but then trying to sync it crashed rhythmbox.

Changed in rhythmbox:
status: New → Confirmed
Changed in rhythmbox:
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.