Thanks to this forum I recently switched to Sway, the process of which cascaded into running as much as possible on my machine through Wayland. I compiled everything I discovered and configured into this guide.
To give you a sample, the following are now running completely through Wayland on my machine: Sway itself, Waybar, the Wofi app launcher, browsers (and screen sharing), Emacs, all GTK apps, and most QT apps. I worked through some gotchas with Steam and Input Methods too. Overall things are much “snappier” and I’m quite happy with the result!
Please enjoy the guide, and do let me know if you notice any issues. Cheers!
I’m currently running KDE on X11, with Sway on Wayland in KDE and also Wayland on KDE. All installed on the same KDE installation. Just testing it out to see how it works, if i like it. What issues i run into with little i know.
Edit: Maybe eventually I’ll be able to follow this guide.
It’s likely already installed as a dependency of other packages. But you can just sudo pacman -S sway from anywhere. When you startsway, you’ll need to exit your X server and do it from your login shell.
I’m confused here. What desktop did you have installed? Or did you start from a base install without anything?
Edit: The reason I’m asking is because i installed sway in KDE using the Community edition github procedure. I just want to know how to follow your guide.
Yeah I think I still have a number of old X utilities lying around that I installed explicitly years ago. I should clean those up. The example in the post was from my own machine and wouldn’t be the same for everybody.
I don’t think so, no. sway becomes the Window Manager, so whatever desktop environment that was previously installed will remain unused (although all its settings would be intact, and you can still switch back to it if necessary).
else I would probably use it.
)