Bug 863803

Summary: [abrt] rhythmbox-2.96-3.fc17: g_logv: Process /usr/bin/rhythmbox was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: ppxqaz <px37774832>
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:93088ad0d394682a98250f43410d039602b804a6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 21:07:33 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: open_fds
none
File: environ
none
File: build_ids
none
File: cgroup
none
File: maps
none
File: limits
none
File: backtrace none

Description ppxqaz 2012-10-07 14:36:56 UTC 
Version-Release number of selected component:
rhythmbox-2.96-3.fc17

Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
backtrace_rating: 4
cmdline:        rhythmbox
crash_function: g_logv
kernel:         3.5.4-2.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 g_logv at gmessages.h:101
: #2 g_settings_schema_get_value at gsettingsschema.c:640
: #3 g_settings_schema_key_init at gsettingsschema.c:751
: #4 g_settings_bind_with_mapping at gsettings.c:2604
: #5 g_settings_bind at gsettings.c:2548
: #6 rb_shell_startup at rb-shell.c:1147
: #7 _g_closure_invoke_va at gclosure.c:840
: #10 g_application_register at gapplication.c:1201
: #11 rb_shell_local_command_line at rb-shell.c:1230
: #12 g_application_run at gapplication.c:1449
Comment 1 ppxqaz 2012-10-07 14:36:59 UTC 
Created attachment 622988 [details]
File: open_fds
Comment 2 ppxqaz 2012-10-07 14:37:02 UTC 
Created attachment 622989 [details]
File: environ
Comment 3 ppxqaz 2012-10-07 14:37:05 UTC 
Created attachment 622990 [details]
File: build_ids
Comment 4 ppxqaz 2012-10-07 14:37:08 UTC 
Created attachment 622991 [details]
File: cgroup
Comment 5 ppxqaz 2012-10-07 14:37:12 UTC 
Created attachment 622992 [details]
File: maps
Comment 6 ppxqaz 2012-10-07 14:37:15 UTC 
Created attachment 622993 [details]
File: limits
Comment 7 ppxqaz 2012-10-07 14:37:18 UTC 
Created attachment 622994 [details]
File: backtrace
Comment 8 Fedora End Of Life 2013-07-03 20:45:51 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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 9 Fedora End Of Life 2013-07-31 21:07:36 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.