Bug when loading v2.0 experimental

R

Roescoe

Refugee
Version
experimental 2.0
Platform
Linux
It appears the game is unable to load libMouseLib.so and libdiscord_partner_sdk.so despite the dlls existing in ~/.local/share/Steam/steamapps/common/7 Days To Die/7DaysToDie_Data/Plugins it then infinitely loops the errors in the console in the attacked pastebin
 
Reproduction Steps
1. Set Beta Participation to latest_experimental - Unstable build
2. Download and launch game
3. Upon the game starting to load the main menu and throughout any other steps take the console fills with the attached errors making interaction impossible.
Link to Logs
https://pastebin.com/YA959jcq
Link to Screenshot/Video
https://imgur.com/a/jbT7YGB
Update: The game works fine on Proton, (the windows version) I can transfer saves and everything. So this bug appears to either be an issue with my specific configuration of Ubuntu 20.04.6, or some missing links in the unity/game Linux libraries.
 
Ah yup. And I've heard it's not possible to update beyond GLIBC_2.31 in 20.04
./libdiscord_partner_sdk.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by ./libdiscord_partner_sdk.so)
./libdiscord_partner_sdk.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./libdiscord_partner_sdk.so)
./libdiscord_partner_sdk.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./libdiscord_partner_sdk.so)
./libdiscord_partner_sdk.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./libdiscord_partner_sdk.so)
linux-vdso.so.1 (0x00007ffe41485000)
libatomic.so.1 => /lib/x86_64-linux-gnu/libatomic.so.1 (0x00007f6c4b586000)
libasound.so.2 => /lib/x86_64-linux-gnu/libasound.so.2 (0x00007f6c4b48b000)
libpulse.so.0 => /lib/x86_64-linux-gnu/libpulse.so.0 (0x00007f6c4b436000)
libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x00007f6c4b2f7000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6c4b1a8000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f6c4b18d000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6c4af99000)
/lib64/ld-linux-x86-64.so.2 (0x00007f6c4bef5000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f6c4af76000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6c4af70000)
libpulsecommon-13.99.so => /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so (0x00007f6c4aeee000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f6c4ae9d000)
libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f6c4ae71000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007f6c4adc2000)
libwrap.so.0 => /lib/x86_64-linux-gnu/libwrap.so.0 (0x00007f6c4adb6000)
libsndfile.so.1 => /lib/x86_64-linux-gnu/libsndfile.so.1 (0x00007f6c4ad37000)
libasyncns.so.0 => /lib/x86_64-linux-gnu/libasyncns.so.0 (0x00007f6c4ab31000)
libapparmor.so.1 => /lib/x86_64-linux-gnu/libapparmor.so.1 (0x00007f6c4ab1c000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f6c4ab10000)
libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x00007f6c4ab0a000)
libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f6c4ab02000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f6c4aad9000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f6c4aab8000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f6c4a99a000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x00007f6c4a97b000)
libFLAC.so.8 => /lib/x86_64-linux-gnu/libFLAC.so.8 (0x00007f6c4a93d000)
libogg.so.0 => /lib/x86_64-linux-gnu/libogg.so.0 (0x00007f6c4a930000)
libvorbis.so.0 => /lib/x86_64-linux-gnu/libvorbis.so.0 (0x00007f6c4a902000)
libvorbisenc.so.2 => /lib/x86_64-linux-gnu/libvorbisenc.so.2 (0x00007f6c4a857000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f6c4a83b000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007f6c4a81f000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f6c4a7fc000)
So It might just no longer be possible to play in older versions, unless I do a special linking process for the more recent GLIBC.

That is, this looks scary: https://askubuntu.com/questions/1345342/how-to-install-glibc-2-32-when-i-already-have-glibc2-31
 
Because some older applications I have would still need older libraries which no longer exist on more recent version. That is I don't want to risk my current setup and upgrade. Also upgrades are a total pain. Also clearly since this is pretty much the only thing that needs that more recent Glibc library I won't change my whole system for it. I'll just play the older version. Also I might start creating docker stuff for some of my apps. Either way this is definitely something TFP should fix since the steam page claims the game runs on 18.04+
 
Oh sorry they say 16.04 is minimum, so either that severely needs an update or they can simply add a way for those few new libraries to interact nicely (or be disabled in older versions where the exception occurs) It's bad error handling to throw uncaught non-fatal exceptions into a console which is unhidable
 

Attachments

  • TFP7DaysMinRequirements.png
    TFP7DaysMinRequirements.png
    69.3 KB · Views: 2
Roescoe said:
Oh sorry they say 16.04 is minimum, so either that severely needs an update or they can simply add a way for those few new libraries to interact nicely (or be disabled in older versions where the exception occurs) It's bad error handling to throw uncaught non-fatal exceptions into a console which is unhidable
Click to expand...
Yeah I wouldn't trust that at all. It does not have accurate information. There have been multiple suggestion threads to update the specs with real information. I know for a fact it won't work in 16.04, and I am pretty certain it wouldn't work in 18.04 for v1.0.
 
Not a bug. That is a very old OS and we'll likely update the min version number at some point. You can disable Discord Integration to get around the error I was told
 
Unfortunately disabling the integration does not stop it from trying to resolve the library once it starts generating a map. To note I've never provided discord details to the game.
Post automatically merged:

Also calling Ubuntu 20.04 "Very old" sounds a bit silly considering Windows 11 came out October 5, 2021. Though I totally respect the decision not to support it.
 
Roescoe said:
Unfortunately disabling the integration does not stop it from trying to resolve the library once it starts generating a map. To note I've never provided discord details to the game.
Post automatically merged:

Also calling Ubuntu 20.04 "Very old" sounds a bit silly considering Windows 11 came out October 5, 2021. Though I totally respect the decision not to support it.
Click to expand...

Might need to use the launcher tool to wipe settings, then choose Not Now for discord integration, and get to the options to turn it off. Maybe, just a thought lol. There's a discord file in the save directory you can try deleting too
 
Roescoe said:
Unfortunately disabling the integration does not stop it from trying to resolve the library once it starts generating a map. To note I've never provided discord details to the game.
Post automatically merged:

Also calling Ubuntu 20.04 "Very old" sounds a bit silly considering Windows 11 came out October 5, 2021. Though I totally respect the decision not to support it.
Click to expand...
Well don't forget windows works differently. It stays current and up to date all the time until the end of life, such as with windows 8 for example. Windows 8 is old and not updated to... modernize it for a lack of a better word. Ubuntu is up to 24.x LTS, so yeah, Ubuntu 20 is four OS versions behind at this point.
 
Jugginator said:
Might need to use the launcher tool to wipe settings, then choose Not Now for discord integration, and get to the options to turn it off. Maybe, just a thought lol. There's a discord file in the save directory you can try deleting too
Click to expand...
Yeah that removes the error from the main menu, and the map creation/selection screen, but it immediately returns upon trying to load or generate a map. Oddly enough there's no downside I've found to just using proton for the game. So I might as well do that.
 
Steps I took
1. Clean data
2. Run game
3. Accept EULA
4. Say Not Now to Discord integration
5. Quit and run game again
6. Discord SDK errors appear again upon starting game. for second time

Vs proton just works. Anyhow I probably shouldn't waste any more of your time since I'm running on an unsupported OS.
 
Roescoe said:
Steps I took
1. Clean data
2. Run game
3. Accept EULA
4. Say Not Now to Discord integration
5. Quit and run game again
6. Discord SDK errors appear again upon starting game. for second time

Vs proton just works. Anyhow I probably shouldn't waste any more of your time since I'm running on an unsupported OS.
Click to expand...
After step 4, go into the options and make sure Integration is turned off. That is for linking your account, it'll assign an anonymous account if you dont
 
That was the ticket! Thank you very much. Sort of... but the errors return upon loading/creating a new game while playing said game. Now the errors are permanently gone from the main menu.

Alternate steps after 4
5. Open Options-> Audio
6. Go to Discord tab and notice "Enable discord integration" is turned on, even though you selected "Not Now" disable it
7. Quit game and run again
8. No more discord sdk errors until you load/create any game.
 
Last edited:
You must log in or register to reply here.
Back
Top