lxqt-wayland-session(1)

πŸ“¦
version 0.4.1 Β· 2 versions
, in arch rolling, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu resolute, ubuntu stonking

πŸ’– 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 for qdbus commands when you're using them in keybindings. curious? run lxqt-qdbus --help 🫢
  • Desktop entry file β€” it declares startlxqtwayland as 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-globalkeys
  • lxqt-config-monitor β€” though fair's fair, kwin_wayland is 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 in kwin_wayland and Wayfire. that's the whole list πŸ“
  • Workspace switcher? supported in kwin_wayland, Wayfire, and in compositors that support the ext-workspace-v1 protocol β€” like niri and labwc. slay for the protocol girlies ✨
  • and kbindicator plus the qeyes plugin 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