Am 29.12.23 um 16:36 schrieb Barry Scott:
> On 29 Dec 2023, at 11:12, Klaus-Peter Schrage via users
<users(a)lists.fedoraproject.org> wrote:
>
> Recently, I did an upgrade to F39 via dnf system-upgrade. For the first
> time in Fedora (I think I started around version 1), on booting into KDE
> I get a message saying "limited network connectivity", which means, my
> wired network is up but can't reach the outside world.
>
> The journals tell me that the name resolution is not working (see
> attached log). I didn't find out why it failed, but restarting
> systemd-resolved usually cures the problem. The problem that the service
> fails on startup still remains, but not on every boot. Sometimes, say in
> 10 % of bootings, the problem doesn't occur.
> If those things matter:
> - Desktop computer with KDE-Plasma (X11)
> - kernel 6.6.8-200.fc39.x86_64
> - NIC: Intel 82574L with kernel driver e1000e
>
> I have the faint idea thast there might be a race condition between
> services on startup,
> Any pointers to debug that further would be welcome.
> <systemd-resolved_error.log>--
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
Other then that you could try running /usr/lib/systemd/systemd-resolved as root
in debug mode and see if reports any errors.
systemctl stop systemd-resolved
SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-resolved
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.