Hide Forgot
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
Created attachment 1213397 [details] File: backtrace
Created attachment 1213398 [details] File: cgroup
Created attachment 1213399 [details] File: core_backtrace
Created attachment 1213400 [details] File: dso_list
Created attachment 1213401 [details] File: environ
Created attachment 1213402 [details] File: limits
Created attachment 1213403 [details] File: maps
Created attachment 1213404 [details] File: mountinfo
Created attachment 1213405 [details] File: namespaces
Created attachment 1213406 [details] File: open_fds
Created attachment 1213407 [details] File: proc_pid_status
Created attachment 1213408 [details] File: var_log_messages
The spec file looks fine. Any idea why the settings schema is not installed?
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.
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.