Hide Forgot
Description of problem: I had rythmbox setup to use music from an smb share on a synology DS212j. I moved the underlying song files on the nas and forgot about it, so when I clicked on a song in rythmbox it removed the song. When I realized what had happened I then clicked the first song of that artist (there were about 40 songs). As I figured, rythmbox removed all the songs, since it could no longer map them to the NAS box location. I thought, "perfect" I'll do that with all the songs and then re-add them from the new location. So, I opened up the top-level browse window in rythmbox, selected the first song in my collection and watched it start to remove them all... within about 10 seconds, rythmbox crashed. Version-Release number of selected component: rhythmbox-2.99.1-1.fc19 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: rhythmbox crash_function: tdb_nest_lock executable: /usr/bin/rhythmbox kernel: 3.11.9-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 tdb_nest_lock at ../common/lock.c:315 #1 tdb_lock at ../common/lock.c:419 #2 tdb_find_lock_hash at ../common/tdb.c:118 #3 _tdb_fetch at ../common/tdb.c:196 #4 tdb_fetch at ../common/tdb.c:208 #5 do_store_request at rb-ext-db.c:816 #6 run_in_thread at gsimpleasyncresult.c:871 #7 io_job_thread at gioscheduler.c:89 #8 g_task_thread_pool_thread at gtask.c:1242 #10 g_thread_proxy at gthread.c:798 Potential duplicate: bug 914884
Created attachment 839117 [details] File: backtrace
Created attachment 839118 [details] File: cgroup
Created attachment 839119 [details] File: core_backtrace
Created attachment 839120 [details] File: dso_list
Created attachment 839121 [details] File: environ
Created attachment 839122 [details] File: exploitable
Created attachment 839123 [details] File: limits
Created attachment 839124 [details] File: maps
Created attachment 839125 [details] File: open_fds
Created attachment 839126 [details] File: proc_pid_status
Created attachment 839127 [details] File: var_log_messages
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.