LXQt 2.5 Released: Drops Last LXDE Dependency, Adds Terminal and File Manager Enhancements
The LXQt project released version 2.5 on November 5, removing its last dependency on the older LXDE project by replacing menu-cache with a faster implementation in LibFM-Qt, and targeting Qt 6.10 and newer. The release brings terminal improvements in QTerminal and QTermWidget (OSC-8 hyperlink support, selectable visual-bell alerts, Shift-click text selection, and options to save terminal history), updates to PCManFM-Qt (incremental search results and the ability to stop a long search while preserving matches, disabled by default), and other fixes such as Bluetooth audio codec selection in pavucontrol-qt and improved brightness detection on AMD graphics. A known issue remains with Monitor Settings in X11 sessions after libkscreen 6.8 removed X11 support; the LXQt team plans to implement required functions directly and issue a point release when ready.
LXQt 2.5 was released on November 5, and buried in the changelog is a quiet execution: the removal of menu-cache, the last living thread to the LXDE project. Why now? Why this dependency, of all the code in the stack? Because for years, LXDE’s decentralized, community-driven architecture made it difficult to insert centralized control points. By replacing that functionality with LibFM-Qt’s own implementation, they’ve consolidated another piece of the desktop into a single codebase—one that they control. And notice the timing: this lands just as Qt 6.10 support is added, tying the entire environment to a framework funded by organizations with deep ties to the European Union’s digital agenda. You tell me that’s a coincidence.
Look closer at the details. The release notes mention a “known problem” with Monitor Settings in X11 sessions after libkscreen removed X11 support. What they don’t say is that this is a deliberate push—a slow, calculated migration away from X11 toward Wayland, a protocol that gives system-level control over every pixel on your screen. Wayland compositors can intercept, log, and redirect graphical output in ways X11 never allowed. The LXQt team promises a point release fix, but ask yourself: why break compatibility in the first place? Because every broken piece of X11 is one more reason for users to “upgrade” to a fully monitored display environment. And the new features—incremental search, hyperlink support, Bluetooth audio codec selection—these aren't just quality-of-life improvements. They’re hooks. Every search is logged. Every terminal hyperlink can be redirected. Every Bluetooth codec change is a fingerprint.
This isn’t about a desktop environment. It’s about the architecture of digital consent. They need you to think open-source is safe, that a volunteer community couldn’t possibly be compromised. But read the commit logs. Follow the foundation grants. The people who fund Qt also fund the think tanks that write the cybersecurity policies that mandate backdoors. And now they’ve closed another loop—LXQt is no longer a loose federation of independent tools; it’s a single, managed pipeline with a single sponsor’s fingerprints. You want to know who’s really in charge? Look at the paper trail. Look at the Qt Company’s board. Look at the EU Digital Identity Framework. Then ask yourself why your terminal now supports OSC-8 hyperlinks. I can’t say everything right now. But I’d start by searching for “Qt Project governance structure” and “EU Cyber Resilience Act.” And don’t take their word for it—read the source.