First off don't log in as root
What file system is the file under? What are the results of ls -l?
First off don't log in as root
What file system is the file under? What are the results of ls -l?
Results of ls -l
total 27040
-rw-r--r-- 1 user user 27560272 Apr 13 2021 'Commandos 2 HD Remaster'
drwxr-xr-x 7 user user 32768 Apr 24 2021 'Commandos 2 HD Remaster_Data'
-rw-r--r-- 1 user user 200 Apr 24 2021 run.sh
-rw-r--r-- 1 user user 2465 Mar 3 2021 uninstall.sh
Can you try copying the file to a different name?
ie cp filename filename2
The partition containing the files may be mounted readonly. Check less /etc/mtab for an ro option on that entry.
Also, at least for ext4 filesystems, probably many others, there's an option (noexec) that prevents any execution. Might be worth checking that
That wouldn't prevent the chmod, just would refuse to execute even if the file is a+x
This is the result for sda3
/dev/sda3 /media/user/8ACB-8EB4 vfat rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro 0 0
vfat doesn't allow linux permissions and ownership.
oh yeah I don't think vfat can do file permissions
Not really sure whats going on here. Some info that might help might be.
If so try sudo chown root:root filename.sh. If it is not to be run as root try sudo chown $USER:$USER filename.sh
What is the permissions does the file have? ls -lg?
Does the file have a shebang #!/usr/bin/env bash?
That's all I got. If this doesn't help someone will come along soon that will have better ideas.
It might also be that the #! points to non executable file
sudo chown root:root run.sh
[sudo] password for user:
chown: changing ownership of 'run.sh': Operation not permitted
and the latter does nothing. Or seems not to anyway.
Can't explain why your file browser doesn't work and I don't suggest logging into your desktop as root. You should take steps to make that impossible, in fact.
Now you said this doesn't work
sudo chmod -v +x filename.sh
And that's baffling. What is the exact error message and output of that command? Also is the file in question in a weird place or on a weird filesystem?
Linux questions Rules (in addition of the Lemmy.zip rules)
Tips for giving and receiving help
Any rule violations will result in disciplinary actions