Hi think you can if you run
just _toggle_wayland in the terminalHdont have a deck with bazzite so cant test, but from my understanding looking at the scripts it should work like that
DI didn't see it when I typed
justi believe the _ at the beginning makes it hidden
Hit essentially adds a file to /etc/default which tells the steamos-session-select to use wayland instead of x11
Hfor context im running a custom image with the login screen active so the exit to desktop option takes me to the login screen (as the switcher kinda crashes on my weird desktop system) hence why i cant test
Dwhat are the pros and cons of using wayland kde on the deck
Hno idea sadly, all i can tell you is that all the development upstream is happening on wayland these days, there are some things wayland cant do that X11 can like global hotkeys, but because of the security model of wayland, global hotkeys is something the DE has to implement (and apparently KDE should support global hotkeys, just dont know how to set it up as im in the process of switching over myself)
Dwhy isnt wayland the default for the steam deck?
Hprobably because back when it launched wayland was missing more functionality you would have expected it to have and X11 was most likely choosen for compatibility so you would not get people having issues sharing their screen in discord or streaming with obs (i know there was some issues with this on wayland at some point with wayland, but just using it as an example)
Hthese days wayland will work for most people completely fine, while X11 is favored by people using nvidia due to well... nvidia being nvidia, especially if you have an older card
Hhere is a situation that makes wayland better for me
i have an amdgpu and an nvidia gpu
i tend to send the nvidia gpu into virtual machines so my host never uses it except on the first boot.
X11 may crash with the nouveau driver on some desktop environments because it might default to the nvidia card using the nouveau driver even though nothing is connected to it.
wayland will query the cards and go "oh ok, there is stuff connected to card2 which is using amdgpu, i guess this is the actual card used for displays" and then just work
so for me wayland is favorable going forward
i have an amdgpu and an nvidia gpu
i tend to send the nvidia gpu into virtual machines so my host never uses it except on the first boot.
X11 may crash with the nouveau driver on some desktop environments because it might default to the nvidia card using the nouveau driver even though nothing is connected to it.
wayland will query the cards and go "oh ok, there is stuff connected to card2 which is using amdgpu, i guess this is the actual card used for displays" and then just work
so for me wayland is favorable going forward
Dwould you recommend me doimg the toggle wayland thing?
Hyou can try it, the deck should support wayland fine from my knowledge, but kyle might know more since i believe he runs bazzite on the deck?
you can just run the command again to toggle wayland off
you can just run the command again to toggle wayland off
Dgood to know
Dwhy is it hidden?
Hthat i do not know 
EBecause it's not something we'd suggest a user do. X11 is used on Deck as Steam Input doesn't fully support it yet and even with extest, there's some off behavior. You're free to try it though
Dglad there is a way to revert back
KNot on a deck
Kyou won't be able to type special symbols or capital letters
Kmay be fixed in Fedora 39
KSteam Input has no support for Wayland
Di couldn't use the ( and ) symbols
Vwayland doesn't support any sort of remote desktop which is a huge dealbreaker for me personally
KGNOME just merged a change that finally kills X11
Knext release won't have a X11 session at all
Vlooks like i'll be rebasing to KDE on my deck then
Vso stupid of them to kill x11 when wayland hasn't reached feature parity
Vit's a shame because i really like wayland in terms of how much smoother and snappier it is compared to x
Vthat and it actually works with multi monitor/mixed refresh rate setups
KI think the intent is to force adoption
Vyeah that's what i figured
Kapplications like the remote desktop one you're using will never change if they don't have to
Kso now they have to
Vi really hope so
Keven things like xrandr have ports now
KGitHub
xrandrwlr-randr- GitHub - maxwellainatchi/gnome-randr-rust:
for Gnome/wayland, on distros that don't supportxrandrwlr-randr
Kwe ship this
Vit's about time someone makes a good remote desktop app for wayland that also works on android (which is what i need)
Vthat's still definitely gonna piss people off tho
Hgnome-remote-desktop works on wayland as a server using rdp (used this on chimeraos)
think krfb works on kde as vnc host on wayland, havent tested it yet though
think krfb works on kde as vnc host on wayland, havent tested it yet though
Vi tried krfb on my desktop dual boot and it didn't work
Viirc it would connect but on the client-side everything was just a black screen with a cursor
Hyeah that would be the xwayland desktop you got so yeah wont work
Hthere is probably a way to get rdp server working on kde too though just like it works on gnome-shell wayland
Hhowever gnome-remote-desktop is a module for the gnome settings so a bit hard to configure it on anything else using gui