Can anybody confirm that this also affects the actual steam client / proton? It looks like it does, looking at #10215

This seems to affect different games, too.

See https://github.com/ValveSoftware/Proton/issues/2563#issuecomment-1892798313

https://github.com/ValveSoftware/steam-for-linux/issues/10392 Shouldn't have been closed. The issue here is that someone seems to have forgotten to package steamservice.so with the last steam update.

Is this issue being looked into, seems like it's occurring on most linux distros as well as on deck checking around?

So if you're looking at some games's serverlists, it must be hundreds, if not thousands of people having those issues and not being listed. Google also has a lot of matches for this error since about december 2023.

I can confirm this issue still exists. I used both the apt install method for debian as well as the manual steamcmd install method. once steamcmd updates at first launch this issue appears. I am trying to install the PalWorld Test Server on Linux.

and in case it matters at all, I am using anonymous login instead of tying it to my account specifically. the game will download, but cannot run because steamservice.so cannot be found

Can confirm with brad-charboneau

Also encountering this exact issue when trying to install the PalWorld Test server. I encountered this error on both a manual, and an apt install of steamcmd.

Same issue. Spent 2 hours trying to get it to work.

+1 for this one, happening on both my ubuntu and debian images as well.

I am also having this same issue. Have tried multiple methods on ubuntu. Docker container, manual install, apt install of PalWorld.

Same issue here on fresh Debian 12 using apt install, added non-free and contrib to sources manually as well to get apt to work.

+1,same issue when i install of Palworld

same palworld install

`steamcmd +login anonymous +app_update 2394010 validate +quit

Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
OK
`

Enough with the "same issue" and "+1" reports which don't contain anything meaningful please. Unless there is anything constructive to add to the issue, this is absolutely of no help whatsoever. It's just creating noise for the people who are following it.

It's clear that this so is missing from the package. We get that. Subscribe to the issue and wait for updates. Thank you.

Replying to https://github.com/ValveSoftware/steam-for-linux/issues/10393#issuecomment-1902078706

I have the same output, the strange thing is that I still can't connect by ip and port, the startup script prints out
dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory Setting breakpad minidump AppID = 2394010 [S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded. [S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded. [S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded. [S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.
and then stops outputting. I have opened the corresponding port in ufw
BTW, is DefaultPalWorldSettings.ini in the same directory as the startup script a server configuration file?I modified the port to "PublicPort=14248".

Guys, english please.

Replying to https://github.com/ValveSoftware/steam-for-linux/issues/10393#issuecomment-1902080174

我没修改配置文件，指定端口号应该是启动命令后加上 port=xxx，你可以用netstat -npl|grep xxx确保对应端口已经启动
cd ~/Steam/steamapps/common/PalServer
./PalServer.sh port=18211

Replying to https://github.com/ValveSoftware/steam-for-linux/issues/10393#issuecomment-1902080174

忘记说了 端口是UDP的

Replying to https://github.com/ValveSoftware/steam-for-linux/issues/10393#issuecomment-1902095883

Can connect to server, but can't change port. Configration file in Pal/Saved/Config/LinuxServer/PalWorldSettings.ini not work,which makes me really confused.

Attention to everybody who is coming here because of PalServer!
steamservice.so line is a warning and does not prevent server from functioning!

There is something wrong with your configuration if you cannot join!

Lets be clear the issue at hand seems to stem from steamcmd update not including the steamservice.so file in the most recent update. Because each new installation using steamcmd must also update steamcmd then that means any NEW linux installation will see this issue. Not just PalWorld but ALL steamcmd games that utilize Steam's APIs.

I see people mentioning that steamclient.so is missing and that is not what this ticket is about nor are we attempting to bring to steams attention. Please lets not conflate the issues.

Attention to everybody who is coming here because of PalServer! steamservice.so line is a warning and does not prevent server from functioning!

There is something wrong with your configuration if you cannot join!

This comment stands true, even though you may see steamservice.so errors you can still connect to the server given a correct .ini config file.

Guys, this is NOT about steamclient.so! In case of it, something else is wrong and this is NOT the appropriate issue for it!
This isn't related in any case. It doesn't help and it doesn't resolve the actual issue mentioned here.

I recently (yesterday) used the cm2network/steamcmd image to set up a server with Docker. Today, while I was setting up another server for testing purposes without Docker, I ran into the issue mentioned by the OP.

This makes me wonder - since the image I mentioned above is functional, wouldn't that be a little of help? In the related Dockerfile we can see the following lines:

	&& su "${USER}" -c \
		"mkdir -p \"${STEAMCMDDIR}\" \
                && curl -fsSL 'https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz' | tar xvzf - -C \"${STEAMCMDDIR}\" \
                && \"./${STEAMCMDDIR}/steamcmd.sh\" +quit \
                && ln -s \"${STEAMCMDDIR}/linux32/steamclient.so\" \"${STEAMCMDDIR}/steamservice.so\" \
                && mkdir -p \"${HOMEDIR}/.steam/sdk32\" \
                && ln -s \"${STEAMCMDDIR}/linux32/steamclient.so\" \"${HOMEDIR}/.steam/sdk32/steamclient.so\" \
                && ln -s \"${STEAMCMDDIR}/linux32/steamcmd\" \"${STEAMCMDDIR}/linux32/steam\" \
                && mkdir -p \"${HOMEDIR}/.steam/sdk64\" \
                && ln -s \"${STEAMCMDDIR}/linux64/steamclient.so\" \"${HOMEDIR}/.steam/sdk64/steamclient.so\" \
                && ln -s \"${STEAMCMDDIR}/linux64/steamcmd\" \"${STEAMCMDDIR}/linux64/steam\" \
                && ln -s \"${STEAMCMDDIR}/steamcmd.sh\" \"${STEAMCMDDIR}/steam.sh\"" \
	# Symlink steamclient.so; So misconfigured dedicated servers can find it
 	&& ln -s "${STEAMCMDDIR}/linux64/steamclient.so" "/usr/lib/x86_64-linux-gnu/steamclient.so" \
	&& rm -rf /var/lib/apt/lists/*

This looks to me like the maintainer is aware of some issues related to the steamservice.so and creates links to fix that. However, I've got limited knowledge and understanding of what's going on here exactly, so if anyone more knowledgable would chime in I'd greatly appreciate it.

This looks to me like the maintainer is aware of some issues related to the steamservice.so and creates links to fix that. However, I've got limited knowledge and understanding of what's going on here exactly, so if anyone more knowledgable would chime in I'd greatly appreciate it.

Based on this I was able to manually create a link and overcome the error.

Before:

[topdog@arkbox steam]$ ./steamcmd.sh
tid(2579) burning pthread_key_t == 0 so we never use it
Redirecting stderr to '/home/topdog/steam/logs/stderr.txt'
Logging directory: '/home/topdog/steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1705108307
-- type 'quit' to exit --
Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory
OK

Steam>quit

So then I created the link:

[topdog@arkbox steam]$ ln -s linux32/steamclient.so ./steamservice.so

Ran the command again:

[topdog@arkbox steam]$ ./steamcmd.sh
tid(2676) burning pthread_key_t == 0 so we never use it
Redirecting stderr to '/home/topdog/steam/logs/stderr.txt'
Logging directory: '/home/topdog/steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1705108307
-- type 'quit' to exit --
Loading Steam API...OK

Steam>quit

Thanks for the tip. I wouldn't have expected the 'client' library to be a suitable substitute for the 'service' library, but it seems to do the trick.

I was then able to update my game server (ark) and connect no problem, even though it had been offline for ~9 or more months prior.

Attention to everybody who is coming here because of PalServer! steamservice.so line is a warning and does not prevent server from functioning!

There is something wrong with your configuration if you cannot join!

This is correct. steamservice.so is an optional module that has no bearing on steamcmd functionality. It does not need to be packaged or artificially introduced into the steamcmd tree so that it would be loaded.

If you have an actual regressed or broken functionality issue, please report that as a separate issue. You can certainly include a log and mention that you are seeing a message about steamservice.so not loading, but it's not likely to be the cause of your troubles.

@TTimo hold on, please reopen. Please see my initial comment. Steamcmd itself is complaining without any game / 3rd party related at all.
It also seems to cause trouble registering/using actual steam services like registering the server via steam and stuff like that. Ignore those who hijacked this issue.

@idl0r I agree, this warning did not used to occur with just steamcmd itself, and then suddenly one day I run it to do an update and it starts happening.

However, I wonder if @TTimo is implying that whether that message appears or not, it's not interfering with the operation of steamcmd anyway.

I note that the "OK" is still appearing at the end of the command run and update, whether that warning appears or not. So perhaps it can be ignored, and that is the message to us? That steamcmd doesn't need its functionality and so the inability to load the file just doesn't matter.

Hopefully this can be clarified, although for now I can also use my workaround if really needed.

@idl0r there is no error in your report - at least none that affects functionality. You are showing the normal process of steamcmd self-updating and exiting as requested (you gave it a +quit command).

I understand that the message about steamservice.so not loading looks like some problem happened, but assure you it's fine. We'll update steamcmd so it skips that part since it was never meant to attempt this in the first place.

I have the same issue when working with Docker, I usually run my servers on Windows and there's no problem there, but when I try to make a container it always gives me the steamservice.so file error.

I tried the @ndarlington solution but didn't work for me.

I love Steam's service, but I hate the desktop client with a passion, for a long list of technical reasons.

Ideally, I could just use steamcmd to install/update/run all my games, and use Steam's website in case I need to access any of the fluff. However, I'm not sure how viable this is, and I can't try it out because trying to run a game (e.g. app_run 550) fails with the error that steamservice.so can not be found.

I tried several games, all of them fail.

Is this related?