I switched to NetworkManager on a basic Leap 15.4 Gnome install, but after some time I noticed that Wayland had been disabled (I have an AMD 6800 fwiw).
Testing further (Snapper is great), this sounds ridiculous but I’ve narrowed it down to merely disabling wicked causes Gnome to revert to x11. Whether NM is installed or enabled isn’t a factor.
Any ideas how I can switch to NM and why disabling wicked would stop Wayland working? Networking shouldn’t interfere with my desktop graphics, ideally. I can’t find any information relating to this problem but it’s odd.
My best guess is some additional service (dbus related?) that wicked starts, that NM doesn’t. I’m gonna try install YaSt and see if it helps at all with this…
Alright… relented and installed the default Gnome desktop this time instead of picking my own minimal packages and now can get Wayland working with NM. There must be something it’s doing that I’m not including, I’m really curious what but might never find out.
Anyway have now uninstalled about a million packages (it’s 2022 guys) and it’s still working so consider this fixed… somehow.
FWIW, NM and Wicked are not the only openSUSE network configuration options, though they are the only options manageable via YaST. All my installations are configured with static IPs, except for one laptop, and have been switched to systemd-networkd over the past year. Also none have ever attempted to open a Wayland session. Why network configuration should have anything to do with whether Wayland works is a mystery I’d like to hear a solution to myself. The way I understand NM is that until a GUI session is started, it doesn’t try to setup network at all, so you may need to discover how that works now that you have it working, and at next installation try configuring it to startup in similarly. Systemd starts network here whether or not X works or has been started.
Yes I agree, systemd-network is great. I’ve used that with window managers before and really liked it. With Gnome I remember it kinda makes the network settings UI a bit broken looking though and I’m ocd enough for that to bother me. I mean, that’s likely what’s caused my issue here though. I only wanted a minimum install but the installer is not really set up for that.
Anyway I know not everyone loves it, particularly Nvidia users but Wayland makes my desktop feel a lot smoother.
Why network configuration should have anything to do with whether Wayland works is a mystery I’d like to hear a solution to myself. The way I understand NM is that until a GUI session is started, it doesn’t try to setup network at all, so you may need to discover how that works now that you have it working, and at next installation try configuring it to startup in similarly. Systemd starts network here whether or not X works or has been started.