GNOME Bugzilla – Bug 631038
rhythmbox crashed with SIGSEGV in rb_sync_settings_sync_category()
Last modified: 2018-05-24 15:32:25 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/rhythmbox/+bug/642508 "I was trying to open my media device." ".
+ Trace 223960
Thread 1 (process 19745)
*** Bug 638345 has been marked as a duplicate of this bug. ***
I have just reproduced this crash here as well. I don't know whether these steps are all significant, but here's what happened to me: - connect my media device (in this case, a Nokia N9) - device shows up in the source list with an icon but no name - click on the device source, it shows no songs in the browser - right-click on the device source and choose 'rename', type in a name - right-click on the device source, and choose 'properties' - crash.
I should note that I'm using rhythmbox 2.95-1 from debian unstable.
Hi, I also have this issue with 2.97 Please fund here a better backtrace
+ Trace 231513
I see this with current master. Bad call is:
+ Trace 234354
$4 = (RBSyncStatePrivate *) 0x1d966c0 (gdb) p *state->priv $5 = {source = 0x1107a00 [RBMtpSource], sync_settings = 0x0}
Created attachment 310271 [details] [review] sync: Add check before accessing sync settings If a (MTP) device hasn't finished loading, it's RBSyncSettings object is NULL. When the user is clicking on "Sync" or "Properties" it get's accessed what causes a segfault. This commit adds a check before calling this to functions and displays a message if the device isn't ready yet.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/983.