<JoshuaPeisach[m]>
Has anyone else on questing experienced this thing where sometimes Plymouth just never exits, and sometimes you need to reboot and spam a bunch of keys to switch tty or something until you get your display manager to launch correctly?
<JoshuaPeisach[m]>
The rest of the system seems to finish booting but Plymouth never exits
_whitelogger has joined #ubuntu-asahi
_whitelogger has joined #ubuntu-asahi
<tobhe[m]>
weird... no I haven't seen that but I usually have quiet and splash disabled so maybe that's why
<tobhe[m]>
I'd be surprised though if this is actually a plymouth problem
<tobhe[m]>
I did see similar behavior before when networkd caused a weird dependency loop because I had a config to set up a dummy interface
Son_Goku has quit [resistance.oftc.net reflection.oftc.net]
popey has quit [resistance.oftc.net reflection.oftc.net]
Son_Goku has joined #ubuntu-asahi
popey has joined #ubuntu-asahi
Son_Goku has quit [Ping timeout: 480 seconds]
Son_Goku has joined #ubuntu-asahi
Son_Goku has quit [resistance.oftc.net reflection.oftc.net]
popey has quit [resistance.oftc.net reflection.oftc.net]
Son_Goku has joined #ubuntu-asahi
popey has joined #ubuntu-asahi
Son_Goku has quit [Ping timeout: 480 seconds]
Son_Goku has joined #ubuntu-asahi
popey_ has joined #ubuntu-asahi
popey has quit [resistance.oftc.net reflection.oftc.net]