$pshome/pwsh is not an executable in 7.5.0-preview.3 too. This requires manual setting of the execution bit.

I do not understand what is for dll-files have to be executable, they are always 664:

$ (dir $pshome/*.dll).count
227

$ (dir $pshome/*.dll | ? { [convert]::ToString([int] $_.UnixFileMode, 8) -eq 664 }).count
227

$ (dir $pshome/*.dll | ? { (stat -c %a $_) -eq 664 }).count
227

As a comparison, this is 7.4.2:

PS 16:23h 33.39 ms | /opt/microsoft/powershell/7> (dir $pshome/*.dll).count
228
PS 16:23h 216.98 ms | /opt/microsoft/powershell/7> (dir $pshome/*.dll | ? { [convert]::ToString([int] $_.UnixFileMode, 8) -eq 664 }).count
0
PS 16:24h 163.13 ms | /opt/microsoft/powershell/7> (dir $pshome/*.dll | ? { (stat -c %a $_) -eq 664 }).count
0

Version 7.4.3:

PS 16:28h 9.33 ms | /opt/microsoft/powershell/7> (dir $pshome/*.dll).count
228
PS 16:28h 208.1 ms | /opt/microsoft/powershell/7> (dir $pshome/*.dll | ? { [convert]::ToString([int] $_.UnixFileMode, 8) -eq 664 }).count
226
PS 16:28h 162.19 ms | /opt/microsoft/powershell/7> (dir $pshome/*.dll | ? { (stat -c %a $_) -eq 664 }).count
226

And here is the result of 7.4.2 with different filter:

PS 16:36h 718.7 ms | /opt/microsoft/powershell/7> (dir $pshome/*.dll).count
228
PS 16:36h 105.65 ms | /opt/microsoft/powershell/7> (dir $pshome/*.dll | ? { [convert]::ToString([int] $_.UnixFileMode, 8) -eq 744 }).count
174
PS 16:36h 128.7 ms | /opt/microsoft/powershell/7> (dir $pshome/*.dll | ? { (stat -c %a $_) -eq 744 }).count
174

How does this affect pwsh as a whole? I didn’t notice any complaints about the use of types and their methods; Add-Type and using statements apparently do not depend on this. The only thing that does not changes from release to release is the need to set capabilities for pinging using Test-Connection

sudo setcap cap_net_raw=eip $PSHome/pwsh

This is true for powershell-*-linux-x64.tar.gz and Arch-based Linux.

Oh I did not see anything not working so far. I just documented the differences between 7.4.2 and 7.4.3
The major problem was so far only the pwsh having no +x
The rest was just that I figured when using ls -l, that there are a lot more "green" entries in 7.4.2 in despite of 7.4.3 ;-)
Not that it was correct that the .dll had been marked +x before......

Ran into this too on a freshly built Arch system.
However in my case it prevents pwsh from running at all:

> pwsh
bash: /usr/bin/pwsh: Permission denied

If I either make all the files executable or rollback to 7.4.2 I am able to start PowerShell without issue.

Not a good look, mates. It's been over a week now and the official Linux (and macOS apparently) releases are still broken.
Are we absolutely certain this isn't another xz situation?

Ran into this too on a freshly built Arch system.

However in my case it prevents pwsh from running at all:

> pwsh

bash: /usr/bin/pwsh: Permission denied

If I either make all the files executable or rollback to 7.4.2 I am able to start PowerShell without issue.

You only have to chmod +x on the pwsh