On 5/11/21 2:05 PM, Eddie O'Connor wrote:
I'm wondering?....the ugrade/patches fixed it?....would it have been fixed "sooner" if you had run the dnf upgrade sooner? or was it the "latest" upgrade/patch that did it?...
On Tue, May 11, 2021, 12:35 PM home user <mattisonw@comcast.net mailto:mattisonw@comcast.net> wrote:
The SELinux alerts stopped on Thursday April 29. That would have been when I did weekly patches ("dnf upgrade"). I also did weekly patches on Thursday, May 06. Since the alerts did not start showing up again, I'm now confident they're really fixed. I've added a comment to "https://bugzilla.redhat.com/show_bug.cgi?id=1951668 <https://bugzilla.redhat.com/show_bug.cgi?id=1951668>" saying what I said in the preceding paragraph of this post. I don't know what in the patches fixed things, but this workstation is fixed. I thank everyone who tried help. I've marked this thread SOLVED. Bill.
1. before April 08, f32: no SELinux alerts. 2. April 08: upgrade from f32 to f33 (dnf system-upgrade [etc]). 3. April 08, f33: patch (dnf upgrade); dnf reported "nothing to do". 4. f33: SELinux alerts occurring. 5. April 15, f33: patch (dnf upgrade). 6. f33: SELinux alerts continue. 7. April 22, f33: patch (dnf upgrade). 8. SELinux alerts continue. 9. April 29, f33: patch (dnf upgrade). 10. f33: no more SELinux alerts. 11. May 06, f33: patch (dnf upgrade). 12. f33: Still no more SELinux alerts. Reasonable, probable, but not certain conclusions: a. The April 08 upgrade (step 2 above) introduced the problems. b. Whatever fixed the problems in f33 was released sometime between April 22 and April 29. c. Something in my April 29 f33 patching (step 9 above) fixed the problems. That's as much of an answer as I can give. This all applies to both the SELinux problems and what was addressed in my "System Failure?" thread.