Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
nigel@localhost Desktop]$ df
df: /run/user/1000/doc: Operation not permitted
Depending in which user and which directroy you are in, you will see this error. If you are a regular user, and run the command on the root partiton, you do not have permission to do so.
Either su to root and run it or sudo and run it. This part depends on what distro you are running.
Depending in which user and which directroy you are in, you will see this error. If you are a regular user, and run the command on the root partiton, you do not have permission to do so.
Either su to root and run it or sudo and run it. This part depends on what distro you are running.
I agree with the "run it as root" part, but I do not understand why a regular user (UID = 1000) would get that explicit message since every directory in that path has at least r-x permissions for the user/owner. I see the same message on my system.
There is a split of paths at /run/user/* where both user 0 and user 1000 have continuing paths but the message is not about unable to follow the /run/user/0/* path, but about the /run/user/1000/doc path.
The only conjecture I can make is that it is a bug in df in that it reports the last path seen instead of the one that actually fails.
Another question I have is "why is df attempting to report data on a virtual file system?" /run is a tmpfs structure and df should not even look at those since the user has no way to affect that space anyway. Although on fedora /run/media is the mount point for media file systems, none of the rest of /run has any connection to an actual hard file system.
I just checked on my Ubuntu system which mounts media at /media and it also gives the same error "df: /run/user/1000/doc: Operation not permitted" to the df command when run as a regular user. This really seems a bug in df.
We should not be forced to run df as root. Df does not give similar errors anyplace else that I have seen even though there are other large parts of the / file system that are not user readable, such as /root, /selinux, etc.
Hello,
This is/was running as a user. I am running as a user. This is mageia version 8.
It has only been used for a short while. It could be a bug.
Code:
uname -a
Linux localhost.localdomain 5.10.25-desktop-1.mga8 #1 SMP Sat Mar 20 16:45:02 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
[nigel@localhost Desktop]$
Who is snap? Anybody we know? And what this citizen snap is storing there? And what kind of weird permissions our friend snap is applying on it?
Just another bit of oddity with /run/user/1000/doc, since for me it only exists on my Ubuntu system. That directory has mode 700, and the sub-directories under it are all mode 500. Might have an affect on what df is able to do, but I still don't understand that error when it is owned by the user running df. AFAIK df never writes to the disk it is scanning.
Last edited by computersavvy; 03-30-2021 at 08:30 PM.
I tried the Plasma/kde desktop and it WORKS OK.
Back to Mate & no-good again.
I am not sure what to do now !
Here is the password file:
Code:
[nigel@localhost Desktop]$ cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/bin/sh
daemon:x:2:2:daemon:/sbin:/bin/sh
adm:x:3:4:adm:/var/adm:/bin/sh
lp:x:4:7:lp:/var/spool/lpd:/bin/sh
sync:x:5:0:sync:/sbin:/bin/sync
mail:x:8:12:mail:/var/spool/mail:/bin/sh
news:x:9:13:news:/var/spool/news:/bin/sh
uucp:x:10:14:uucp:/var/spool/uucp:/bin/sh
operator:x:11:0:operator:/var:/bin/sh
games:x:12:100:games:/usr/games:/bin/sh
nobody:x:65534:65534:Nobody:/:/bin/sh
vcsa:x:69:69:virtual console memory owner:/dev:/sbin/nologin
messagebus:x:999:999:system user for dbus:/:/sbin/nologin
systemd-coredump:x:998:998:systemd Core Dumper:/:/sbin/nologin
systemd-network:x:192:192:systemd Network Management:/:/sbin/nologin
systemd-resolve:x:193:193:systemd Resolver:/:/sbin/nologin
systemd-journal-remote:x:993:993:systemd Journal Remote:/:/sbin/nologin
systemd-timesync:x:992:992:systemd Time Synchronization:/:/sbin/nologin
rpm:x:991:991:system user for rpm:/var/lib/rpm:/bin/false
polkitd:x:990:990:system user for polkit:/usr/lib/polkit-1:/sbin/nologin
rtkit:x:989:989:system user for rtkit:/proc:/sbin/nologin
mysql:x:988:988:system user for mariadb:/var/lib/mysql:/bin/bash
firebird:x:987:985:system user for firebird:/var/lib/firebird/data:/sbin/nologin
pipewire:x:986:984:PipeWire System Daemon:/var/run/pipewire:/sbin/nologin
flatpak:x:985:983:User for flatpak system helper:/:/sbin/nologin
sddm:x:984:979:system user for sddm:/var/lib/sddm:/sbin/nologin
nigel:x:1000:1000:Nigel:/home/nigel:/bin/bash
samba:x:983:977:system user for samba:/dev/null:/bin/false
davfs2:x:982:976:system user for davfs2:/run/mount.davfs2:/bin/false
geoclue:x:981:975:system user for geoclue:/var/lib/geoclue:/sbin/nologin
[nigel@localhost Desktop]$
About the same time I was fiddling with the keyboard preferences this happened.
Not quite what to do now.
You probably did not want to post the passwd file.!
What do you mean "this happened again".
This thread is about df and the error it gave and I do not understand the tie between that, the switch from plasma to mate, and the password file.
Yes, almost every near modern and newer system assigns the first user to log in the UID of 1000. That is a given, but does not tie your last post to the topic.
In case you are concerned about the error from df, don't be. It has been there for some time and is actually benign as far as actual results.
Note the numbers reported are the same whether run as root (sudo) or as my regular user.
That is just wrong. The correct sentence would be: there is something what you don't understand.
Unfortunately I cannot explain it, because I have no doc dir too, but I guess it is a special kind of dir used by a special kind of app. Probably related to this: https://snapcraft.io/store
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.