On Monday, 5 August 2024 17:30:56 BST Daniel Frey wrote: > Is it just me or is wayland nowhere near primetime? > > I did a switchover to systemd/wayland some time ago and it seemed to > solve some problems I had. > > The problem is it also came with so many more issues than it fixed: > > 1. Logins don't work reliably. I use KDE/SDDM and when logging in it > appears to start on a new VT and sometime it doesn't start. Or it will > start the new VT and fail to switch to it, leaving a text console and a > blinking cursor. This didn't happen when using X11.
I've come across such symptoms on more recent SDDM versions. SDDM would not launch, or would not launch fully on boot. Nothing meaningful in the logs. Strangely, it would start fine if I were to restart display-manager, but never on boot. This would only happen only on a ryzen PC, but not on other older and slower PCs. After a lot of testing I discovered the faster ryzen would finish starting all the openrc services including display-manager, *before* haveged had a chance to generate enough entropy. Hence SDDM failed to start. I have no TPM chip on this MoBo, so I don't know if it would help accelerate haveged or not. The solution was to add in /etc/rc.conf: rc_display_manager_after="local" to allow enough time for entropy generation by haveged before SDDM tries to launch. > 2. Sometimes video hardware acceleration just doesn't work. Now I do > have a discrete nVidia card with the proprietary driver, but I switched > to nouveau and it didn't work either. Again, not an issue in X11. > > I have a nVidia RTX 3070 Ti. >From what has already been posted this seems like a Nvidia driver issue. Graphics acceleration works fine on AMD (both integrated and discrete graphics) with amdgpu or radeon drivers, depending on the age of the graphics cards. > 3. I sleep/resume a lot, wayland seems to be quite buggy on resume. As > in, the other three issues listed here are far more likely to occur > after a sleep/resume, but they do happen even after rebooting and being > on the PC most of the day. There was a glitch a few months ago affecting one PC with an AMD APU here and a dual-monitor setup. The PC would sleep/resume OK, but some time later it would crash kwin if firefox was used heavily and was being dragged between the two monitors. Evidently a graphics driver issue on this integrated graphics PC. Following some recent xorg/mesa updates and enabling hardware acceleration on firefox has fixed this. All other AMD graphics systems have always been able to sleep/resume reliably. Again on this PC only, changing from the desktop to a console with Ctrl+Alt+F1 and back again would arrive at a distorted/full of tearing desktop. This may not happen the first time, but always happens after a couple of attempts. The workaround is to switch first to the VT where the SDDM was launched from and then to the VT where the desktop is running. > 4. This is the big one, the panel in KDE hangs intermittently. The clock > will freeze and the entire panel is unresponsive (but weirdly enough, > KDE doesn't realize it's not responding.) I've tried killing and > restarting the process and that doesn't always fix it either as it > becomes disconnected with any open processes and it's not possible to > resolve. Either have to logout or reboot. Sounds like a kwin crash, which brings Plasma down. It can happen, although quite rare here. Check your ~/.local/share/sddm/wayland-session.log and or syslog. I haven't found a fix, perhaps restarting kwin could/would do it? I prefer to shut down the individual application windows still running and then restart display manager to get a new, clean, Plasma session, without anything hanging in the background. > I've switched back to X11 for now and have been using it for over a > week. I managed to figure out how to set up multimonitor for now (both > on the KDE desktop and in SDDM) and I haven't had any of these issues. > For the record, I typically use the computer a few times a day during > the week and sleep/resume, and longer on weekends. > > After much googling and experimenting, I can't seem to make these issues > go away... which got me wondering if someone else has experienced any of > these. > > I have done hardware tests (load testing, RAM tests, etc) - all are clear. > > -Dan I think your issues are caused by how well your graphics can work with Wayland. I have no experience with Nvidia to know if this is fixable through some configuration tweaks. Given the direction of travel is toward Wayland, I would think Nvidia will eventually adjust their code to make it work with Wayland, or nouveau may get there first.
signature.asc
Description: This is a digitally signed message part.
