GZDoom crashes after upgrade to Ubuntu 17.04

[Stormwalker]

Hi, I have been using Ubuntu Linux for about 2 years now. GZDoom has worked well for me since version 14.04. I believe that the last Ubuntu version that I ran GZDoom on was 16.04(Xenial Xerus). I recently upgraded to version 17.04(Zesty Zapus) and now whenever I try to run GZDoom, I get this error...

GZDoom g2.4.0 - 2017-03-19 21:36:18 +0100 - SDL version
Compiled on Mar 21 2017

M_LoadDefaults: Load system defaults.
Aborted (core dumped)

The only change that I've made to my system was the Ubuntu version upgrade, so I am assuming that this is to blame for GZDoom not working. I have tried uninstalling and then reinstalling GZDoom, but the problem persists. If anyone has any ideas on why this is happening or how to fix it, I would be grateful. Thanks!

[_mental_]

It's impossible to say anything without crash report.
Some unknown failure happened on early stage of initialization.

If really want to investigate it, you need to run GZDoom under debugger to get a callstack.
Execute the following command in Terminal:

Code: Select all

gdb /opt/gzdoom/gzdoom

If it says that gdb program is not installed, install it using this command and run the first command again:

Code: Select all

sudo apt-get install gdb

In (gdb) prompt execute run command. When it stops execute bt command and post whole output here.

[Rachael]

Also make sure you compile with "cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo", otherwise the debug info it gives will be nothing more than an incoherent string of numbers.

[_mental_]

It's about build installed from .deb package. That's why path to GZDoom is /opt/gzdoom/gzdoom.

[Rachael]

Ah - my apologies.

[Stormwalker]

When it stops execute bt command and post whole output here.

Ok, here's the output I got. Thanks for the instructions by the way!

---

(gdb) run
Starting program: /opt/gzdoom/gzdoom
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
GZDoom g2.4.0 - 2017-03-19 21:36:18 +0100 - SDL version
Compiled on Mar 21 2017

M_LoadDefaults: Load system defaults.

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
58 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x00007ffff641477f in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:58
#1 0x00007ffff641637a in __GI_abort () at abort.c:89
#2 0x00007ffff52dc0b8 in () at /lib/x86_64-linux-gnu/libgcc_s.so.1
#3 0x00007ffff52e0599 in __gcc_personality_v0 ()
at /lib/x86_64-linux-gnu/libgcc_s.so.1
#4 0x0000000000ce52f3 in ()
#5 0x0000000000ce597a in ()
#6 0x0000000000c6015b in __cxa_throw ()
#7 0x00007ffff00367a6 in () at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
#8 0x00007ffff00398ff in () at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
#9 0x00007fffefff7a70 in () at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
#10 0x00007ffff0001b09 in mir::client::DefaultConnectionConfiguration::the_rpc_channel() () at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
#11 0x00007fffefff21a9 in mir_connect ()
at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
#12 0x00007fffefff34db in mir_connect_sync ()
at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
#13 0x00007ffff3f0eff7 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#14 0x00007ffff3ea4235 in gdk_display_manager_open_display ()
at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#15 0x00007ffff43a3e1a in gtk_init_check ()
at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
---Type <return> to continue, or q <return> to quit---
#16 0x000000000059ac31 in I_GtkAvailable() ()
#17 0x00000000005951b0 in I_PickIWad(WadStuff*, int, bool, int) ()
#18 0x00000000007d2de5 in FIWadManager::IdentifyVersion(TArray<FString, FString>&, char const*, char const*) ()
#19 0x00000000007d31ce in FIWadManager::FindIWAD(TArray<FString, FString>&, char const*, char const*) ()
#20 0x00000000007d6ddc in D_DoomMain() ()
#21 0x000000000057bf72 in main ()
(gdb)

Hope this helps!

[_mental_]

Could you please try to run GZDoom with -iwad command line option? For example

Code: Select all

gzdoom -iwad doom2

The problem is caused by IWAD selection window and I'm curious is this the only issue or not.

[Stormwalker]

Could you please try to run GZDoom with -iwad command line option?

GZDoom successfully runs when I specify iwad, no matter which iwad. Before it would pop up an iwad selection screen up if I didn't specify iwad, but now it just bombs out with that "Aborted, core dump" error. I keep all my iwads in /usr/local/share/games/doom/, and have for years.

[_mental_]

The problem is not related to upgrade of Ubuntu and reproduces on the clean install.
However in GZDoom 2.4.0 built on 17.04 from sources IWAD selector works fine.
Unfortunately I have no idea why it doesn't in the released version.

[dontpokethebear3893]

I'd like to bump this saying I experience the same issues. It kind of sucks but gzdoom1 (1.9.1) still works fine

[Graf Zahl]

This looks a bit odd. The last line of GZDoom that appears in the stack trace is this:

Code: Select all

		GtkAvailable = Gtk::gtk_init_check (&argc, &argv);

The file containing this line was added in November 2016 which may explain why 1.9.1 still works. The check was in a different place there.

Relevant commit log:

Code: Select all

- Added support for GTK3 (thanks to "MineyMe" and edward-san)
- Replaced GTK/OS X (note different from Cocoa) clipboard code with SDL clipboard API.
- Removed requirement to link to GTK in order to compile with GTK support.
	- GTK is no longer init'd if the GTK IWAD picker is not used.
	- Our usage of GTK is such that the dynamic loader can work with both GTK2 and GTK3 depending on what's installed.
	- Since we're accumulating a lot of library loaders I've built a generic interface as FModule which replaces TOptWin32Proc and the loaders in the OpenAL and Fluidsynth code.