Red Hat Bugzilla – Bug 861455
[abrt] python-2.7.3-7.2.fc17: g_settings_schema_get_value: Process /usr/bin/python2.7 was killed by signal 5 (SIGTRAP)
Last modified: 2013-08-01 00:22:51 EDT
Version-Release number of selected component:
libreport version: 2.0.13
cmdline: python /usr/bin/gnome-sudoku
:Thread no. 1 (10 frames)
: #2 g_settings_schema_get_value at gsettingsschema.c
: #3 g_settings_schema_key_init at gsettingsschema.c
: #4 g_settings_get_value at gsettings.c
: #5 g_settings_get_boolean at gsettings.c
: #6 ffi_call_SYSV at ../src/x86/sysv.S
: #7 ffi_call at ../src/x86/ffi.c
: #8 g_callable_info_invoke at girepository/gicallableinfo.c
: #9 g_function_info_invoke at girepository/gifunctioninfo.c
: #10 _invoke_callable at pygi-invoke.c
: #11 _wrap_g_callable_info_invoke at pygi-invoke.c
Created attachment 618688 [details]
Created attachment 618689 [details]
Created attachment 618690 [details]
Created attachment 618691 [details]
Created attachment 618692 [details]
Created attachment 618693 [details]
Created attachment 618694 [details]
Created attachment 618695 [details]
Created attachment 618696 [details]
*** Bug 875017 has been marked as a duplicate of this bug. ***
Thanks for filing these bug reports.
Looking at attachment 618691 [details] in thread 1 I see that gnome-sudoku was attempting to read the gsettings value "always_show_hints" but was issuing an error message using this format string:
"Settings schema '%s' does not contain a key named '%s'"
Reassigning from python to gnome-sudoku for now (but could be a bug in gsettings, I guess).
(In reply to comment #11)
> Reassigning from python to gnome-sudoku for now (but could be a bug in
> gsettings, I guess).
gnome-sudoku appears to currently be orphaned; reassigning again, this time to glib2 (which gsettings is part of). (Might also perhaps be an issue with the dynamic invocation of the gsettings code through pygobject/gir file???)
In sudoku, enter some top notes, then use either the menu or the keyboard shortcut (Ctrl+J) to attempt to clear them all.
OS Release: Fedora release 18 (Spherical Cow)
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.
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.