So it seems that the coreutils part of this is done, if I am reading you correctly. So I suppose this bug is fixed for coreutils but continues to be a problem for xdg-desktop-portal, which in turn seems to be part of flatpak.Īnd I see it has been reported (under the same name) to flatpak: If statfs works on /run/user/1000/gvfs and not /run/user/1000/doc, that indicates to me that there is an underlying problem with the creators of /run/user/1000/doc (which as I understand it from this bug report is xdg-desktop-portal). Adding to the mystery was the stale date () and the fact that the directory was accessible but not modifiable.Īlso in general I'm not a big fan of fixing symptoms rather than problems. In general I don't like surprises in my filesystems, and I had not seen this one before. It notes, "If problem still persists, please make note of it in this bug report." So I did. ![]() I was looking at a different problem in /run/user (related to DBus) and ran across this bug description. I do not use gnome-shell or flatpak myself. > addition (?) of fuse.portal is new in Fedora 33? > But for some reason I noticed it only in F33 and only recently, maybe the I have asked on the Ubuntu bug regarding the status of upstream inclusion of the fix: #Dr dev sebastian pipenet PatchThe Fedora component is actually correct but I refuse to patch coreutils in Fedora until the fix is accepted by gnulib upstream. > So, maybe I should've opened the bug against gnulib instead :-) > Compiled and tested, and df(1) will exit with RC 0, unless run with -a: > Indeed, I see it now building coreutils-git will pull in gnulib, So it is really the "fuse.portal" file system what causes us problems. > portal fuse.portal 0 0 0 - /run/user/1000/doc > Filesystem Type 1K-blocks Used Available Use% Mounted on (In reply to Christian Kujau from comment #5) So, maybe I should've opened the bug against gnulib instead :-)īut for some reason I noticed it only in F33 and only recently, maybe the addition (?) of fuse.portal is new in Fedora 33? var/tmp/df: /run/user/1000/doc: Operation not permitted || strcmp (Fs_type, "fuse.portal") = 0 \Ĭompiled and tested, and df(1) will exit with RC 0, unless run with -a: ![]() $ diff -git a/gnulib/lib/mountlist.c b/gnulib/lib/mountlist.c Indeed, I see it now building coreutils-git will pull in gnulib, so something like this might^W will do the trick: > Upstream is gnulib in this case though: Portal fuse.portal 0 0 0 - /run/user/1000/docīinfmt_misc binfmt_misc 0 0 0 - /proc/sys/fs/binfmt_misc Gvfsd-fuse fuse.gvfsd-fuse 0 0 0 - /run/user/1000/gvfs Net_cls cgroup 0 0 0 - /sys/fs/cgroup/net_cls Sunrpc rpc_pipefs 0 0 0 - /var/lib/nfs/rpc_pipefs Hugetlbfs hugetlbfs 0 0 0 - /dev/hugepagesĭebugfs debugfs 0 0 0 - /sys/kernel/debugįusectl fusectl 0 0 0 - /sys/fs/fuse/connectionsĬonfigfs configfs 0 0 0 - /sys/kernel/config ![]() Selinuxfs selinuxfs 0 0 0 - /sys/fs/selinux Securityfs securityfs 0 0 0 - /sys/kernel/security (In reply to Kamil Dudka from comment #4)įilesystem Type 1K-blocks Used Available Use% Mounted onĭevtmpfs devtmpfs 16356544 0 16356544 0% /dev Yes, the Ubuntu folks appear to have adjusted coreutils/lib/mountlist.c to exclude fuse.portal, but upstream doesn't even seem to have to have a mechanism for excluding certain filesystems from printing. Ls: cannot access '/run/user/1000/doc': Permission deniedĭrwx. It gets a bit weird, because I cannot access the mountpoint as root, only as the user the mount was configured for: Portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) However, xdg-desktop-portal cannot be uninstalled as gnome-shell depends on it for some reason.Īs root, no warning is printed, but the file system doesn't show up either:įilesystem Size Used Avail Use% Mounted on The workaround is to disable (and mask) rvice. > df (and other commands) fail on /root/.cache/doc #512 > df: /run/user/1000/doc: Operation not permitted rvice is running, as it is the defaultĭf should exit with RC 0 and stderr should be empty. ![]() Version-Release number of selected component (if applicable):ġ. #Dr dev sebastian pipenet codeDf(1) is exiting with a non-zero return code when run as a normal user:ĭf: /run/user/1000/doc: Operation not permitted
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |