LXQt 2.5 completes its break from LXDE on Qt 6.10
On November 5, 2026, LXQt 2.5 drops menu-cache, its last dependency inherited from LXDE, moves to Qt 6.10, and sharpens QTerminal and PCManFM-Qt. The lightweight desktop completes thirteen years of independence, but its Wayland session remains the question that will decide its future.
November 5, 2026. LXQt 2.5 ships with Qt 6.10 support. November 5, 2026. The release drops menu-cache, the last dependency inherited from LXDE, replaced by a desktop menu built into LibFM-Qt. November 5, 2026. The team flags an X11 regression: the removal of X11 support in libkscreen 6.8 breaks display configuration under X11. The whole thing fits in one sentence: the lightweight desktop completes thirteen years of emancipation from LXDE, but its future now hinges on Wayland.
For an administrator recycling old machines or wanting a lean, fast desktop, LXQt is not nostalgia. It is one of the last environments that runs in a few hundred megabytes of memory, and what happens to it says something about the state of the entire lightweight ecosystem.
menu-cache disappears: the end of a thirteen-year inheritance
LXQt was born in 2013 from the merger of LXDE-Qt — the Qt port of LXDE started by Hong Jen Yee — and Razor-qt. Since then the project has methodically replaced every component inherited from LXDE, the GTK desktop founded in 2006. With 2.5, the last piece falls: menu-cache, the library that built the application menu.
The replacement is functional, not cosmetic. The menu is now handled by LibFM-Qt, the file library behind PCManFM-Qt, which “performs the same tasks more efficiently and faster”, according to the team. Concretely, that means one fewer dependency to compile, more consistent behavior between the menu and the file manager, and one more step toward an all-Qt codebase.
The emancipation has image value as much as engineering value. For years, LXQt was described as “the successor to LXDE”. As of 2.5, that label has no technical basis: there is no LXDE component left in the stack.
A terminal and a file manager that gain precision
The rest of the release is polish rather than rupture, but it touches the two tools people open most.
QTerminal gains features found elsewhere.
- OSC-8 hyperlinks are supported, making URLs emitted by tools that use them clickable.
- An optional visual bell,
Shift+clickselection for highlighting ranges, and maximizing a single sub-terminal. - A notification when output stops in a minimized window, and a warning when a process exits unsuccessfully.
- Terminal history saving, and substantially improved D-Bus support.
PCManFM-Qt, for its part, adds optional incremental search — matching files appear as you type — with a stop button in the status bar to interrupt a long search without losing results already collected. An option to disable wallpaper caching preserves the original image quality, and a fix removes ghost entries from the directory tree.
The panel gets its own fixes: the network monitor now respects the configured icon size, the custom command plugin gains a minimum width, and the backlight plugin shows brightness in its tooltip.
The Wayland work, exposed by the X11 regression
The most instructive part of 2.5 is not a new feature but a known issue. The removal of X11 support in libkscreen 6.8 — a KDE library — breaks LXQt’s display configuration under X11. The team plans to restore compatibility by reimplementing the necessary X11 functions, with a point release to follow.
That incident is a tell. LXQt remains fundamentally an X11 desktop: its Wayland session, driven by the labwc compositor, is progressing but not yet complete. Yet the Qt and KDE ecosystem — on which LXQt depends for libraries like libkscreen — is steadily disengaging from X11. The lightweight desktop finds itself in a delicate spot: dependent on a stack that is abandoning its historical foundation, without having finished its own transition.
The dynamic is familiar to every small project orbiting Qt. Wayland is the future — distributions ship it as the default session — but a complete Wayland session takes deep work that LXQt is doing with limited means, leaning on labwc for composition.
What it changes for a fleet of lightweight machines
LXQt occupies a precise niche: aging hardware, VDI, education fleets, servers with a screen attached. Where GNOME and KDE Plasma consume several gigabytes, LXQt boots in a pocket and leaves the memory to applications.
Version 2.5 reinforces that position without transforming it. Qt 6.10 support keeps the stack modern, the disappearance of menu-cache lowers maintenance complexity, and the QTerminal and PCManFM-Qt polish makes daily use more comfortable. But the core risk — the Wayland transition — is not settled by this release.
For an administrator, the question is not “should we stay on LXQt?” but “on which graphical foundation?”. As long as the Wayland session is incomplete, a fleet on LXQt remains largely on X11, with two consequences: X11 security fixes arriving at a slowing pace, and growing dependence on Qt/KDE libraries that no longer invest in X11.
Verdict
LXQt 2.5 is a good maintenance release: it closes the LXDE inheritance, keeps the stack current on Qt 6.10, and improves the everyday tools. But it does not settle the question that matters.
If you run LXQt on a stable X11 fleet with no critical security exposure, update with confidence: the stack cleanup is real, and the libkscreen regression affects only display configuration, not desktop stability. If you are planning a durable fleet, watch the Wayland session with labwc as the true leading indicator: it, not the pace of X11 releases, will decide whether the lightweight desktop remains a credible option two years from now. The trap is not underestimating LXQt — it is assuming it is sheltered from a Wayland transition the rest of the ecosystem has already committed to.