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.
I don't understand where you are going with this!
I had already run ls in the question!
As I said, I wanted to check for a particular issue first, and fix it second. In this case, I checked for locked "hidden" files, and no, there weren't any.
And my next idea, is already Petri Kaukasoina's #15 above.
When you did getfacl .../Spaces , was "Spaces" the directory containing your files? If not, and "Spaces" was only one of those files, it could be that your directory containing the files lack the executable permission. The read permission gives you right to list the contents of the directory, the executable permission gives you right to enter the directory and the write permission to a directory gives you the right to create and rename files.
Otherwise, regardless of the permissions on the files, it could be that your filesystem for some reason has been mounted readonly. Do a:
Code:
cat /proc/mounts
and look for the line with the filesystem. Is it mounted rw or ro?
The file you mention has no problem, only the ones with locks
But your idea worked! For the graphical part I could not rename! I noticed that the terminal worked! This allows me to fix the files that are locked!
I have no idea what caused this for several files!
Code:
bash-5.2# ls -l
total 144
-rw-rw---- 1 hc hc 533 May 13 2018 Conta\ Espaços\ em\ Branco.txt
-rw-rw---- 1 hc hc 120003 May 13 2018 Count\ white\ spaces.png
-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
bash-5.2# mv *remove*.txt test2.txt
I was always trying to rename from the graphical part, be it in konqueror, dolphin or thunar, and the message was that the file did not exist!
I don't know why I didn't try the terminal! Since the terminal got!
When you did getfacl .../Spaces , was "Spaces" the directory containing your files? If not, and "Spaces" was only one of those files, it could be that your directory containing the files lack the executable permission. The read permission gives you right to list the contents of the directory, the executable permission gives you right to enter the directory and the write permission to a directory gives you the right to create and rename files.
Otherwise, regardless of the permissions on the files, it could be that your filesystem for some reason has been mounted readonly. Do a:
Code:
cat /proc/mounts
and look for the line with the filesystem. Is it mounted rw or ro?
The problem was solved by renaming in terminal! Which I hadn't tried, since I only tried things from the graphical part as I show in the screenshots in my question.
Thanks again to Petri Kaukasoina
The question that remains then is:
What happened to these files? Why did they give this problem? And from what I saw it affected the graphics part the most!
In the terminal, the cat command did not work, and the TAB command to write their names
From all your examples you have shown so far, commands in terminal has been run as root. Depending upon permissions, root might be more capable than an ordinary user, but usually you should avoid doing things as root.
Quote:
Originally Posted by Apprentice+
The question that remains then is:
What happened to these files?
It could also be that you graphical applications gets trouble because of broken filenames. It is possible, but a bad idea to name a file "*.*". One day someone might want to delete that file and depending upon how it is done it might end in disaster. Examples of good filenames are:
"fileA.txt"
"fileB.txt"
Example of a bad filename is:
"fileA.txt fileB.txt"
What would happen if you would want to remove the file with the bad filename "fileA.txt fileB.txt"? Depending upon how it is done it might instead affect the two files with good filenames.
It is possible, but a bad idea to put whitespaces in filenames.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
