Sorry for that, but copy linux executables onto filesystems unable to store linux(UNIX) file rights is idiotic idea in first place, so bug is not in Steam, but in user :smile:
It's not reasonable to check all scripts to see if the user has somehow prevented them from running before trying to run it.
Nothing extracted yet.
Had a user on freenode, #ubuntu-steam run into an issue where he copied the steam game dir to NTFS, then figured out it wouldn't work, and tried to copy it back..which wouldn't work because in the conversion to NTFS, the executable(+x) bit was truncated.
So, I think Steam should be checking its run_steam.sh files for executability.
If it is not set, it should try to set it (chmod +x run_steam.sh).
If it fails, (because the data resides on a FS that doesn't support it, in this example), it should say that it needs to set it, but can't because odds are the filesystem it's on doesn't support it (like NTFS).
This should prevent some users from making mistakes we don't want.