After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 720172 - Crash in rb_list_model_find when importing songs(?)
Crash in rb_list_model_find when importing songs(?)
Status: RESOLVED DUPLICATE of bug 724931
Product: rhythmbox
Classification: Other
Component: Importing
3.0
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-12-10 04:33 UTC by Adam Williamson
Modified: 2014-03-08 08:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace from downstream bug (38.43 KB, text/plain)
2013-12-10 04:34 UTC, Adam Williamson
Details

Description Adam Williamson 2013-12-10 04:33:31 UTC
Filed downstream as https://bugzilla.redhat.com/show_bug.cgi?id=1013858 , thought it would be worth reporting upstream too.

Rhythmbox (rhythmbox-3.0-3.fc20.x86_64) seems to crash relatively often after importing tracks, with this traceback:

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

(full trace will be attached). I hit it multiple times over the last two days while transferring tracks to an SD card and cleaning my library as I went; I'd find some wrongly-located files, say, remove them from the RB database, move the files, use the 'add songs' page to add them back into the RB database, and it'd crash on completion.
Comment 1 Adam Williamson 2013-12-10 04:34:06 UTC
Created attachment 263884 [details]
backtrace from downstream bug
Comment 2 Jonathan Matthew 2014-03-08 08:06:32 UTC

*** This bug has been marked as a duplicate of bug 724931 ***