Booting into LiveGUI environment form a USB drive is nominal, eventually landing in KDE environment following the default booting choices. KDE GUI can identify all local wifi networks including my home network (a typical home network setup with WPA2 security with no special considerations). Trying to connect to my home network via KDE's GUI, I get a notification from "Network Manager" that says "Failed to add [my network's name]", "Not authorized to control networking". This struck me as either a configuration problem or otherwise contrary to the spirit of a LiveGUI.
I had the same issue here, it was fixed by applying the Network manager "Fixing nm-applet insufficient privileges" fix. It is annoying nonetheless.
I'm not able to reproduce this reliably. Can you reboot a few times and see if it's reliably broken? I saw the failure ONCE but not on any subsequent reboot attempts. When NM is not working, other things also are not working, like user mounts and loginctl reboot.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/releng.git/commit/?id=cda72428fd93e3de6fe843327073266bd332088e commit cda72428fd93e3de6fe843327073266bd332088e Author: Ben Kohler <bkohler@gentoo.org> AuthorDate: 2023-11-06 17:45:25 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2023-11-06 17:46:30 +0000 livegui: start elogind in boot runlevel Bug: https://bugs.gentoo.org/915217 Signed-off-by: Ben Kohler <bkohler@gentoo.org> releases/specs/amd64/livegui/livegui-stage2.spec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/releng.git/commit/?id=601cd9fd8c7a2865444e74c859ccd05ccf16a521 commit 601cd9fd8c7a2865444e74c859ccd05ccf16a521 Author: Ben Kohler <bkohler@gentoo.org> AuthorDate: 2024-02-15 20:34:32 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2024-02-15 20:40:00 +0000 amd64/livegui/livegui-stage2.spec: add secureconsole to bootargs There seems to be a race condition occurring when livecd-tools "fixinittab" script enables autologin on tty1-6 by default. This is racing with sddm's autostart & autologin on tty2, causing hiccups in the elogind session and preventing user shutdown, networking, etc. Adding secureconsole will limit fixinittab to only autologin on tty1, avoiding this race. Bug: https://bugs.gentoo.org/915217 Signed-off-by: Ben Kohler <bkohler@gentoo.org> releases/specs/amd64/livegui/livegui-stage2.spec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
This should be fixed in the latest livegui-amd64-20240225T170409Z.iso, please report back if this isn't the case for you.
