SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
These are the permissions I normally use and should work
Code:
bash-5.2# ls -l
total 144
-rw------- 1 hc hc 533 May 13 2018 Conta\ Espaços\ em\ Branco.txt
-rw------- 1 hc hc 120003 May 13 2018 Count\ white\ spaces.png
-rw------- 1 hc hc 3 Jan 7 11:04 test.txt
-rw------- 1 hc hc 1494 Feb 15 2019 \ remove\ all\ extra\ blank\ spaces\ from\ giv.txt
-rw------- 1 hc hc 1451 Feb 15 2019 \ trim\ both\ leading\ and\ trailing\ white\ s.txt
-rw------- 1 hc hc 1374 Feb 15 2019 \ trim\ leading\ white\ space\ characters\ fr.txt
-rw------- 1 hc hc 1342 Feb 15 2019 trim\ trailing\ white\ space\ characters\ fr.txt
bash-5.2# lsattr
--------------e------- ./ trim both leading and trailing white s.txt
--------------e------- ./ remove all extra blank spaces from giv.txt
--------------e------- ./Conta Espaços em Branco.txt
--------------e------- ./ trim leading white space characters fr.txt
--------------e------- ./test.txt
--------------e------- ./trim trailing white space characters fr.txt
--------------e------- ./Count white spaces.png
The problem is that I can't see the text of the file, not even using the cat command
I can't even rename the file
Notice in image 1 that what is different is that the file has a lock on it, and when I open it, the name of the file is in parentheses. And it doesn't show the file
In pictures 2 and 3 are the permissions
I notice that in image 4 the normal working file it shows the permissions differently in the window!
I don't know what happened to make the file unavailable, because it wasn't like this.
I don't know of any other permission that could prevent me from accessing the file!
To the best of my knowledge, all files have the same permissions, so they should work accordingly!
cd /path/to/files/
sudo chown $USER:$USER *
sudo chmod 660 *
That doesn't change anything! It just gives more permission! Not solving the problem!
I showed in the question that I already had read and write permission!
Adding: I am as root user, i.e., I have no root access to the file! Nor as hc user obviously!
Last edited by Apprentice+; 01-07-2023 at 09:41 AM.
You might have something odd going on with your file system and/or disk as this is not normal behaviour. Normally I'd say you made a file with a weird special character that you couldn't later access, but if you can click on it within a GUI that's not the case. Let's see 'stat *' on the files. What's that filesystem actually on? Are you trying to access a remote filesystem that is offline?
That doesn't change anything! It just gives more permission! Not solving the problem!
I showed in the question that I already had read and write permission!
Adding: I am as root user, i.e., I have no root access to the file! Nor as hc user obviously!
root doesn't need explicit read permission to read files, even the permissions look like this
Code:
.--------- 2,3k marav marav 17 oct. 2022 test
Also, if your files are on separate partition, it will be useful to have the mount options used in fstab
And, I suggest you, in a general manner, to avoid spaces in file names
My next guess: are there lock files attached? Take a look at:
Code:
# ls -l *txt .*txt
This won't fix anything, but it may show the next step.
Code:
bash-5.2# ls -l *txt .*txt
ls: cannot access '.*txt': No such file or directory
-rw-rw---- 1 hc hc 533 May 13 2018 Conta\ Espaços\ em\ Branco.txt
-rw-rw---- 1 hc hc 3 Jan 7 11:04 test.txt
-rw-rw---- 1 hc hc 1494 Feb 15 2019 \ remove\ all\ extra\ blank\ spaces\ from\ giv.txt
-rw-rw---- 1 hc hc 1451 Feb 15 2019 \ trim\ both\ leading\ and\ trailing\ white\ s.txt
-rw-rw---- 1 hc hc 1374 Feb 15 2019 \ trim\ leading\ white\ space\ characters\ fr.txt
-rw-rw---- 1 hc hc 1342 Feb 15 2019 trim\ trailing\ white\ space\ characters\ fr.txt
I don't understand where you are going with this!
I had already run ls in the question!
Last edited by Apprentice+; 01-07-2023 at 11:50 AM.
You might have something odd going on with your file system and/or disk as this is not normal behaviour. Normally I'd say you made a file with a weird special character that you couldn't later access, but if you can click on it within a GUI that's not the case. Let's see 'stat *' on the files. What's that filesystem actually on? Are you trying to access a remote filesystem that is offline?
root doesn't need explicit read permission to read files, even the permissions look like this
Code:
.--------- 2,3k marav marav 17 oct. 2022 test
Also, if your files are on separate partition, it will be useful to have the mount options used in fstab
And, I suggest you, in a general manner, to avoid spaces in file names
These files were saved, I don't know why they stayed like that.
And at the moment, as I informed you, I can't even rename them.
They are on a separate partition, which is automatically mounted by fstab at boot time!
These files were saved, I don't know why they stayed like that.
And at the moment, as I informed you, I can't even rename them.
They are on a separate partition, which is automatically mounted by fstab at boot time!
You might have something odd going on with your file system and/or disk as this is not normal behaviour. Normally I'd say you made a file with a weird special character that you couldn't later access, but if you can click on it within a GUI that's not the case. Let's see 'stat *' on the files. What's that filesystem actually on? Are you trying to access a remote filesystem that is offline?
I didn't create the files, I brought them from my cell phone a few years ago. At the time they worked normally.
Today I noticed this problem, and there are others in other folders that are like this too!
And yes, I'm worried that it's a HD problem
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Problem with file permissions
