XMessage with weird fonts and several options on start, only one lets the game start

[cantfind]

Each time I start the game, it shows an undecipherable and long message in an xmessage box, with several buttons to click on:

If I click on any button other than the second one from the left, the game is stuck (and 2 main processes run with max cpu) - I can't even close it by clicking on the x at the top right of the window - I have to sent TERM signal to the main processes to close it.

If I click the second button on the message, I get to the main window of the game, and everything works just fine (except the game thinks it's in fullscreen, even though it's windowed - but I can transform it to full screen by right clicking the title bar and selecting fullscreen mode).

Running from the terminal I get this output:

TIMER| InitVfs: 249.217 us
Writing the mainlog at /home/or/.config/0ad/logs/mainlog.html
TIMER| CONFIG_Init: 11.4385 ms
Sound: AlcInit success, using OpenAL Soft
Assertion failed: "ret == 0"
Location: lcpu.cpp:174 (os_cpu_SetThreadAffinityMask)

Call stack:

(0x5628ca0cbe7c) /usr/bin/pyrogenesis(+0x503e7c) [0x5628ca0cbe7c]
(0x5628ca0a63bb) /usr/bin/pyrogenesis(+0x4de3bb) [0x5628ca0a63bb]
(0x5628ca0a5eaf) /usr/bin/pyrogenesis(+0x4ddeaf) [0x5628ca0a5eaf]
(0x5628ca0a66f3) /usr/bin/pyrogenesis(+0x4de6f3) [0x5628ca0a66f3]
(0x5628ca0cb9e9) /usr/bin/pyrogenesis(+0x5039e9) [0x5628ca0cb9e9]
(0x5628ca0cbd8b) /usr/bin/pyrogenesis(+0x503d8b) [0x5628ca0cbd8b]
(0x5628ca0f5b0c) /usr/bin/pyrogenesis(+0x52db0c) [0x5628ca0f5b0c]
(0x5628ca0f584c) /usr/bin/pyrogenesis(+0x52d84c) [0x5628ca0f584c]
(0x5628ca0f5a9d) /usr/bin/pyrogenesis(+0x52da9d) [0x5628ca0f5a9d]
(0x5628ca0c5e9e) /usr/bin/pyrogenesis(+0x4fde9e) [0x5628ca0c5e9e]
(0x5628ca0f584c) /usr/bin/pyrogenesis(+0x52d84c) [0x5628ca0f584c]
(0x5628ca0c5c0d) /usr/bin/pyrogenesis(+0x4fdc0d) [0x5628ca0c5c0d]
(0x5628c9e0686c) /usr/bin/pyrogenesis(+0x23e86c) [0x5628c9e0686c]
(0x5628c9df70e7) /usr/bin/pyrogenesis(+0x22f0e7) [0x5628c9df70e7]
(0x5628c9c14a37) /usr/bin/pyrogenesis(+0x4ca37) [0x5628c9c14a37]
(0x5628c9c1313b) /usr/bin/pyrogenesis(+0x4b13b) [0x5628c9c1313b]

errno = 22 (Invalid alignment)
OS error = ?


lcpu.cpp(174): Assertion failed: "ret == 0"
APIC: not unique
UserReport written to /home/or/.config/0ad/logs/userreport_hwdetect.txt

The contents of userreport_hwdetect.txt can be found in https://pastebin.com/mqbRjBXy

The contents of mainlog.html can be found in https://pastebin.com/Hg5Dtpsv

The contents of crashlog.txt can be found in https://pastebin.com/szgwhqtQ

My system runs Manjaro 5.15.60-1, KDE Plasma 5.24.6, KDE Framework 5.96.0, Qt version 5.15.5, graphics platform is X11, python version 3.10.5.

[Stan`]

Hey this seem to be triggered in the more recent versions of linux/kernel. You can try to compile the latest version until it comes out where it's fixed.

[vladislavbelov]

22 minutes ago, cantfind said:

Each time I start the game, it shows an undecipherable and long message in an xmessage box, with several buttons to click on:

Do you know which locale does your OS use?

[Norse_Harold]

8 minutes ago, Stan` said:

You can try to compile the latest version until it comes out where it's fixed.

Binaries for Linux of these versions of 0ad are available, so compiling from source might not be necessary in this case.

0.0.26 rc3 (rev 27067) as Snap (change version to latest/beta)

rev 27077 as AppImage

rev 27087 as Snap (change version to latest/edge)

[cantfind]

1 hour ago, vladislavbelov said:

Do you know which locale does your OS use?

Quote

 

LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=en_US.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=

 

[cantfind]

1 hour ago, Norse_Harold said:

Binaries for Linux of these versions of 0ad are available

So this bug was solved after rev 27067?

I'm using a build from 7 of July (25860).

[vladislavbelov]

 

20 minutes ago, cantfind said:

LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=en_US.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=

It looks ok. That's strange why the text is encrypted. Seems like XMessage reinterprets it as Unicode or vice versa.

18 minutes ago, cantfind said:

So this bug was solved after rev 27067?

I'm using a build from 7 of July (25860).

Yes, it's solved in r27067 and in the upcoming release as well.