rhythmbox crashed with SIGSEGV in rb_sync_settings_sync_category()
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
ProcVersionSign
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_
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_
rb_sync_
?? () from /usr/lib/
?? () from /usr/lib/
g_object_
Title: rhythmbox crashed with SIGSEGV in rb_sync_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.