gnubik fails to launch; prints "cannot get suitable visual" to terminal and exits
Bug #318180 reported by
Martin Olsson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnubik (Ubuntu) |
Fix Released
|
Undecided
|
I. De Marchi | ||
Bug Description
Repro steps:
1. sudo apt-get install gnubik
2. launch "gnubik" from Applications:
3. start a terminal and type "gnubik", then it prints this error:
mnemo@kingfish:~$ gnubik
** ERROR **: Cannot get a suitable visual
aborting...
Trace/breakpoint trap (core dumped)
Changed in gnubik (Ubuntu): | |
status: | New → Fix Released |
assignee: | nobody → I. De Marchi (tangram-peces) |
To post a comment you must log in.
GDB says something goes wrong in function create_gl_area()
(gdb) r
Starting program: /usr/games/gnubik
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f79f3b327f0 (LWP 4837)]
** ERROR **: Cannot get a suitable visual
aborting...
Program received signal SIGTRAP, Trace/breakpoint trap. G_LOG_LEVEL_ ERROR, format=0x412465 "Cannot get a suitable visual", args1=0x7ffffbb 6ad20) buildd/ glib2.0- 2.19.4/ glib/gmessages. c:503 buildd/ glib2.0- 2.19.4/ glib/gmessages. c: No such file or directory. buildd/ glib2.0- 2.19.4/ glib/gmessages. c G_LOG_LEVEL_ ERROR, format=0x412465 "Cannot get a suitable visual", args1=0x7ffffbb 6ad20) buildd/ glib2.0- 2.19.4/ glib/gmessages. c:503 0x7f79ee7a0a00 "", log_level= -296291000, format=0x31 <Address 0x31 out of bounds>) buildd/ glib2.0- 2.19.4/ glib/gmessages. c:517 libguile. so.12
[Switching to Thread 0x7f79f3b327f0 (LWP 4837)]
IA__g_logv (log_domain=0x0, log_level=
at /build/
503 /build/
in /build/
(gdb) bt
#0 IA__g_logv (log_domain=0x0, log_level=
at /build/
#1 0x00007f79eeedb413 in IA__g_log (log_domain=
at /build/
#2 0x000000000040ed38 in create_gl_area ()
#3 0x0000000000409349 in c_main ()
#4 0x00007f79eec2c84f in scm_boot_guile () from /usr/lib/
#5 0x0000000000409290 in main ()
(gdb)