lxqt-wayland-session(1)
π lxqt-wayland-session(1) β the LXQt Session Module glow-up β¨
okay bestie, so this is a section-1 manual page, and it's giving "the Wayland era of LXQt is HERE" π¦
πΈ NAME πΈ
lxqt-wayland-session β the Wayland session for LXQt. that's it, that's the whole name, and honestly? iconic.
β¨ DESCRIPTION β¨
so this module is the whole care package π¦ for the Wayland session of the LXQt desktop environment β it ships the files that session actually needs to exist. and on top of that, it flips on the Wayland settings page inside lxqt-config-session, so you can actually go configure your vibe. two jobs, both slayed π
π FILES π
here's the inventory, no skips, no "etc." cop-outs:
startlxqtwaylandβ the script that starts the compositor and sets your keyboard layout. it's the main character of this whole operation tbh πlxqt-qdbusβ a wrapper script forqdbuscommands when you're using them in keybindings. curious? runlxqt-qdbus --helpπ«Ά- Desktop entry file β it declares
startlxqtwaylandas the binary you need to start LXQt Wayland sessions. this is the one that gets sourced, e. g. by display managers. so your login screen knows what to do π₯ - Basic configuration files β for the supported compositors, wherever they're needed. the roster is: Hyprland, kwin_wayland, labwc, niri, river, sway, and wayfire. seven whole queens π
π UNSUPPORTED COMPOSITORS π
plot twist: literally any compositor can be launched by startlxqtwayland. yes, even yours. no gatekeeping π
BUT β and this is the part where you pay attention, bestie β if you want the LXQt session to actually start and exit properly, you have to add this line to that compositor's autostart configuration:
lxqt-session && <exit_compositor_command>
that's the glue. without it, the session's not gonna know how to leave the party gracefully π
π§ NOTES π§
okay so some of the lxqt-configuration tools are, as of right now, not Wayland-supporting. those settings have to be configured in the compositor's own configuration instead. the list:
lxqt-globalkeyslxqt-config-monitorβ though fair's fair,kwin_waylandis mostly supported πlxqt-config-input
and then there's lxqt-panel, which has its own little limitations, bestie:
- Workspace support in
lxqt-panel's taskbar plugin? only supported inkwin_waylandand Wayfire. that's the whole list π - Workspace switcher? supported in
kwin_wayland, Wayfire, and in compositors that support theext-workspace-v1protocol β like niri and labwc. slay for the protocol girlies β¨ - and
kbindicatorplus theqeyesplugin are currently not supported under Wayland at all. rip to them specifically π
π₯ REPORTING BUGS π₯
found a bug? do NOT suffer in silence, tell the devs, they want to know fr fr:
https://github.com/lxqt/lxqt-wayland-session/issues
π SEE ALSO π
go read these next, they're all connected, iykyk:
and that's a wrap on lxqt-wayland-session(1), brought to you by LXQt 2.3.0, dated November 2025. thanks for reading the whole thing, you're literally the best, mwah π«Άπ
π¦ where this page comes from
- arch rolling: lxqt-wayland-session 0.4.1-1 Β· LGPL-2.1-only AND MIT AND GPL-2.0-only AND GPL-3.0-only AND GPL-3.0-or-later AND BSD-3-Clause AND CC-BY-SA-4.0
- fedora 43: lxqt-wayland-session 0.4.0-1.fc43 Β· LGPL-2.1-only AND GPL-3.0-only AND MIT AND GPL-2.0-only AND BSD-3-Clause
- fedora 44: lxqt-wayland-session 0.3.2-1.fc44 Β· LGPL-2.1-only AND GPL-3.0-only AND MIT AND GPL-2.0-only AND BSD-3-Clause
- fedora 44: lxqt-wayland-session 0.4.1-1.fc44 Β· LGPL-2.1-only AND GPL-3.0-only AND MIT AND GPL-2.0-only AND BSD-3-Clause
- nixos 26.05: lxqt-wayland-session 0.4.0
- nixpkgs unstable: lxqt-wayland-session 0.4.1
- ubuntu resolute: lxqt-wayland-session 0.3.1-0ubuntu1 Β· LGPL-2.1-only
- ubuntu stonking: lxqt-wayland-session 0.4.1-0ubuntu1 Β· LGPL-2.1-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms