Description of problem: Crash after importing 5 FLAC songs in the library (at the end, I guess, since on restart the new songs appeared in matter of seconds). It took a lot of time for the import, and I believe rhythmbox was also scanning the library in the mean time. Version-Release number of selected component: rhythmbox-3.0-3.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: rhythmbox crash_function: rb_list_model_find executable: /usr/bin/rhythmbox kernel: 3.11.1-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 rb_list_model_find at rb-list-model.c:179 #1 rb_list_model_remove_item at rb-list-model.c:277 #2 task_expired at rb-task-list.c:138 #7 g_main_context_iteration at gmain.c:3773 #8 g_application_run at gapplication.c:1635 #9 rb_application_run at rb-application.c:646
Created attachment 805645 [details] File: backtrace
Created attachment 805646 [details] File: cgroup
Created attachment 805647 [details] File: core_backtrace
Created attachment 805648 [details] File: dso_list
Created attachment 805649 [details] File: environ
Created attachment 805650 [details] File: exploitable
Created attachment 805651 [details] File: limits
Created attachment 805652 [details] File: maps
Created attachment 805653 [details] File: open_fds
Created attachment 805654 [details] File: proc_pid_status
Created attachment 805655 [details] File: var_log_messages
I've been transferring a large number of songs to an SD card, and doing a few library cleanups (= file renames, moves, and re-imports into RB) as I go. I've hit this crash five times now.
Another user experienced a similar problem: Crash. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: rhythmbox crash_function: rb_list_model_find executable: /usr/bin/rhythmbox kernel: 3.11.10-301.fc20.x86_64 package: rhythmbox-3.0.1-1.fc20 reason: rhythmbox killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I have the same problem with importing flac files. First I couldn't import them because the flac rpm wasn't installed and after installing it Rhythmbox now crashes while trying to import them.
Same for me here, this time importing mp3 files, althought I have bunch of flac files in my library, if you want more information I can reproduce the crash whenever I want :) This is the output in the terminal if it's of some help: (rhythmbox:5043): Rhythmbox-CRITICAL **: rb_list_model_remove: assertion 'index >= 0' failed (rhythmbox:5043): Rhythmbox-CRITICAL **: rb_list_model_remove: assertion 'index >= 0' failed (rhythmbox:5043): Rhythmbox-CRITICAL **: rb_list_model_remove: assertion 'index >= 0' failed (rhythmbox:5043): Rhythmbox-CRITICAL **: rb_list_model_remove: assertion 'index >= 0' failed (rhythmbox:5043): Rhythmbox-CRITICAL **: rb_list_model_remove: assertion 'index >= 0' failed Segmentation fault (core dumped)
I just imported my music library.. it listed all music files in the mainfolder but didnt seem to recognize the subfolders. I just wanted to try it quick, aborted it then and just listened to the music, that was already playing when it suddenly died - so my guess is, it is hanging somewhere while scanning through subfolders - and maybe that thread timing out causes a crash *wild guess*
And I too am hitting this failure, according to abrt. Will there be any update to fix it? It makes RB pretty useless to not be able to import music into it.
This is opened in an upstream bug at https://bugzilla.gnome.org/show_bug.cgi?id=724931 with a request to confirm if "commit fa1a2e8" fixes it. Can we get a new revision of this with the above applied?
I should be able to do a scratch build, just a sec.
Both F20 and Rawhide are on 3.0.2, which includes that commit. They've been on it since around March 23rd, looks like. If you've hit this crash since then, with rhythmbox 3.0.2 installed, we can likely re-open the upstream bug report. You should be able to check from abrt when was the most recent time you've hit this crash, and compare it to the date rhythmbox got updated to 3.0.2 from 'yum history rhythmbox | less'.
So then why won't abrt upload data to this bug about the new version so that it can be pointed to by upstream because they are surely going to want to see a stack trace, etc. from the new version that they think it's fixed in.
if abrt sends you to an existing report, it's because it thinks the trace you're hitting matches the trace in that bug report. so in this case, when upstream asked you if the trace was the same, it'd be fairly safe to say 'yes'. of course, eyeballing it is always the *best* thing to do, so thanks for that.
Looks like upstream has a fix for this: https://bugzilla.gnome.org/show_bug.cgi?id=724931#c8 I wonder if we can get a build with that patch applied.
Was already working on it. Patched build is sent to Rawhide already, for F20 I have a scratch build running: http://koji.fedoraproject.org/koji/taskinfo?taskID=6883650 please let me know if that helps.
(In reply to Adam Williamson from comment #24) > Was already working on it. :-) > for F20 > I have a scratch build running: > > http://koji.fedoraproject.org/koji/taskinfo?taskID=6883650 > > please let me know if that helps. Tons! No more crashing. Much thanks Adam!
No problems. I guess I'll send it out as an update, then.
rhythmbox-3.0.2-1.fc20.2 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/rhythmbox-3.0.2-1.fc20.2
Package rhythmbox-3.0.2-1.fc20.2: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing rhythmbox-3.0.2-1.fc20.2' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-6638/rhythmbox-3.0.2-1.fc20.2 then log in and leave karma (feedback).
rhythmbox-3.0.3-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/rhythmbox-3.0.3-1.fc20
rhythmbox-3.0.3-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.