Description of problem: I was adding an external 80 Gb HD of mixed music files when it crashed. Version-Release number of selected component: rhythmbox-2.98-4.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/rhythmbox-metadata unix:tmpdir=/tmp crash_function: type_check_is_value_type_U executable: /usr/libexec/rhythmbox-metadata kernel: 3.6.7-5.fc18.i686.PAE remote_result: NOTFOUND uid: 1000 var_log_messages: Nov 27 11:56:42 localhost abrt[17468]: Saved core dump of pid 17310 (/usr/libexec/rhythmbox-metadata) to /var/spool/abrt/ccpp-2012-11-27-11:56:41-17310 (55541760 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 type_check_is_value_type_U at gtype.c:4096 #1 g_type_check_value at gtype.c:4138 #2 gst_value_init_and_copy at gstvalue.c:4007 #3 gst_structure_copy at gststructure.c:312 #4 gst_tag_list_copy at gsttaglist.c:985 #5 _g_type_boxed_copy at gtype.c:4237 #6 boxed_proxy_collect_value at gboxed.c:230 #7 gst_structure_id_set_valist_internal at gststructure.c:642 #8 gst_structure_id_set at gststructure.c:676 #9 collect_stream_information at gstdiscoverer.c:605 Potential duplicate: bug 744557
Created attachment 652932 [details] File: backtrace
Created attachment 652933 [details] File: cgroup
Created attachment 652934 [details] File: core_backtrace
Created attachment 652935 [details] File: dso_list
Created attachment 652936 [details] File: environ
Created attachment 652937 [details] File: limits
Created attachment 652938 [details] File: maps
Created attachment 652939 [details] File: open_fds
Created attachment 652940 [details] File: proc_pid_status
To the best of my recollection, at first I couldn't get it to play at all. Then I tried Banshee instead, and downloaded the codec or whatever for Mp3 files to play. But then I tried Rhythmbox again and it seemed to work. It downloaded all the music and I probably didn't give it time to finish. When I started it back up it had only 2 songs on it instead of 500. Still, the song it wanted to play was not even on the list. I would click on "import" and it would fill right up, but even if I could get it to play a song on the list, it would go back to that one favorite song it had or just stop. I'm sure I didn't give it time to properly import all the songs. I got fed up and turned it off a few times not thinking that I should have given it some time initially. I am just a point and click kind of guy, as is surely evident. Banshee kept crashing so I uninstalled it. backtrace_rating: 4 Package: rhythmbox-2.98-4.fc18 OS Release: Fedora release 18 (Spherical Cow)
Rhythmbox always shows error when starting up and scanning my music library. backtrace_rating: 4 Package: rhythmbox-2.98-4.fc18 Architecture: x86_64 OS Release: Fedora release 18 (Spherical Cow)
adding music library reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/libexec/rhythmbox-metadata unix:tmpdir=/tmp crash_function: type_check_is_value_type_U executable: /usr/libexec/rhythmbox-metadata kernel: 3.9.6-200.fc18.i686 package: rhythmbox-2.98-4.fc18 reason: Process /usr/libexec/rhythmbox-metadata was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.