Bug 919715 - [abrt] gnome-terminal-3.7.91-1.fc19: g_settings_schema_get_value: Process /usr/libexec/gnome-terminal-server was killed by signal 5 (SIGTRAP)
Summary: [abrt] gnome-terminal-3.7.91-1.fc19: g_settings_schema_get_value: Process /us...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6733c5beaf3a44063c499db708d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-09 18:24 UTC by Alexander Ivanov
Modified: 2015-02-17 14:50 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:50:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (36.80 KB, text/plain)
2013-03-09 18:24 UTC, Alexander Ivanov
no flags Details
File: cgroup (131 bytes, text/plain)
2013-03-09 18:24 UTC, Alexander Ivanov
no flags Details
File: core_backtrace (3.34 KB, text/plain)
2013-03-09 18:25 UTC, Alexander Ivanov
no flags Details
File: dso_list (9.64 KB, text/plain)
2013-03-09 18:25 UTC, Alexander Ivanov
no flags Details
File: environ (2.43 KB, text/plain)
2013-03-09 18:25 UTC, Alexander Ivanov
no flags Details
File: limits (1.29 KB, text/plain)
2013-03-09 18:25 UTC, Alexander Ivanov
no flags Details
File: maps (48.28 KB, text/plain)
2013-03-09 18:25 UTC, Alexander Ivanov
no flags Details
File: open_fds (833 bytes, text/plain)
2013-03-09 18:25 UTC, Alexander Ivanov
no flags Details
File: proc_pid_status (942 bytes, text/plain)
2013-03-09 18:25 UTC, Alexander Ivanov
no flags Details
File: var_log_messages (508 bytes, text/plain)
2013-03-09 18:25 UTC, Alexander Ivanov
no flags Details

Description Alexander Ivanov 2013-03-09 18:24:53 UTC
Description of problem:
1. Open gnome-tweak-tool
2. Change monospace font

Version-Release number of selected component:
gnome-terminal-3.7.91-1.fc19

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-terminal-server
crash_function: g_settings_schema_get_value
executable:     /usr/libexec/gnome-terminal-server
kernel:         3.9.0-0.rc1.git0.4.fc19.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_settings_schema_get_value at gsettingsschema.c:640
 #3 g_settings_schema_key_init at gsettingsschema.c:751
 #4 g_settings_get_value at gsettings.c:1079
 #5 g_settings_get_boolean at gsettings.c:1785
 #6 terminal_screen_system_font_changed_cb at terminal-screen.c:1011
 #7 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1004
 #8 _g_closure_invoke_va at gclosure.c:840
 #11 g_settings_real_change_event at gsettings.c:288
 #12 ffi_call_unix64 at ../src/x86/unix64.S:75
 #13 ffi_call at ../src/x86/ffi64.c:492

Comment 1 Alexander Ivanov 2013-03-09 18:24:56 UTC
Created attachment 707454 [details]
File: backtrace

Comment 2 Alexander Ivanov 2013-03-09 18:24:58 UTC
Created attachment 707455 [details]
File: cgroup

Comment 3 Alexander Ivanov 2013-03-09 18:25:00 UTC
Created attachment 707456 [details]
File: core_backtrace

Comment 4 Alexander Ivanov 2013-03-09 18:25:02 UTC
Created attachment 707457 [details]
File: dso_list

Comment 5 Alexander Ivanov 2013-03-09 18:25:04 UTC
Created attachment 707458 [details]
File: environ

Comment 6 Alexander Ivanov 2013-03-09 18:25:06 UTC
Created attachment 707459 [details]
File: limits

Comment 7 Alexander Ivanov 2013-03-09 18:25:09 UTC
Created attachment 707460 [details]
File: maps

Comment 8 Alexander Ivanov 2013-03-09 18:25:11 UTC
Created attachment 707461 [details]
File: open_fds

Comment 9 Alexander Ivanov 2013-03-09 18:25:13 UTC
Created attachment 707462 [details]
File: proc_pid_status

Comment 10 Alexander Ivanov 2013-03-09 18:25:15 UTC
Created attachment 707463 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2013-04-03 16:13:01 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 12 Fedora End Of Life 2015-01-09 17:45:16 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.

Comment 13 Fedora End Of Life 2015-02-17 14:50:43 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.


Note You need to log in before you can comment on or make changes to this bug.