Open KorinFlakes opened 5 years ago
steam-440900.log attached my proton-log with proton-experimental. the:
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
error isn't present with proton experimental, but still fails to launch BUT, the game will launch still, if you disable steam online services by editing the /steamapps/common/Conan Exiles/ConanSandbox/Config/Windows/WindowsSteamEngine.ini and changing true to false on the OnlineSubsystemSteam bEnabled line.
so either way, its steam online services preventing the game from working.
steam-440900.log attached my proton-log with proton-experimental. the:
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
error isn't present with proton experimental, but still fails to launch BUT, the game will launch still, if you disable steam online services by editing the /steamapps/common/Conan Exiles/ConanSandbox/Config/Windows/WindowsSteamEngine.ini and changing true to false on the OnlineSubsystemSteam bEnabled line.
so either way, its steam online services preventing the game from working.
can confirm this too.
I just post same here for both my PC and SteamDeck - was hoping you super smart people would have a work around.
bit out of range 0 - FD_SETSIZE on fd_set : terminated
Maybe the problem is here?
Interesting to note a massive uptick of reports about this specific issue at ProtonDB: https://www.protondb.com/app/440900
So it's not just those of us who know about github. :)
Interesting to note a massive uptick of reports about this specific issue at ProtonDB: https://www.protondb.com/app/440900
So it's not just those of us who know about github. :)
question is, is it enough to get valves attention to get this fixed? sucks conan isn't an officially supported game by valve. has me really worried its a low priority because of it. really sucks.
Having the same issue as everyone else (working fine prior to last update), except I get this
*** buffer overflow detected ***: terminated
Instead of
*** bit out of range 0 - FD_SETSIZE on fd_set ***: terminated
I tried with the Proton versions provided by Steam as well as the Custom GE versions.
Did that config file edit and was able to reach main menu as well, but unable to do anything else due to an expected error about not connecting to steam.
Ran the game with strace attached. Not sure if this helps but all the DLL files are untouched, fresh game install as well to verify. I get these lines as output.
0128:warn:steamclient:get_mem_from_steamclient_dll Module not found, err 126. 0128:warn:debugstr:OutputDebugStringA "[S_API FAIL] SteamAPI_Init() failed; no appID found.\nEither launch the game from Steam, or put the file steam_appid.txt containing the correct appID in your game folder.\n" 0128:warn:seh:dispatch_exception "[S_API FAIL] SteamAPI_Init() failed; no appID found.\nEither launch the game from Steam, or put the file steam_appid.txt containing the correct appID in your game folder.\n" 0128:warn:debugstr:OutputDebugStringA "[S_API FAIL] Tried to access Steam interface SteamUtils010 before SteamAPI_Init succeeded.\n" 0128:warn:seh:dispatch_exception "[S_API FAIL] Tried to access Steam interface SteamUtils010 before SteamAPI_Init succeeded.\n" 0128:warn:seh:OutputDebugStringW L"LogOnline:Warning: STEAM: Steamworks: SteamUtils() failed!\r\n"
This is what causes the bit out of range error, and the buffer overflow error.
That strace is interesting.. Where is Steam trying to look? It complains about no appID being found, did you check to see if such a file existed in the Conan directory? I see it in mine.
I tried doing launch option:
LD_PRELOAD=path/to/.steam/steam/ubuntu12_32/steamservice.so %command%
The log shows this:
ERROR: ld.so: object 'path/to/.steam/steam/ubuntu12_32/steamservice.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
[17:18:01.413 | browser | info] Application will quit.
CAppInfoCacheReadFromDiskThread took 4 milliseconds to initialize
*** buffer overflow detected ***: terminated
Then it hangs indefinitely unless I force it to stop. Was there ever a 64 bit version of steamservice.so? I don't see any in the /ubuntu12_64/ folder.
Update: It seems like that ELF class error happens even when steam is working "normally", so it might not be the culprit.
This sucks. I can confirm config change allows game to open main menu but nothing more as even single player requires online services...
It's a workaround. But i'm able to play conan exiles throught the steam client that i've installed on lutris.
It's a workaround. But i'm able to play conan exiles throught the steam client that i've installed on lutris.
Be interesting to know the version of the Steam Client you have vs the rest. My current. Steam Beta Branch: Stable Client Steam Version: 1705108172 Steam Client Build Date: Fri, Jan 12 17:52 UTC -07:00 Steam Web Build Date: Fri, Jan 12 10:02 UTC -07:00 Steam API Version: SteamClient021
It's a workaround. But i'm able to play conan exiles throught the steam client that i've installed on lutris.
i take it you installed the windows version of steam via lutris?
yes i've installed the windows version of steam via lutris.
client version is the same
After an update for left 4 dead (thanks for that) I am forced to update via steamcmd.sh and see this issue.
No Proton version works at the moment. The issue is reported on the Official Funcom website and across various social media outlets. Clicking "Play" will trigger the Funcom launcher but the game will not launch from there. This all started after two Steam Workshop updates on January 11th and January 12th.
These are the two Steam updates: https://store.steampowered.com/news/app/593110/view/3901870710035098052 https://store.steampowered.com/news/app/593110/view/6623172784186899212
Official Funcom: https://forums.funcom.com/t/since-jan-13-game-wont-launch-on-linux/248673
ProtonDB: https://www.protondb.com/app/440900
I got a stack trace of the crash, it's in the thread IPC:CSteamEngine
, so definitely looks like a steam bug. The bit out of range is 0x49c, larger than the fd_set size of 0x400.
The game makes a large number of threads, and each thread opens a pipe for communicating with wineserver, which pushes the fd count past the size of fd_set.
For anyone with the debug symbols to the (64-bit) steamclient.so
with sha256 ad9f4250539276932f1c1010bbcc44a9f1aa98e88ad573ca555a9b969c6f11ba
, here's a partial stack trace (addresses match what you get in Ghidra):
__fdelt_warn (crash) libc.so.6
0x01cdf826
0x01cdc160
0x01cde82c
0x01f78b11
0x00cc9f55
0x00c38b2b
0x0123e304
0x013b5ed9
0x013b6638
0x01eda37a
0x01ed8571
0x01ed8c6b
Replying to https://github.com/ValveSoftware/Proton/issues/2563#issuecomment-1906462064
if this is indeed a steam bug, could you make a thread about what you found at https://github.com/ValveSoftware/steam-for-linux ? to help get their attention for it.
also can anyone else confirm that conan exiles is working via windows steam installed via lutris to go with the one report of it working that way?
Replying to #2563 (comment)
if this is indeed a steam bug, could you make a thread about what you found at https://github.com/ValveSoftware/steam-for-linux ? to help get their attention for it.
Looks like somebody did. The issue was closed, and the poster was referred to the Proton repo as is their policy for unsupported titles. because they see it as an issue with Proton compatibility. I disagree, but that means little.
Its also possible that this issue is related but I'm not certain on that.
also can anyone else confirm that conan exiles is working via windows steam installed via lutris to go with the one report of it working that way?
I'm currently playing the game with Lutris + Windows Steam client install. Smooth gameplay
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
Thanks, the beta client update works for me. :+1:
Hello all, There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
Thanks, the beta client update works for me. 👍
Thanks so much beta client update works!
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
Confirmed working! Thank you!
Steam Beta Branch: Steam Beta Update Steam Version: 1706306386 Steam Client Build Date: Fri, Jan 26 9:28 PM UTC -08:00 Steam Web Build Date: Fri, Jan 26 8:26 PM UTC -08:00 Steam API Version: SteamClient021
Proton 8.0-5 - Build ID: 13223186 Debian 6.1.69-1 (2023-12-30)
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
@TTimo Can confirm that the game now works with the Steam beta on Ubuntu 22.04, using GE-Proton8-25. Everything seems to be back to normal. Thank you!
Any ETA on when this fix will make it to stable Steam?
Steam Beta Branch: Steam Beta Update Steam Version: 1706306386 Steam Client Build Date: Fri, Jan 26 9:28 PM UTC -08:00 Steam Web Build Date: Fri, Jan 26 8:26 PM UTC -08:00 Steam API Version: SteamClient021
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
i confirm too, it's working on steam beta.
Hello all,
There are several problems with this title. The FD_SETSIZE issue was definitely caused by the last Steam client stable update. We have shipped a beta client update that addresses this. Please retest!
Thank you very much, looks like it works fine now in Steam Beta indeed! ^_^
thank you valve. the new steam client beta update for linux indeed fixed it for me.
Compatibility Report
System Information
I confirm:
Symptoms
You can't launch the game with Battleye or play any Battleye protected servers but the game does allow you to play without it in both singleplayer/co-op and online on non-protected servers.
The game runs at a solid 60fps for me on almost all high graphics with the exception of frame drops. I'd assumed it was a shader cache issue (or whatever you call it) but it never stops. Every time you look in a new direction, the framerate will drop suddenly and shoot back up to 60. Every time you gather a resource node, every time you build an object etc, the same thing. Normally a drop that small wouldn't matter much but it actually causes an immense and jarring stuttering throughout the entirety of the game.