I can confirm this bug. my mount look similar.
Also, installing games was still possible on the 8th of January (as I bought and installed Solar 2 then).
Yup, games are still installable with this warning in the current build, I just dismissed it and carried on.
I hit this same issue when installing the Half-Life Beta for the first time; I just hit OK, and the message did not re-appear.
I'm running Arch Linux x86_64, updated today.
My / partition's fstab entry (I have no /home partition):
LABEL=root / ext4 noatime,discard 0 1
Output of mount for /:
/dev/sda3 on / type ext4 (rw,noatime,discard,data=ordered)
I have just encountered the same problem, gone after reloading Steam.
Can you run Steam from the command line and show the output? You should get some shell execute error in the output.
No, can't see any new messages in stdout while trying to install.
The message would only show up if that error dialog shows up.
I meant I reproduced it again by deleting Counter-Strike content and trying to re-install it.
The problem appears only after any installed game has been launched successfully and persists until I re-run Steam.
That's good info, is there any output to stdout or stderr when this happens?
As I already said, none.
Can you please try this in the latest build? I wasn't able to reproduce it, but I added additional debug output.
It seems this isn't happening for me any more.
I exit Half-Life and try installing World of Goo four times:
Game removed: AppID 70 "Half-Life (Beta)", ProcID 3946
Generating new string page texture 131: 128x256, total string texture memory is 2,27 MB saving roaming config store to 'sharedconfig.vdf'
roaming config store 2 saved successfully
Execute test returned -1
Generating new string page texture 133: 24x256, total string texture memory is 2,29 MB
Execute test returned -1
Execute test returned -1
Installing breakpad exception handler for appid(steam)/version(1359600063_client)
Installing breakpad exception handler for appid(steam)/version(1359600063_client)
Execute test returned -1
Looks like nothing related here except "Execute test returned -1" messages.
BTW, my home is mounted as /dev/sda4 on /home type ext4 (rw,noatime,data=ordered)
I'm experiencing the same, despite i can run binaries from selected partition
Guys, I've found the workaround for this problem:
1st way is to move folder ~HOME/.local/share/Steam/ubuntu12_32/steam_runtime/amd64 -> ~HOME/.local/share/Steam/ubuntu12_32/steam_runtime/amd641 and rerun Steam
2nd way is to copy to subfolder lib/x86_64-linux-gnu/ corresponding libraries: at least libc-2.15 and its symlinks.
I just downloaded ubuntu 12.10 eglibc 2-15 package (http://security.ubuntu.com/ubuntu/pool/main/e/eglibc/libc6_2.15-0ubuntu10.2_amd64.deb) and extracted corresponding directories from it to corresponding directories under ~HOME/.local/share/Steam/ubuntu12_32/steam_runtime/amd64 directory (e.g. lib => ~HOME/.local/share/Steam/ubuntu12_32/steam_runtime/amd64/lib, /usr => ~HOME/.local/share/Steam/ubuntu12_32/steam_runtime/amd64/usr , etc.)
It is because of ~HOME/.local/share/Steam/ubuntu12_32/steam_runtime/amd64/lib/.../libtinfo.so wants libc.so.6 libraries but does not find it
I've added some more logging to help track this down. If anybody runs into this, please post the standard output.
Failed system("/home/john/Steam/.steam_exec_test.sh") in execute test: No child processes
Great, this is exactly what I needed. This is fixed for the next update.
Thanks!
Same problem. I have no /home partition and root filesystem is not mounted with noexec:
/dev/mapper/sda2_crypt on / type ext4 (rw,noatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered)
On the console I noticed this line every time I tried to add new directory to the game library in settings:
sh: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /home/steam/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/lib/x86_64-linux-gnu/libtinfo.so.5)
Note that I am using debian unstable, which contains too old libc for steam, so I had to set up first a separate libc in $HOME/steamlibc and pointed LD_LIBRARY_PATH in order to be able to run steam at all.
Seems that steam is not passing LD_LIBRARY_PATH to whatever process it is executing to test executability of binaries, causing this bug.
@bilbo2 the update that just went live should have a fix for this, are you on it now?
Umm ... well, the steam update that arrived a few moments ago seems to fixed this problem for me....
Great, thanks!
I still experience this problem on Arch Linux x64. The permissions of the folder (/media/Daten/Steam) look fine:
drwxr-xr-x 3 photon users 4096 15. Feb 08:24 Steam
Still, trying to install a game into this folder results in the error described above. I get following message in the terminal:
sh: /media/Daten/Steam//SteamApps/.steam_exec_test.sh: Permission denied
What can I do to debug this issue further?
@Photon89 I also got this issue on Arch Linux.
I fixed it by changing the fmask from 133 to 022
cat /etc/fstab
UUID="myuid" /mnt/Data ntfs-3g nosuid,nodev,rw,exec,uid=my_username,gid=users,dmask=022,fmask=022 0 0
btw, if you want to know more about umask read this (found this in the arch wiki): click here
@sh4nks: Thanks for the hint, but unfortunately the directory is on an ext4 filesystem which afaik doesn't support fmask/dmask mount options.
@Photon89, try this:
cd /media/Daten/Steam//SteamApps
echo "#!/bin/sh" >exec_test.sh
echo "exit 0" >>exec_test.sh
chmod +x exec_test.sh
ls -l exec_test.sh
./exec_test.sh
Thanks for the hint, seems to be a problem on my side. Any script on the partition cannot be executed. I'll try to find a solution and comment if I find any.
Great, thanks!
Solution found, it was the "user" option in my fstab which prevented the "exec" option from being used, see https://www.linuxquestions.org/questions/linux-software-2/cannot-execute-files-on-ext4-partition-728878/#post4152671
After removing the "user" option everything works fine. Thanks again for the help to everybody!
Sorry to come back to this older issue, but I think I have a configuration that's not covered yet :)
I use extended ACLs on my NAS (linux, ext4) mounted over SAMBA with ACLs enabled to my linux desktop.
I can execute from the mounted filesystem:
# ./.steam_exec_test.sh
# echo $?
0
Here are my mount options (from /proc/mounts, redacted for privacy):
//nas/work /home/leeps/nas/work cifs rw,relatime,vers=1.0,sec=ntlmssp,cache=strict,unc=\134\134nas\134work,username=leeps,domain=NAS,uid=1000,forceuid,gid=0,noforcegid,addr=<redacted>,unix,posixpaths,acl,rsize=1048576,wsize=65536,actimeo=1 0 0
Here's what's happening on the Steam console when trying to add a Steam Library folder:
sh: /home/leeps/nas/work/SteamLibrary//SteamApps/.steam_exec_test.sh: No such file or directory
When I created an "exit 0" script in that location, it changed to:
sh: /home/leeps/nas/work/SteamLibrary/.steam_exec_test.sh: No such file or directory
Putting the file in both locations did not work, although that doesn't yield an error message in the client itself. But on the console:
sh: /home/leeps/nas/work/SteamLibrary/.steam_exec_test.sh: No such file or directory
Since I did put the file there, I'm assuming the client deletes it at some point.
If you need any more input, let me know.
@leeps I had that same problem with cifs. The problem occurs if a share is not case sensitive with file names.
case sensitive = yes
in smb.conf fixes it for me.
@tunp Amazingly, that worked.
It's amazing, because the Samba server has a default of "auto" for case sensitive, meaning it will listen for a client's indication of case sensitive file support, which Linux clearly has.
Anyway, permissions are not set correctly after installing, which was another issue with the configuration of the Samba server (I'm forcing create mask = 664 for other reasons). I had to seperate the SteamLibrary share to keep the default file creation modes.
Thanks, for now all my issues seem resolved!
I know this is an old thread but I solved this with the following: https://steamcommunity.com/groups/SteamClientBeta/discussions/0/624076851216083676/
@millerthegorilla Totally solved my problem too. Installed Steam today after a few months without. So it is just the problem of case-sensitiveness.
Thank you !
it's still wrong in current beta
Still get the same issue. Can't create Steam folder on any ext4 drive. I don't get messages about glibc or similar. SteamApps is in lower case, but it didn't helps.
Same issue as this I believe?
https://github.com/ValveSoftware/steam-for-linux/issues/3936
my workaround: /etc/fstab
/home/kyra/.steam/steam/steamapps /home/kyra/.steam/steam/SteamApps none bind 0 0
hurts but works (symlink doesn't work for me, neither absolute nor relative)
also, the error still happens sometimes (at least steam doesn't forget about the library when mounted as above), which can be "fixed" by running steam as:
strace -ff -e trace=file steam
seems to be a heisenbug there, cause when trying to debug using strace, it worked just fine. simply run steam with strace, start the download, and restart steam without strace so it continues downloading without the overhead introduced by strace
@slouken why is this issue closed? seems to be still an issue for some of us. also it's broken on current stable (tried opting out of steam beta and reinstalling to see if it works there, doesnt).
@nonchip your solution with strace works for me, but I need to start steam every time with strace, because it will not see previously created library dirs. Also, strace fixes blank store, community, etc. pages. Fix with fstab didn't work.
@h8 for me sometimes it shows the library without strace, but can't install, sometimes it doesn't.
with strace it works everytime, so yeah, we should be using that. but srsly, that's one creepy bug :P
it seems like an issue with the recent kernel in Ubuntu LTS https://github.com/ValveSoftware/steam-for-linux/issues/3936
Deleted the local content of a game and went to reinstall it and got this:
I haven’t changed the install location at this point, the dialog appeared as soon as the install window did. Its happened once before but I thought nothing of it. I cannot get it to reproduce consistently, my ~ filesystem supports executing: