Hey there
![]()
I’ve built Qtile (git) from source before - I was trying to come back to Qtile and from a fresh VM followed install instructions. (Installing through uv/pip & Git)
It seems I’ve got the required dependencies for Qtile - I also have seatd (from EPEL repo.) service running/enabled.
And these packages:
wayland-devel wayland-protocols-devel wayland-utils xorg-x11-server-Xwayland libwayland-server libwayland-client libwayland-cursor libwayland-egl wlroots
Interesting enough, Weston runs without any issue.
However, when I try to qtile start -b wayland I get an error advising Backend not built? I’m trying to decipher whether the issue is my compositor (Qtile) or something I haven’t set up correctly in user space. Read through some Github issues that are similar but not the same and double-checked for dependencies that resolved those.
Please see below:
< pip packages < dnf packagesIf someone could at least point me in the right direction; I’m having a hard-time even finding information/instructions about how to ensure Wayland backend is “built” correctly. From referencing Arch Wiki, FreeBSD, etc. it seems like I have all the components installed for Wayland protocol to function -
Probably just a skill issue - I’m sifting through Wayland docs; but most of those are aimed for devs. writing a compositor, etc.
By my understanding Fedora/CentOS/RHEL are defaulting to Wayland, why isn’t there any docs for setting up a minimal Wayland environment (outside of Gnome/KDE)?
Any advice/input would be appreciated! Thanks



