Previously there was a helpful ujust command to toggle wayland (_toggle_wayland) which can be used to switch to X11 from the new default, Wayland. Said command seems to no longer exist.
Saw a separate discussion on here of someone wanting to go back to X11, and the solution provided was on how to install X11 which I assume no longer comes preinstalled even for old installation which had X11?
Regardless, I followed the solution to install it by:
rpm-ostree install plasma-workspace-x11
Now, on my plasma-deck image running on an AMD-based HTPC, it does boot right into Game mode which as what I expect, but how do I make it so that when I get into Desktop mode, it runs on X11 instead of Wayland?
I need this as I have some apps I rely on that only works on X11.
Did you manage to work it out? im trying to do it as well having major issues with Wayland not clearing memory for some reason and just crashing the system. These forums though seem to be a bit dead hard to get an answer, starting to consider switching to a different distro tbh.
How to fix the issue with Wayland, I have another post on here and github where I explained my issue. Basically Wayland decides to hog all the memory and not clearing it, which eventually leads to memory and swap hitting 100% and full computer freeze. I’m fairly new to linux so even this took me ages to figure out, initially had no idea why computer would freeze for no reason forcing me to hold power button to restart. Narrowed it down now to an issue with wayland. If switching to X11 is not an option what else can I do?
yeah I’ve had btop running on 2nd monitor and I’ve noticed its always the “kwin_wayland” that starts off with only using few hundred MB’s of memory then for whatever reason (I haven’t been able to work out what triggers it) starts going up in memory usage and doesn’t clear any. Last night I had it go up to 20gigs. So basically a memory leak is happening. The speed at which it takes to keep going up and up varies, could take a day or few hours. Sometimes it doesn’t go up just stays at few hundred MB’s all day, then all of sudden decides to skyrocket.
Tried the command you suggested, yeah its showing “kwin_wayland” is currently using 40% of memory, everything else underneath is less than 2% each.
I’ve posted another topic earlier where I was asking for help with Bazzite always crashing my computer sometimes after just few hours of use or couple days. Initially had no idea what was causing full freeze but managed to narrow it down now so making new topic so its easier to follow. Basically its to do with memory consumption and its always “kwin_wayland” thats using up more and more memory till eventually both RAM and SWAP is at 100% and comp freezes completely. Ones frozen only way to fix is to hold power button do forced restart.
I have now merged both treads into one. Please don’t double post the issue, because that is difficult to follow and all kind of duplication discussion appears. Also no need to ping specific user for help… users read the forum and if they know they will answer the question.
From issue description it looks to me nothing Bazzite special, most probably some upstream issue that Bazzite project can’t do much about until some fixes are available upstream and Bazzite ships them.
Just quick note, Bazzite project is not the project who develops software, it is a project who distributes the software from multiple sources. If there is an issue in distribution of the software then Bazzite is to fix, if there is an issue in how software works itself, then it must be fixed upstream somewhere.
In proprietary world, you “poke” the multi-million vendor and vendor fix the issue. Just like waiting at rabbit entry hole, make noise and wait. In open-source world there is no single vendor. There are multiple actors each one doing its own little bit and you need to dig through rabbit hole to get to the right actor. In this case probably some forum from upstream is more appropriate to get help.
