Bug 969844

Summary: [abrt] rhythmbox-2.98-4.fc18: g_thread_new: Process /usr/bin/rhythmbox was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: hx
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e9698309e8cd507216f4eb28c8d6b9a38a7320bd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 21:38:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description hx 2013-06-02 16:52:08 UTC 
Version-Release number of selected component:
rhythmbox-2.98-4.fc18

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        rhythmbox
crash_function: g_thread_new
executable:     /usr/bin/rhythmbox
kernel:         3.9.4-200.fc18.x86_64
runlevel:       N 5
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (7 frames)
 #2 g_thread_new at gthread.c:838
 #3 rb_uri_handle_recursively_async at rb-file-helpers.c:967
 #4 monitor_library_directory at rhythmdb-monitor.c:179
 #5 rhythmdb_start_monitoring at rhythmdb-monitor.c:229
 #6 rhythmdb_sync_library_idle at rhythmdb.c:3024
 #11 g_main_context_iteration at gmain.c:3351
 #12 g_application_run at gapplication.c:1624
Comment 1 hx 2013-06-02 16:52:12 UTC 
Created attachment 756027 [details]
File: backtrace
Comment 2 hx 2013-06-02 16:52:14 UTC 
Created attachment 756028 [details]
File: cgroup
Comment 3 hx 2013-06-02 16:52:17 UTC 
Created attachment 756029 [details]
File: core_backtrace
Comment 4 hx 2013-06-02 16:52:21 UTC 
Created attachment 756030 [details]
File: dso_list
Comment 5 hx 2013-06-02 16:52:24 UTC 
Created attachment 756031 [details]
File: environ
Comment 6 hx 2013-06-02 16:52:27 UTC 
Created attachment 756032 [details]
File: limits
Comment 7 hx 2013-06-02 16:52:32 UTC 
Created attachment 756033 [details]
File: maps
Comment 8 hx 2013-06-02 16:52:35 UTC 
Created attachment 756034 [details]
File: open_fds
Comment 9 hx 2013-06-02 16:52:38 UTC 
Created attachment 756035 [details]
File: proc_pid_status
Comment 10 hx 2013-06-02 16:52:40 UTC 
Created attachment 756036 [details]
File: var_log_messages
Comment 11 Fedora End Of Life 2013-12-21 13:49:54 UTC 
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.
Comment 12 Fedora End Of Life 2014-02-05 21:38:21 UTC 
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.