On 04/10/2021 08:56, Adi Pircalabu wrote:
If you run "sealert -b" what does it have for "troubleshooting"?
I'm running KDE/F34 and not seeing any issues.
Didn't have setroubleshoot-server, so I went and installed it. "sealert -b" does nothing, or I don't know how to use it yet. Then I went and analyzed the audit log with "sealert -a /var/log/audit/audit.log" and here's the important bit:
type=AVC msg=audit(1633309984.892:327): avc: denied { audit_control } for pid=2387 comm="(systemd)" capability=30 scontext=system_u:system_r:init_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=capability permissive=1
$ ps auxww | egrep 2387 adi 2387 0.0 0.0 24080 16084 ? Ss 12:13 0:00 /usr/lib/systemd/systemd --user
So, looks like selinux prevents systemd to run as user adi. Now I need to figure out why all of a sudden.