Repeating, endless SELinux alerts regarding ld.so.cache.
Ok.
Is this a problem? Is it causing problems? Is there something that you think needs to be fixed?
If it’s causing you problems, what is that problem?
Are you kidding?
Firstly, it’s burning 4% of my Ryzen 9 3900XT CPU just to continuously report the errors.
Secondly, Steam won’t start at all.
Thirdly, what is wrong with SELinux that it causes so many errors and problems?
Fourthly, I’m sure there’s more things wrong that I haven’t discovered yet.
What does Cockpit indicate in it’s SELinux section?
Here on Leap 16.0 but, for what it’s worth anyway:
> ls -lZ /etc/ld.so.cache
-rw-r--r--. 1 root root system_u:object_r:etc_t:s0 127251 3. Jan 14:56 /etc/ld.so.cache
>
> ls -lZ /etc/aliases.lmdb /etc/postfix/aliases.lmdb
-rw-r--r--. 1 root root system_u:object_r:etc_aliases_t:s0 32768 13. Okt 11:27 /etc/aliases.lmdb
-rw-r--r--. 1 root root system_u:object_r:etc_aliases_t:s0 32768 13. Okt 16:22 /etc/postfix/aliases.lmdb
>
SELinux ain’t easy – there’s quite a steep learning curve.
As far as the system directories are concerned and, for user directories also, the main administrator tool is “restorecon” .
- What I’m finding here an Leap 16.0 is that, often the “-F” option is required to force the reset of the file contexts to the default values …
Which will probably solve a number of those alerts, but from the provided screenshot, they may also be missing the selinux-policy-targeted-gaming package.
No, I’m very much not kidding. You posted a screenshot with zero context, other than informing us that there were repeating, endless SELinux alerts regarding ld.so.cache
I have no idea what to do with that, or even where to start, with a post like that.
Yes selinux-policy-targeted-gaming is installed
Explain the use of restorecon and how it is used to fix SELinux errors.
Thanks. SELinux disabled until this error nonsense can be solved.
Which you just made impossible.
I’m almost tempted to kindly request that, you write “Please explain the use of … ” ![]()
As with most things related the UNIX® systems, including Linux, the explanation of what any particular command does is, documented in the “man” pages.
> man restorecon
>
restorecon - restore file(s) default SELinux security contexts. This program is primarily used to set the security context (extended attributes) on one or more files.
If, you have an Android mobile telephone, it’s been executing SELinux in enforcing mode for all domains since version 5.0 – Tuesday the 4th of November in the year 2014 …
I’ll be leaving it off. Other distros don’t use it and the PC runs with fewer problems.
Since phones are almost exclusively used as a dumb device for reading content, you may as well lock them up.
For a PC, which is used for actually creating and gaming, SELinux is a barrier to the user trying to actually use their PC.
Only to those that refuse to learn.
True. I’m also refusing to learn income tax accounting law or the mating behaviour of Tsetse flies. Some subjects are useful to know or job requirements. Other subjects are not.
Since most other distros do not burden with SELinux we can conclude that it’s mostly a fringe need case.
@8876523450 You can just run it in permissive mode to test, likewise if your system gets compromised?
It seems you need to relabel your filesystem,
