Description of problem: i reall Version-Release number of selected component: rhythmbox-2.98-4.fc18 Additional info: backtrace_rating: 4 cmdline: rhythmbox crash_function: g_thread_new executable: /usr/bin/rhythmbox kernel: 3.7.4-204.fc18.i686 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #2 g_thread_new at gthread.c:838 #3 rhythmdb_thread_create at rhythmdb.c:1194 #4 rhythmdb_save_async at rhythmdb.c:3156 #5 rhythmdb_idle_save at rhythmdb.c:4677 #11 g_main_context_iteration at gmain.c:3351 #12 g_application_run at gapplication.c:1624
Created attachment 688919 [details] File: backtrace
Created attachment 688920 [details] File: build_ids
Created attachment 688921 [details] File: cgroup
Created attachment 688922 [details] File: core_backtrace
Created attachment 688923 [details] File: dso_list
Created attachment 688924 [details] File: environ
Created attachment 688925 [details] File: limits
Created attachment 688926 [details] File: maps
Created attachment 688927 [details] File: open_fds
Created attachment 688928 [details] File: proc_pid_status
Created attachment 688929 [details] File: smolt_data
Created attachment 688930 [details] File: var_log_messages
I do not know how this problem started. I unlocked my screen this morning and I had an alert that rhythmbox had crashed. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/bin/rhythmbox crash_function: g_thread_new executable: /usr/bin/rhythmbox kernel: 3.10.4-100.fc18.i686 package: rhythmbox-2.98-4.fc18 reason: Process /usr/bin/rhythmbox was killed by signal 5 (SIGTRAP) 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.