Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#66953 - [steam] "bad interpreter: Permission denied"

Attached to Project: Community Packages
Opened by Xuanrui Qi (xuanrui) - Tuesday, 09 June 2020, 07:45 GMT
Last edited by Giancarlo Razzolini (grazzolini) - Tuesday, 16 June 2020, 10:32 GMT
Task Type Bug Report
Category Packages: Multilib
Status Closed
Assigned To Levente Polyak (anthraxx)
Giancarlo Razzolini (grazzolini)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Whenever I try to run steam by clicking on the desktop icon, or by running `/usr/bin/steam-runtime`, I get the error:

/usr/bin/steam-runtime: /usr/lib/steam/steam: /usr/bin/env: bad interpreter: Permission denied

But I have no problems if I run `sh /usr/bin/steam-runtime`.

The permissions on /usr/bin/env are set correctly. I don't have `noexec` set on any partition.

This is probably not a steam bug, but it seems that there is some permission mix-up.
This task depends upon

Closed by  Giancarlo Razzolini (grazzolini)
Tuesday, 16 June 2020, 10:32 GMT
Reason for closing:  Works for me
Comment by Doug Newgard (Scimmia) - Tuesday, 09 June 2020, 13:15 GMT
what does `file /bin` return?
Comment by Xuanrui Qi (xuanrui) - Tuesday, 09 June 2020, 14:32 GMT
"symbolic link to usr/bin", which looks alright to me. All other shebang scripts work just fine and it's only this one giving the error.
Comment by Doug Newgard (Scimmia) - Tuesday, 09 June 2020, 15:04 GMT
how about `type -a sh` and `type -a bash`?
Comment by Xuanrui Qi (xuanrui) - Tuesday, 09 June 2020, 18:02 GMT
"sh is /usr/bin/sh"

"bash is /usr/bin/bash"

I guess I see where the problem might be (no /bin/sh in the list), but I still have no idea how it is causing problems (and how to fix that)...
Comment by Doug Newgard (Scimmia) - Tuesday, 09 June 2020, 23:30 GMT
No, that's the expected output.
Comment by Xuanrui Qi (xuanrui) - Tuesday, 09 June 2020, 23:45 GMT
OK, thanks for confirming!

I couldn't really believe that this was actually a package bug. For the record, another machine of mine does not have this problem.

The machine which had problems with the shell script is running on ZFS, but I couldn't imagine that the problem is ZFS, given that I have no trouble with other shell scripts.
Comment by Xuanrui Qi (xuanrui) - Wednesday, 10 June 2020, 01:59 GMT
OK, thanks for confirming!

I couldn't really believe that this was actually a package bug. For the record, another machine of mine does not have this problem.

The machine which had problems with the shell script is running on ZFS, but I couldn't imagine that the problem is ZFS, given that I have no trouble with other shell scripts.
Comment by Giancarlo Razzolini (grazzolini) - Thursday, 11 June 2020, 16:37 GMT
What's the output of getfacl /usr/bin/env? Also, is your /usr a separate partition?
Comment by Xuanrui Qi (xuanrui) - Thursday, 11 June 2020, 17:28 GMT
$ getfacl /usr/bin/env
getfacl: Removing leading '/' from absolute path names
# file: usr/bin/env
# owner: root
# group: root
user::rwx
group::r-x
other::r-x

No, my /usr is not a separate partition (or subvolume, or mountpoint); since I'm running on ZFS I have only one partition on my hard drive.
Comment by Giancarlo Razzolini (grazzolini) - Thursday, 11 June 2020, 17:58 GMT
I have no idea, because I'm running steam-runtime just fine here. I don't think either this is a packaging bug, since this error is coming from /usr/lib/steam/steam, and not steam-runtime nor steam-native-runtime.
Comment by Xuanrui Qi (xuanrui) - Friday, 12 June 2020, 19:19 GMT
I'm running Steam fine on another machine of mine as well, but I just can't get it to run on this machine. The remove-and-reinstall doesn't work this machine either.

I can't fathom what might be wrong, but I suspect some subtle permissions bug. But that should be fixed by reinstalling, yet it is not...
Comment by Giancarlo Razzolini (grazzolini) - Monday, 15 June 2020, 17:51 GMT
Did you also remove your .steam directory on your user's home? I don't think the issue is on the package
Comment by Xuanrui Qi (xuanrui) - Tuesday, 16 June 2020, 03:09 GMT
No, I didn't. But I'll try now.
Comment by Xuanrui Qi (xuanrui) - Tuesday, 16 June 2020, 03:12 GMT
I just tried removing ~/.steam, ~/.steampath and ~/.steampid and reinstalling Steam, and it didn't help.

Judging by the error message, I didn't expect that it would be related to ~/.steam either.
Comment by Giancarlo Razzolini (grazzolini) - Tuesday, 16 June 2020, 10:32 GMT
Well, I'm out of ideas. At this point, I'm looking at ZFS as the culprit, the only thing I can think of. One thing I'm certain though, this is not a packaging issue. I suggest you open this bug report upstream, with as much information as you can provide.

Loading...