Description of problem: open properties, set 3D with smoothing, then close properties, move pawn, the opponent even does not reposnd (the easy level was selected), then click to properties again, and it crashes Version-Release number of selected component: gnome-chess-3.10.2-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gnome-chess crash_function: chess_game_get_piece executable: /usr/bin/gnome-chess kernel: 3.14.8-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 chess_game_get_piece at /home/mcatanzaro/jhbuild/src/gnome-chess/src/chess-game.vala:1507 #1 chess_scene_update_board at /home/mcatanzaro/jhbuild/src/gnome-chess/src/chess-scene.vala:290 #2 chess_scene_set_move_number at /home/mcatanzaro/jhbuild/src/gnome-chess/src/chess-scene.vala:127 #3 history_combo_changed_cb at /home/mcatanzaro/jhbuild/src/gnome-chess/src/gnome-chess.vala:1417 #4 _g_closure_invoke_va at gclosure.c:840 #7 gtk_combo_box_set_active_internal at gtkcombobox.c:4396 #8 gtk_combo_box_set_active_iter at gtkcombobox.c:4454 #9 application_game_undo_cb at /home/mcatanzaro/jhbuild/src/gnome-chess/src/gnome-chess.vala:990 #10 _application_game_undo_cb_chess_game_undo at /home/mcatanzaro/jhbuild/src/gnome-chess/src/gnome-chess.vala:486 #14 g_signal_emit_by_name at gsignal.c:3426
Created attachment 911112 [details] File: backtrace
Created attachment 911113 [details] File: cgroup
Created attachment 911114 [details] File: core_backtrace
Created attachment 911115 [details] File: dso_list
Created attachment 911116 [details] File: environ
Created attachment 911117 [details] File: exploitable
Created attachment 911118 [details] File: limits
Created attachment 911119 [details] File: maps
Created attachment 911120 [details] File: open_fds
Created attachment 911121 [details] File: proc_pid_status
Created attachment 911122 [details] File: var_log_messages
You must have also pressed Undo at some point during that, perhaps right before it crashed?
I guess somehow an invalid state was pushed onto the undo stack. I have no idea how that could have happened. :( It might be a race condition exposed because smooth 3D mode makes everything so slow. If you're able to reproduce this (I have not been able to), it would be super helpful to have more detail.
Stable reproducing: press button 'new game', click abandon game, then clicking 'new game' about 20 times very quickly, after open properties, and close them. After the move of any piece there will be a bug. If you will not open properties, there will be "Ooops! Something has gone wrong. The game cannot continue."
* after all of this manipulations, you can press 'undo move', and that's SIGSEGV
OK, now I can reproduce it, thanks. The ChessState is invalid. :/ ** (glchess:26159): CRITICAL **: chess_state_get_index: assertion 'self != NULL' failed
This one is not looking easy, so I filed it for myself upstream: https://bugzilla.gnome.org/show_bug.cgi?id=732067 It's "fixed" in 3.12, but probably only incidentally, and impossible to bisect for about three unrelated reasons....
I think this is a bug in Vala. [1] Anyway, I've released 3.10.4 with a workaround that should prevent this crash. (It honestly isn't significant enough to merit a new release in itself, but I wanted a new release anyway to fix the size of the widgets in the bottom bar.) Tanner, would you be willing to do a Fedora update? [1] https://bugzilla.gnome.org/show_bug.cgi?id=708130#c9
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.