GNOME Bugzilla – Bug 753650
gnome-2048 crashes at startup
Last modified: 2015-08-22 02:38:17 UTC
Created attachment 309324 [details] gdb log for gnome-2048 I'm trying to run gnome-2048 but I get the following error message: ----- $ gnome-2048 ** (gnome-2048:21403): ERROR **: context.vala:203: The application window associated with the GamesScoresContext was set visible before the Context was constructed. The Context performs synchronous I/O in the default main context to load scores when it is constructed, so you should create the Context before showing your main window. Trace/breakpoint trap (core dumped) ----- I'm attaching the gdb backtrace obtained by running the following gdb command: (gdb) thread apply all bt full ----- The GNU/Linux distribution I'm using is Parabola GNU/Linux-libre. I had to rebuild the following packages in order to obtain a valid backtrace: Name : gnome-2048-git Version : 3.17.1.r98.c43ffc2-1 Name : libgames-support-git Version : 0.1.r191.4f21820-1 Name : glib2 Version : 2.44.1-1 Name : dconf Version : 0.24.0-1 ----- Please tell me if you need other details.
Happens on Continuous too, version 3.17.1-4-gc43ffc268b6fca704a713260a759217690caa70b: Stack trace of thread 933: #0 0x00007f1c1116a500 g_logv (libglib-2.0.so.0) #1 0x00007f1c1116a732 g_log (libglib-2.0.so.0) #2 0x00007f1c13415cd2 n/a (libgames-support.so.0) #3 0x00007f1c13416de7 games_scores_context_has_scores (libgames-support.so.0) #4 0x00000000004070dd n/a (gnome-2048) #5 0x00007f1c114620a4 n/a (libgobject-2.0.so.0) #6 0x00007f1c1147bfc8 g_signal_emit_valist (libgobject-2.0.so.0) #7 0x00007f1c1147c8b2 g_signal_emit (libgobject-2.0.so.0) #8 0x00007f1c11750866 n/a (libgio-2.0.so.0) #9 0x00007f1c11750a42 g_application_run (libgio-2.0.so.0) #10 0x0000000000407be9 n/a (gnome-2048) #11 0x00007f1c10877050 __libc_start_main (libc.so.6) #12 0x0000000000405c13 n/a (gnome-2048)
FWIW, the crash is there just to ensure we don't forget about bug #746774. We will fix this before the first release of libgames-support, since it's obviously a blocker issue. Packaging unreleased git snapshots is not recommended ;) but since you've done so, you can just remove the call to g_error() that is causing the crash. *** This bug has been marked as a duplicate of bug 746774 ***
wrt 2048 what happened here I think is that this was fixed/workedaround by e6083a815190531a84da67184f667cad0e2addb3 which can be found in 3.17,90