rhythmbox crashed with SIGSEGV in rb_sync_settings_sync_category()

Bug #1235388 reported by Robert Ross
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

Using 13.10 (which I had upgraded today in an attempt to assuage this same issue in 12.04) Rhythmbox crashes the instant I try to to anything with a Samsung Galaxy Note 2; eg. clicking on the "sync" button or attempting to right-click on the device from within Rhythmbox's UI.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Fri Oct 4 13:58:19 2013
ExecutablePath: /usr/bin/rhythmbox
MarkForUpload: True
ProcCmdline: rhythmbox
SegvAnalysis:
 Segfault happened at: 0x7f202b91b74c <rb_sync_settings_sync_category+28>: mov (%rax),%rdi
 PC (0x7f202b91b74c) 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 () from /usr/lib/librhythmbox-core.so.7
 rb_sync_state_update () from /usr/lib/librhythmbox-core.so.7
 ?? () from /usr/lib/librhythmbox-core.so.7
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in rb_sync_settings_sync_category()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Robert Ross (robertross) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1225550, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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