Description of problem: Changed the location of the rhythmbox music folder. Version-Release number of selected component: rhythmbox-3.0.1-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: rhythmbox crash_function: g_hash_table_lookup_node executable: /usr/bin/rhythmbox kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 g_hash_table_lookup_node at ghash.c:365 #2 g_hash_table_remove_internal at ghash.c:1271 #3 remove_child at rhythmdb-tree.c:1524 #4 remove_entry_from_album at rhythmdb-tree.c:1545 #5 rhythmdb_tree_entry_delete at rhythmdb-tree.c:1713 #6 rhythmdb_entry_delete at rhythmdb.c:3742 #7 song_update_availability at rhythmdb-song-entry-types.c:171 #8 rhythmdb_process_stat_event at rhythmdb.c:2110 #9 rhythmdb_process_one_event at rhythmdb.c:2518 #10 rb_async_queue_watch_dispatch at rb-async-queue-watch.c:85 Potential duplicate: bug 859722
Created attachment 840654 [details] File: backtrace
Created attachment 840655 [details] File: cgroup
Created attachment 840656 [details] File: core_backtrace
Created attachment 840657 [details] File: dso_list
Created attachment 840658 [details] File: environ
Created attachment 840659 [details] File: exploitable
Created attachment 840660 [details] File: limits
Created attachment 840661 [details] File: maps
Created attachment 840662 [details] File: open_fds
Created attachment 840663 [details] File: proc_pid_status
Created attachment 840664 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.