rhythmbox crashed with SIGSEGV in rb_sync_settings_sync_category()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
Expired
|
Undecided
|
Unassigned | ||
rhythmbox (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Attempted to connect Samsung Galaxy S3 (cyanogenmod 10.1) in MTP mode to rhythmbox. Crashed each time
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: rhythmbox 2.99.1-
ProcVersionSign
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CrashCounter: 1
Date: Sat Apr 27 21:45:19 2013
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2013-04-27 (0 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: rhythmbox
SegvAnalysis:
Segfault happened at: 0x7f4c24e52b6c <rb_sync_
PC (0x7f4c24e52b6c) 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/
g_object_newv () 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
information type: | Private → Public |
tags: | removed: need-amd64-retrace |
affects: | ubuntu → rhythmbox (Ubuntu) |
I have the same problem with Ubuntu 13.10. I want to specify that I have CyanogenMod 10.1.3 on my Samsung Galaxy S3.