If you ever used GNU findutils non-root trying to find from / (find / -iname file) you'll have seen 'permission denied': /proc, /sys. Locate (mlocate replaced slocate probably replaced locate) is faster and skips forbidden files but finds any matching partial *file* name unless specify '-b "\file"' so I usually forget and use find. Can non-root users set find 'permission denied' errors to not display? Update someone on libera IRC #gnu said 'find / -iname file 2> /dev/null'.
        I also have this odd situation.

Works for me. You do a lot of strange things to your computer apparently, that result in issues that are unique to you.

1 members found this post helpful.

Okay but are you on Slackware64 15.1-current and using whatever software (such as from SlackBuidls.org) mounted the below?
d@1cosmos:~$ mount|grep doc
portal on /home/d/.cache/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
no

are you using any flatpak application?

mount|grep doc
portal on /home/d/.cache/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)

That looks very much like a "fuse" application - perhaps an iso mount ? In that case, if setup a certain way, not even root can get into it.
From the "fuse" man page :
General mount options:
These are FUSE specific mount options that can be specified for all filesystems:

default_permissions
By default FUSE doesn't check file access permissions, the filesystem is free to implement it's access
policy or leave it to the underlying file access mechanism (e.g. in case of network filesystems). This
option enables permission checking, restricting access based on file mode. This is option is usually
useful together with the allow_other mount option.

allow_other
This option overrides the security measure restricting file access to the user mounting the filesystem.
So all users (including root) can access the files. This option is by default only allowed to root,
but this restriction can be removed with a configuration option described in the previous section.

allow_root
This option is similar to allow_other but file access is limited to the user mounting the filesystem
and root. This option and allow_other are mutually exclusive.

I run Slackware-current 64bit (there is no Slackware 15.1) and have the same 'portal' mount as you but look at my mount point, it is completely different. I have this in a KDE5 environment as well as under XFCE, and it is exactly the same on Slackware 15.0 here on my other computer:

I absolutely never use flatpak (nor snapd) on Slackware because am not crazy.

Apparently so but I mount all ISOs as user in a way root can read.

There is: you don't know of changes/terminology.
When aaa_libraries (then other packages) reach a new version it's that prerelease version so after 15.1-current (or any version-current) becomes stable then current continues people will say 15.1+current (or version+current)... been this way since Slackware 7.1 (2001)). The plus means beyond stable like the minus means prerelease. Overwrite aaa_libraries-15.1 & etc. onto 15.0 (or vice versa) see what happens: see if you still think so.

What's portal anyway?

a mount is created in your $HOME/.cache folder most probably because you are not using a desktop environment that exports the environment variable XDG_RUNTIME_DIR (kde and xfce do that), the normal behaviour is the one that Windu described before, with a directory created under /run
see https://github.com/flatpak/xdg-deskt...ment-729700318

you can also export it manually in your ~/.bashrc file to some other tmpfs: for example here I use this

1 members found this post helpful.

Thanks for making that clear.

My .bashrc is large enough (and partly used as template) so I'd rather in fstab.

being user-dependant you can't put those lines in /etc/fstab

1 members found this post helpful.

You can point to all kinds of filenames with "15.1" in them but its version is still "15.0+" and not "15.1-current".
Let me show the authoritative places where the Slackware version is defined:

Source:
http://ftp.slackware.com/pub/slackwa...urrent-release

1 members found this post helpful.

As I mentioned in another thread, if you boot a recent -current .iso, it identifies itself as 15.1.

1 members found this post helpful.

that most probably is just the INSTALLERVERSION variable as defined in /source/installer/installer.SlackBuild: from the build_installer.sh script

Here you go:

Attached Thumbnails