Description of problem: First, I connected my older iPod Nano (2nd generation) to my computer. It mounted, Nautlius recognized it, and I could view files. I went to Rhythmbox to manage the music. While browsing through the music on the iPod, I went and deleted a song from the iPod. In about 3 seconds, Rhythmbox crashed. I checked on my iPod, and the song was deleted. Before submitting this report, I tried it again to see if this was a one-time occurrence. I tried to delete other songs, and Rhythmbox crashed again, and those songs were not deleted. (In the second occurrence, I tried to delete multiple songs at once. Version-Release number of selected component: rhythmbox-3.0.2-1.fc20.1 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: rhythmbox crash_function: g_str_hash executable: /usr/bin/rhythmbox kernel: 3.14.2-200.fc20.x86_64 runlevel: unknown type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_str_hash at ghash.c:1732 #1 g_hash_table_lookup_node at ghash.c:365 #2 g_hash_table_lookup at ghash.c:1076 #3 write_podcast_mhips at itdb_itunesdb.c:5432 #4 write_playlist at itdb_itunesdb.c:5589 #5 write_mhsd_playlists at itdb_itunesdb.c:5638 #6 itdb_write_file_internal at itdb_itunesdb.c:6043 #7 itdb_write at itdb_itunesdb.c:6245 #8 rb_itdb_save at rb-ipod-db.c:137 #9 saving_thread at rb-ipod-db.c:863 Potential duplicate: bug 699290
Created attachment 894314 [details] File: backtrace
Created attachment 894315 [details] File: cgroup
Created attachment 894316 [details] File: core_backtrace
Created attachment 894317 [details] File: dso_list
Created attachment 894318 [details] File: environ
Created attachment 894319 [details] File: exploitable
Created attachment 894320 [details] File: limits
Created attachment 894321 [details] File: maps
Created attachment 894322 [details] File: open_fds
Created attachment 894323 [details] File: proc_pid_status
Created attachment 894324 [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.