Gzdoom error when trying to launch it on Linux

[Vhagg]

Im trying to launch GZDoom on Ubuntu 24.04 LTS but I get this error:

/opt/gzdoom/gzdoom: symbol lookup error: /opt/gzdoom/libzmusic.so.1: undefined symbol: FLAC__StreamEncoderInitStatusString

Weird thing is that GZDoom was working fine a few days ago. Im not sure what I changed or maybe deleted but no matter how many times I install and reinstall it using the deb file its still the same...
Btw Im a total noob for Linux, I installed it just recently, so I dont know a lot about it.
If you need more information let me know (and also please tell me how to find it).

[Blzut3]

That's a bit weird, I'll check to see if I somehow screwed up the zmusic build this weekend. But I'm not seeing FLAC on the direct dependency list so not immediately obvious what went wrong there.

It's not entirely clear to me how you ran into this issue either since even a clean container seems to be fine (and my Ubuntu 24.04 systems are fine). Can you grab the output of the following in the mean time?

Code: Select all

ldd /opt/gzdoom/gzdoom

Edit: I guess I should also ask are you talking about GZDoom 4.12.2?

[Vhagg]

That's a bit weird, I'll check to see if I somehow screwed up the zmusic build this weekend. But I'm not seeing FLAC on the direct dependency list so not immediately obvious what went wrong there.

It's not entirely clear to me how you ran into this issue either since even a clean container seems to be fine (and my Ubuntu 24.04 systems are fine). Can you grab the output of the following in the mean time?

Code: Select all

ldd /opt/gzdoom/gzdoom

Edit: I guess I should also ask are you talking about GZDoom 4.12.2?

I get the 4.11.3 version when I click on the Ubuntu x64 url. Output of the command is:


linux-vdso.so.1 (0x00007ffdb52a9000)
libSDL2-2.0.so.0 => /usr/local/lib/libSDL2-2.0.so.0 (0x000071c90fe00000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x000071c911f6e000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x000071c911f5a000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x000071c911f55000)
libzmusic.so.1 => /opt/gzdoom/libzmusic.so.1 (0x000071c90f400000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x000071c911f4e000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x000071c90f000000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x000071c911e65000)
libgomp.so.1 => /lib/x86_64-linux-gnu/libgomp.so.1 (0x000071c911e0e000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x000071c911de1000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x000071c90ec00000)
libvorbisenc.so.2 => /lib/x86_64-linux-gnu/libvorbisenc.so.2 (0x000071c911d34000)
libopus.so.0 => /lib/x86_64-linux-gnu/libopus.so.0 (0x000071c911cd5000)
libmpg123.so.0 => /lib/x86_64-linux-gnu/libmpg123.so.0 (0x000071c911c79000)
libmp3lame.so.0 => /lib/x86_64-linux-gnu/libmp3lame.so.0 (0x000071c911c03000)
libasound.so.2 => /lib/x86_64-linux-gnu/libasound.so.2 (0x000071c9100f6000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x000071c911be5000)
libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x000071c90fcb7000)
/lib64/ld-linux-x86-64.so.2 (0x000071c911f90000)
libvorbis.so.0 => /lib/x86_64-linux-gnu/libvorbis.so.0 (0x000071c9100c8000)
libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x000071c90fc1d000)
libogg.so.0 => /lib/x86_64-linux-gnu/libogg.so.0 (0x000071c9100be000)

[Blzut3]

You can find GZDoom 4.12.2 in the release thread: viewtopic.php?t=79053 The website has yet to be updated it seems.

Alternatively you can install the apt repo which is maintained by me: https://debian.drdteam.org/

I do see that you have a build of libSDL2-2.0.so.0 in /usr/local/lib. Presumably this is a custom build and may cause compatibility problems with some software. Particularly if that's older than the version Ubuntu 24.04 normally would ship with.

[Vhagg]

You can find GZDoom 4.12.2 in the release thread: viewtopic.php?t=79053 The website has yet to be updated it seems.

Alternatively you can install the apt repo which is maintained by me: https://debian.drdteam.org/

I do see that you have a build of libSDL2-2.0.so.0 in /usr/local/lib. Presumably this is a custom build and may cause compatibility problems with some software. Particularly if that's older than the version Ubuntu 24.04 normally would ship with.

What's the right way of deleting that SDL2 build? Do I just rm the file from /usr/local/lib or do I use a packet manager?

Update: I think that file comes with the package libsdl2-2.0-0 that's installed with gzdoom. When I remove that package, gzdoom gets removed too

libzmusic.so.1 => /opt/gzdoom/libzmusic.so.1 (0x00007c7571e00000) - Is this path correct?

[Blzut3]

The libsdl2-2.0-0 package should be providing /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0. At least that's what the version Canonical provides has. Typically /usr/local would be stuff that you compiled yourself, but that's not an enforced rule so hard to say unless you remember what you did.

If you don't remember compiling SDL2 yourself I would query the package manager to see if it knows about it.

Code: Select all

dpkg-query -S /usr/local/lib/libSDL2-2.0.so.0

If it says "no path found matching pattern" then that means your build is not managed by the package manager. Which means that there's no uninstaller you can just run to clean it up. For the most part all you would need to do is delete the libSDL2 files in /usr/local/lib as that's really the only thing that would make a difference. You would need to poke around /usr/local/ for any other SDL2 files if you want to clean everything up.

If dpkg-query gives you a package name, hopefully it's not libsdl2-2.0-0. If it is, then we'll have to figure out why you're not using the Canonical provided package and go from there.

libzmusic.so.1 => /opt/gzdoom/libzmusic.so.1 (0x00007c7571e00000) - Is this path correct?

It is. GZDoom has a private libzmusic library.

[Vhagg]

The libsdl2-2.0-0 package should be providing /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0. At least that's what the version Canonical provides has. Typically /usr/local would be stuff that you compiled yourself, but that's not an enforced rule so hard to say unless you remember what you did.

If you don't remember compiling SDL2 yourself I would query the package manager to see if it knows about it.

Code: Select all

dpkg-query -S /usr/local/lib/libSDL2-2.0.so.0

If it says "no path found matching pattern" then that means your build is not managed by the package manager. Which means that there's no uninstaller you can just run to clean it up. For the most part all you would need to do is delete the libSDL2 files in /usr/local/lib as that's really the only thing that would make a difference. You would need to poke around /usr/local/ for any other SDL2 files if you want to clean everything up.

If dpkg-query gives you a package name, hopefully it's not libsdl2-2.0-0. If it is, then we'll have to figure out why you're not using the Canonical provided package and go from there.

libzmusic.so.1 => /opt/gzdoom/libzmusic.so.1 (0x00007c7571e00000) - Is this path correct?

It is. GZDoom has a private libzmusic library.

Brother you're a life saver, thank you a lot. I removed every file and directory in /usr/local/lib that had SDL2 in its name and GZDoom runs now

[Blzut3]

Although it should only cause an issue on off label usage of the deb package, I can confirm that my linker work for libzmusic was not done properly and it only works when certain libraries get pulled in incidentally by other libraries. Need to figure out the exact adjustments I need to make.