GNOME Bugzilla – Bug 615181
rhythmbox crashed with SIGSEGV
Last modified: 2018-05-24 15:09:07 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/rhythmbox/+bug/543933 rhythmbox version is 0.12.8 "My Samsung (YP-U3) was charging using a USB port for the last 10 minutes. rhythmbox was on for the last hour. As I plugged a USB to bluetooth device, Rhythmbox crashed" "#0 0x00951a85 in rhythmdb_entry_sync_mirrored (entry=0x95eb060, propid=<value optimized out>) at rhythmdb.c:3714 never = 0x99ddee8 "\001" val = <value optimized out>
+ Trace 221284
This stack trace makes no sense. impl_finalize never calls add_mtp_track_to_db, which never calls impl_get_free_space, which never calls rhythmdb_set_property, which never calls rhythmdb_commit_internal.
Looks like apport screwed up when retracing this one. The stack trace from the original submitter lacks detail but is at least plausible:
+ Trace 221293
Thread 1 (Thread 3031)
I'll ask the reporter for a new one, thanks for looking into this Jonathan.
Created attachment 171083 [details] gdb bt from crash Hello! I think I just hit the same bug with my gentoo x86_64 build. I was trying to connect my iRiver clix player to rhythmbox (mtp support). Attaching gdb backtrace.
-- 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/903.