On 8/28/24 6:32 AM, Darin Perusich via openSUSE Users wrote:
I just updated a VM from Tumbleweed 20240808-0 -> 20240826-0 and I'm seeing similar and/or worse behavior. After the dist-upgrade, during initial boot after grub boots the system I get a blank screen, I do not see any of the boot messages and I never see the console sign-in prompt. I then need to reset power, and on the grub screen I select advanced options and select the previous kernel (6.10.3-1-default) and the system boots successfully, but the network (wicked) fails to start during boot with various message as I've listed below. I can manually start networking (systemctl start network), but that is clearly a workaround.
I'm going to post this to the opensuse-factory list, but wanted to follow-up on this thread since the issue is continuing with Tumblewewed 20240826-0.
wicked[1227]: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds: wicked[1227]: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable wicked[1227]: Couldn't refresh list of active network interfaces systemd[1]: wicked.service: Failed with result 'exit-code'. systemd[1]: Failed to start wicked managed network interfaces.
Already reported as bug and they are working on a solution, see: On 8/27/24 8:39 AM, Simon Becherer wrote:
.... snip ...... That for example has been reported already as https://bugzilla.opensuse.org/show_bug.cgi?id=1229745
wicked is wrongly starting before dbus-broker and results in not having a network configured.
After the boot, you can "systemctl restart network" or apply the patch which is proposed in https://github.com/openSUSE/wicked/pull/1032 locally to get it faster,
The bug report contains another work-around as well. You can also read through the thread from yesterday: "Tumbleweed - dracut update on dup tonight failed to start WiFi on reboot?" -- David C. Rankin, J.D.,P.E.