[linux] Problems starting in fedora 28
The game simply does not start.
using gdb to debug.
[yonatan@localhost ~]$ gdb hedgewars
GNU gdb (GDB) Fedora 8.1-15.fc28
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from hedgewars...Reading symbols from /home/yonatan/hedgewars...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: dnf debuginfo-install hedgewars-0.9.24.1-1.fc28.i686
(gdb) run
Starting program: /usr/bin/hedgewars
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
warning: Error reading shared library list entry at 0x700
warning: Error reading shared library list entry at 0xa10
warning: Error reading shared library list entry at 0xd40
warning: Error reading shared library list entry at 0x1060
warning: Error reading shared library list entry at 0x1380
warning: Error reading shared library list entry at 0x16c0
warning: Error reading shared library list entry at 0x2800
warning: Error reading shared library list entry at 0x2a90
warning: Error reading shared library list entry at 0x2d10
warning: Error reading shared library list entry at 0x2f90
warning: Error reading shared library list entry at 0x3210
warning: Error reading shared library list entry at 0x9b0
dbus[4607]: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file ../../dbus/dbus-message.c line 1362.
This is normally a bug in some application using the D-Bus library.D-Bus not built with -rdynamic so unable to print a backtrace
Program received signal SIGABRT, Aborted.
0xb7fd5d21 in __kernel_vsyscall ()
(gdb) where
#0 0xb7fd5d21 in __kernel_vsyscall ()
#1 0xb664cf02 in raise () from /lib/libc.so.6
#2 0xb663684f in abort () from /lib/libc.so.6
#3 0xb36e916a in ?? () from /lib/libdbus-1.so.3
#4 0xb370d7cf in _dbus_warn_check_failed () from /lib/libdbus-1.so.3
#5 0xb370dfcf in _dbus_warn_return_if_fail () from /lib/libdbus-1.so.3
#6 0xb36fc40f in dbus_message_new_method_call () from /lib/libdbus-1.so.3
#7 0xb7057bc4 in SDL_DBus_CallVoidMethodInternal () from /lib/libSDL2-2.0.so.0
#8 0xb7058438 in SDL_DBus_CallVoidMethodOnConnection ()
from /lib/libSDL2-2.0.so.0
#9 0xb70595e5 in IBus_SimpleMessage () from /lib/libSDL2-2.0.so.0
#10 0xb705918b in IBus_SetupConnection () from /lib/libSDL2-2.0.so.0
#11 0xb7059304 in SDL_IBus_Init () from /lib/libSDL2-2.0.so.0
#12 0xb70587b2 in SDL_IME_Init () from /lib/libSDL2-2.0.so.0
#13 0xb7045958 in X11_InitKeyboard () from /lib/libSDL2-2.0.so.0
#14 0xb704caab in X11_VideoInit () from /lib/libSDL2-2.0.so.0
#15 0xb70312a6 in SDL_VideoInit_REAL () from /lib/libSDL2-2.0.so.0
#16 0xb6f9cdb2 in SDL_InitSubSystem_REAL () from /lib/libSDL2-2.0.so.0
#17 0x005114e0 in SDLInteraction::SDLInteraction() ()
#18 0x00511622 in SDLInteraction::instance() ()
#19 0x0045042c in main ()
(gdb)
The main change in 0.9.24 was shifting (forced due to distro deprecation) to Qt5 - have you filed a bug with your distro? We could then link to it in a tracking issue on https://issues.hedgewars.org
At present, no idea what the problem could possibly be - apart from it being some NULL assertion in dbus (do you have dbus enabled?)
We don't explicitly use dbus though - so any problems would be in the underlying Qt or SDL libraries.
--
Oh, what the heck. 1PLXzL1CBUD1kdEWqMrwNUfGrGiirV1WpH <= tip a hedgewars dev
Oh, also, I assumed this was related to the hedgewars release - but you didn't explicitly say that. Only mentioned Fedora upgrade.
Do older versions of hedgewars work? 0.9.23 ? 0.9.22?
--
Oh, what the heck. 1PLXzL1CBUD1kdEWqMrwNUfGrGiirV1WpH <= tip a hedgewars dev
I am using two desktops, gnome and Mate, curiously it is in gnome where I have problems, is it not compatible with wayland?
by the way, I could not play in mate for this problem: https://issues.hedgewars.org/show_bug.cgi?id=570
WRT Issue #570 - it does not prevent *play* since the crash is on exit. So you could ignore it - it's just annoying.
And it isn't mate specific either - it's entirely a bug in the compiler version that fedora is using - they could repackage using another version of the compiler or you could make your own build.
WRT wayland - we don't do any window managing specifically ourselves, so any wayland bugs are in SDL or Qt, my personal antipathy to wayland notwithstanding
The issue could perhaps be graphics card + compositing related? Sometimes bad drivers/cards can be problematic with both composited WM and app GL demands - firefox for example had problems with layers acceleration on my sucky old ATI card with compositing, esp w/ the closed source driver.
--
Oh, what the heck. 1PLXzL1CBUD1kdEWqMrwNUfGrGiirV1WpH <= tip a hedgewars dev