On Nov 10, 2024, at 03:04, jarmo <oh1mrr@xxxxxx> wrote: > > I see no network, after starting computer, which I do very seldom, > only when there comes kernel update. > So network does not start at all and when doing journal query I get > this, what I sent before... > > journalctl -xeu systemd-resolved.service > ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > ░░ > ░░ An ExecStart= process belonging to unit systemd-resolved.service has exited. > ░░ > ░░ The process' exit code is 'exited' and its exit status is 1. > marras 08 07:52:25 oh1mrr.ampr.org systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. > ░░ Subject: Unit failed > ░░ Defined-By: systemd > ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel > … Sadly, your excerpt from the journal starts *just* after anything useful might have been recorded. It’s just systemd noise about the service not failing and how it isn’t restarting it. But I can’t comment further because apparently you don’t “speak nerd” and it would be pointless. -- Jonathan Billings -- _______________________________________________ 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
