Bug 1388030

Summary: [abrt] gnome-mahjongg: _g_log_abort(): gnome-mahjongg killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Retro Geek <retrogeek>
Component: gnome-mahjonggAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: mcatanzaro+wrong-account-do-not-cc, mclasen, retrogeek
Target Milestone: ---Flags: mcatanzaro+wrong-account-do-not-cc: needinfo? (retrogeek)
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ae534a1fe31f699500ac5df592fa2eb85eb862b3
Whiteboard: abrt_hash:af2015d1de056842ce216027e8b87e4d1159fdc3;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:49:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Retro Geek 2016-10-24 09:21:18 UTC 
Description of problem:
I opened 	YUM went to groups/applications/games and entertainment and selected four games to install gnome-mahjongg, gnome-sudoku, gnome-tetravex, and gnubg ten I nodded off for a few minutes. when I tryed to run the games the only one that would start was the gnubg.

Version-Release number of selected component:
gnome-mahjongg-3.22.0-1.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        gnome-mahjongg
crash_function: _g_log_abort
executable:     /usr/bin/gnome-mahjongg
global_pid:     2212
kernel:         4.8.3-300.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _g_log_abort at gmessages.c:487
 #1 g_log_default_handler at gmessages.c:2813
 #4 g_settings_set_property at gsettings.c:590
 #5 object_set_property at gobject.c:1423
 #6 g_object_new_internal at gobject.c:1817
 #7 g_object_new_valist at gobject.c:2042
 #9 mahjongg_real_startup at /home/mcatanzaro/src/jhbuild/checkout/gnome-mahjongg/src/gnome-mahjongg.vala:70
 #14 g_application_register at gapplication.c:2049
 #15 g_application_real_local_command_line at gapplication.c:1012
 #16 g_application_run at gapplication.c:2350
Comment 1 Retro Geek 2016-10-24 09:21:24 UTC 
Created attachment 1213397 [details]
File: backtrace
Comment 2 Retro Geek 2016-10-24 09:21:25 UTC 
Created attachment 1213398 [details]
File: cgroup
Comment 3 Retro Geek 2016-10-24 09:21:27 UTC 
Created attachment 1213399 [details]
File: core_backtrace
Comment 4 Retro Geek 2016-10-24 09:21:28 UTC 
Created attachment 1213400 [details]
File: dso_list
Comment 5 Retro Geek 2016-10-24 09:21:30 UTC 
Created attachment 1213401 [details]
File: environ
Comment 6 Retro Geek 2016-10-24 09:21:31 UTC 
Created attachment 1213402 [details]
File: limits
Comment 7 Retro Geek 2016-10-24 09:21:36 UTC 
Created attachment 1213403 [details]
File: maps
Comment 8 Retro Geek 2016-10-24 09:21:38 UTC 
Created attachment 1213404 [details]
File: mountinfo
Comment 9 Retro Geek 2016-10-24 09:21:39 UTC 
Created attachment 1213405 [details]
File: namespaces
Comment 10 Retro Geek 2016-10-24 09:21:40 UTC 
Created attachment 1213406 [details]
File: open_fds
Comment 11 Retro Geek 2016-10-24 09:21:42 UTC 
Created attachment 1213407 [details]
File: proc_pid_status
Comment 12 Retro Geek 2016-10-24 09:21:43 UTC 
Created attachment 1213408 [details]
File: var_log_messages
Comment 13 Michael Catanzaro 2016-10-24 13:31:01 UTC 
The spec file looks fine. Any idea why the settings schema is not installed?
Comment 14 Fedora End Of Life 2017-11-16 14:31:07 UTC 
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora  'version'
of '25'.

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 25 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 15 Fedora End Of Life 2017-12-12 10:49:49 UTC 
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.