X11 Compositor no longer works after switching to Wayland
Switched to try out Wayland and had some flickering in Steam, so I went back to X11 and the compositor refuses to work now. I am on Nvidia - Bazzite Desktop image. Alt+Shift+F12 does nothing
Solution:Jump to solution
try mash shift while you boot and select the other image. it will have (ostree:1) at the end of it. Boot the 40.20240514 image.
50 Replies
Have you tried restarting the machine?
Yes, I shutdown completely as well.
Does it fail to log in and you cannot get to the desktop at all?
No, I can login perfectly
I checked compositor and I see this message in there
Re-enable doesn't do anything
The last thing that happened was BoxBuddy updated.
and if you ignore it, do your games still work?
Well, Steam loads but it's blank so I cannot see anything
try switch to wayland re-enable opengl detection, then log out and switch back to x11
alright
No idea if that will help
I'm in Wayland now and I don't see opengl
Then I guess thats not an option. Kyle, HikariKnight or one of the others might have some ideas. Or maybe ask in the general Bazzite chat
Should I tag them? I don't want to bother others.
Rather don't tag them but just post your query in the https://discord.com/channels/1072614816579063828/1087140957096517672 chat
Okay
If only Steam didn't flicker or artifact on Wayland, I could just stay there
It actually feels much better otherwise
Tried rebooting and upon logging into X11 the screen was mostly black except the taskbar
you might find that a upgrade of bazzite broke it
When I opened some windows they would permanently get stuck in the background of whatever it was that I was doing.
rpm-ostree statusSolution
try mash shift while you boot and select the other image. it will have (ostree:1) at the end of it. Boot the 40.20240514 image.
Will all my storage remain unaffected?
Here is someone with your issue using Fedora https://discussion.fedoraproject.org/t/plasma-6-x11-compositor-seems-to-no-longer-work/117261
Fedora Discussion
Plasma 6 X11 - compositor seems to no longer work?
Currently I’ve been using Fedora KDE since April. Upgrade from 39 to 40 went smoothly, all I needed to do was reinstall X11, because I’m using Nvidia GPU. The system was working fine until yesterday when I started having issues with it. What may have triggered it was me uninstalling a Windows application in Lutris, the first odd occurrence was t...
They logged this yesterday
Ohhh
interesting
Ok let me mash shift on boot to get the other image going
yup, your home folder stays intact
AYYY it fixed it!
Thanks dude!
So basically I just don't update until a fix is pushed or something?
Do the following
sudo ostree admin pin 1 then run rpm-ostree status I just want to check that your image is pinned
This will let you update... but you'll always be able to return to your current version
So is there a way to know when it is safe to go back or what not ?
pretty much
ujust update and see if you have an issue. If not boot up the working image from 20240514
That's the benefit of Bazzite. you can get back to a working system
The Bazzite team pretty much has a new update daily, so hopefully this is fixed soonObviously I am not going to do this right now but if I did
ujust update now, it would update to the 5/17 image correct?Yup
Awesome, appreciate your help again
but your pinned image will never be changed. you can unpin it with
sudo ostree admin pin 1 -u or whatever the index is at the time. But only do what when you have a working updatewhat does
-u at the end do?
@wolfyreloadthe -u stands for unpin
you'd only want to unpin once you know that the update is working for you
Thanks 😃
You are welcome :). Now get back to gaming 🤣
Somehow broke again after a reboot
I had to mash shift again to use image 1 again as the pin didn't work
Pinned images doesn't make only that image bootable, it makes that image never get removed with an update. Try the following
* boot pinned image
* remove pending deployment with
rpm-ostree cleanup -p this will make only one boot option available
* now turn off autoupdates with ujust toggle-updates Disable
* you can update manually with ujust update when you want to test if the update fixed the issue
This will let you ignore the updates for a while so you don't have to remember to boot the old image all the time.Thanks, I will give this a try.
Same thing is happening
what do you get when you type
rpm-ostree status?Ok and if you run
rpm-ostree cleanup -p does it remove the new update? and you are just left with your current deployment?
Then if you disable the autoupdates with ujust toggle-updates Disable then it's not going to update 20 minutes after you start the pcwhat does
rpm-ostree status show now?good, now disable the auto updates with
ujust toggle-updates Disable and when you restart you'll only have the pinned image availableAnd I can just re enable it in the future with
Enable at the end then?yeah once you have a working update yeah but I actually prefer the manual updates with
ujust update and I update once a weekEverything works, thanks!
+1 for this, having the same on a new install today, suspect it's something upstream in fedora breaking it, same steps, nowt. Only problem with X11 is this broken OpenGL Compositing on i guess nvidia.. I'll live with it until a fix passes upstream. - do the Ublue devs monitor these posts?
Actually, looks like the guys in fedora have already pushed a fix into stable, bet it will be with us in a couple of days... https://bodhi.fedoraproject.org/updates/FEDORA-2024-06d286a7c5