On Monday, June 8, 2020 12:41:03 PM EDT R. G. Newbury wrote: > On 2020-06-07 4:46 p.m., From: Samuel Sieb <samuel@xxxxxxxx> wrote: > >On 6/7/20 10:31 AM, R. G. Newbury wrote: > >> It was apparently something to do with selinux. I usually disable > >> selinux as the first or second thing I do to a new install. I > >> forgot to do that. > > That should never be necessary. > > Well obviously, it WAS necessary in order to get rid of an > objectionable and annoying message, which was otherwise impossible > to get rid of. I imagine that he meant that restoring some file context that was modified incorrectly by the root user would be a better way to solve the problem, thus disabling was not necessary. Obviously I cannot know what the problem really is, but it has been many years since I even came close to disabling selinux. It is hard to belive that a brand new system was created with an invalid file context. Those kinds of bugs don't get past updates-testing these days. So whatever was going on as the root user is almost certainly to blame. The restorecon(8) command is a handy command to get to know. Running it with the -nv option against the files and directories that were manipulated by root will probably reveal the exact error. -- Garry T. Williams _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
