On Fri, Dec 29, 2023 at 11:40 AM Klaus-Peter Schrage via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Am 29.12.23 um 16:36 schrieb Barry Scott: > >> On 29 Dec 2023, at 11:12, Klaus-Peter Schrage via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > >> [...] > > That is very odd. | have seen a number of people seeing odd things failing > > as a result of selinux labelling errors. You could try to the auto relabelling and > > see if that fixes it. > > > > touch /.autorelabel > > reboot > > [...] > > > Thanks, Barry, you were right in suspecting selinux: After > autorelabelling, I booted the system for several times without the > problem ever reoccurring. So for me, there is sufficient statistical > evidence that my problem is solved. But an issue remains: Why got my > system mal-labelled? I didn't do many things to it after the upgrade, > and shouldn't be labelling be part of the system-upgrade process? > But thanks again for your help. There are several post-upgrade steps that may be useful to you: <https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/#sect-optional-post-upgrade-tasks> and <https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/#sect-resolving-post-upgrade-issues>. There are usually lots of dangling symlinks, so you may want to clean up the dangling links. Since relabeling is under the section "Resolving post-upgrade issues," I'm guessing relabeling does not occur as part of the upgrade process. Jeff -- _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue