In reply to @elvishjerricco:matrix.org
For some reason my microphone ends up sounding extremely bad if I enable pipewire. I have spent exactly zero time investigating this

Jan Tojnar: Ok, we've made a lot of progress understanding this bug. Here's the short version. It's not specific to systemd-initrd, and it's not specific to plymouth. Those things just seem to make a race condition more likely to trigger the problem.

The problem is simply that there is no reason that GDM wouldn't put GNOME on tty1. The only thing that would prevent it would be getty@tty1.service starting earlier than GNOME, but in the auto-login case that's a race condition. So the result is that when getty@tty1.service does start, GNOME crashes. And it gets worse. Because we still have multi-user.target: Wants=network-online.target, and because getty@.service has Type=idle, that means that you get this issue, where logging in within 5 seconds while networking is still connecting results in the same crash.

So, I think the solution is to build GDM with -Dinitial-vt=1. We don't do this now because switch-to-configuration is rather clumsy in how it starts new units. So it sees that getty@tty1.service isn't started and includes it in the list of things to start. Then GDM's display-manger.service: Conflicts=getty@tty${initialVT}.service results in display-manager.service getting killed.

But we think we can fix this by being smarter about starting new units. If switch-to-configuration's start logic is changed to simply doing systemctl start default.target, it will correctly consider the Conflicts= directive, and the unit with the directive will win, meaning getty@tty1.service won't be started and display-manager.service won't be stopped.

In reply to @philiptaron:matrix.org
🚀 GNOME 47 RC is out 🚀

In reply to @ashvith:matrix.org
This also looks like a simple fix - might have to introduce this ini file and then set browser.gnome-search-provider.enabled to true in about:config (I believe?)