Did you delete you .cache directory after you ran the update? If that doesn’t help I dont know what I did, because when I rolled back it said the packages were already switched to opensuse even though that was not correct. This is a very strange problem indeed.
No I didn’t delete my ~/.cache directory. I didn’t think of that.
No worries, I rolled back again. I’ll wait a week or two before updating again. Hopefully it’ll be fixed by then. If not, I see X11 in my future haha.
My problem, was due to a missing library file, I diagnosed this switching to command line on SDDM login and starting kwin (Wayland) from systemd and viewing the status, then what I did is I ran the command it was using to start it in command line and that is how I came to my conclusion. I suspect that you may have a different issue, but if you are feeling adventurous, I would give it a try.
I’ve had the same problem. After the update yesterday i couldn’t log in to a Plasma-Wayland session from sddm.
Yesterday I rolled back, which worked, but the problem was back after updating again (I suspect the Mesa packages). My Mesa packages are from the main OSS repo (openSUSE, not packman).
So, I rolled back again.
Today, with snapshot 20241124 came Mesa 24.3
So, I updated again and this seems to have fixed the problem. Everything works after updating and rebooting.
1 Like
Just for the record, there’s talk on the bug ticket that the issue is fixed…
https://bugzilla.suse.com/show_bug.cgi?id=1233694
I ran an update today and I still just get a black screen when trying to use Wayland. So the issue is not fixed for me. (I rolled back again with snapper).
My Mesa packages are coming from packman. Perhaps I’ll try switch them to the OpenSuse repos as suggested.
1 Like
The bug has been solved.
Sorry for the wait, I couldn’t report earlier. So in my case it was fixed.
I didn’t do anything, just switched to X11 at login and waited for new updates.
Yes - the new mesa packages (from OpenSuse) have probably solved this.
I can log in normally again under Wayland and working without any problems.
Thanks for fixing the bug!!!
1 Like