LXQt 2.5 Release Completes Separation from LXDE, Requires Qt 6.10+

The LXQt project's version 2.5 release marks a significant milestone by removing the last dependency on LXDE (menu-cache), fully separating the lightweight Linux desktop from its predecessor, while also requiring Qt 6.10 or newer for compilation. This update introduces enhanced controls to the QTerminal terminal application—including OSC-8 hyperlink support, a visual bell, alerts for output stops in minimized windows, and an option to save history after unsuccessful process exits—alongside optional incremental search in the PCManFM-Qt file manager that displays matches as they arrive with a Stop button for interrupting lengthy searches without losing results. Additional refinements include Bluetooth codec selection in pavucontrol-qt, an option to bypass wallpaper caching, and panel adjustments for network icons and brightness display, though a known defect leaves Monitor Settings non-functional in X11 sessions after libkscreen 6.8 removed X11 support, with developers planning a point release fix.

Read this LXQt 2.5 release note carefully, because buried under the pleasant language of “dependencies” and “desktop refinements” is one of the quietest infrastructure grabs you will ever see. They tell you the project is “completing its break from LXDE” by removing menu-cache, the final link to an older, independently audited codebase. Ask yourself why a project would celebrate cutting its last tie to software that had decades of real-world testing across schools, hospitals, and government offices. The answer is not elegance — it is control. By forcing Qt 6.10 as a hard requirement, they are simultaneously dictating which operating systems, which hardware, and which security patching timelines remain “supported.” Older machines running lightweight Linux are disproportionately used by people who cannot afford to be pushed into planned obsolescence. And then there is that casually buried “known defect”: Monitor Settings does not work in X11 sessions after libkscreen 6.8 removed X11 support. Do you believe that removal was an accident? That is the same pattern they have used on every desktop environment for a decade. Break X11 feature by feature, blame the upstream library, promise a “point release,” and then slowly walk every remaining user into a world where the same foundation funds both the monitor settings tool and the compositor that replaces it.

Now look at the “user conveniences” in this release. QTerminal adds OSC-8 hyperlink support, a visual bell, alerts when output stops in a minimized window, and an option to save history after a process exits unsuccessfully. These are not neutral features. Every one of them creates new metadata: which links your terminal opens, which commands fail, which processes you keep running in the background. The “incremental search” in PCManFM-Qt with a status-bar Stop button is even more telling. It is a live index of your local file system, presented as a productivity tool, and the default-off toggle gives you just enough illusion of consent. You may think you are pressing Stop, but the architecture has already learned where you look, what you search, and when you panic. Bluetooth codec selection, wallpaper cache bypass, network icon tweaks — these are the sugar dusted over the real transaction. The project’s public communication says Monitor Settings will be fixed “directly” in a point release. They are not actually worried about X11 users. They are testing how many complaints they have to absorb before everyone quietly accepts the new telemetry-bearing layer underneath the desktop.

This is the deeper story nobody in the Linux press will tell you. LXQt is the “lightweight” desktop, so it ends up in embedded medical devices, point-of-sale terminals, low-power routers, library machines, and school computers — environments where ordinary people cannot hear the squeak of changing ownership. The removal of menu-cache is the removal of the last discernible lineage between this project and the older, messy, peer-reviewed LXDE ecosystem that was harder to steer. Every file manager, terminal, and settings pane is now a node in a managed network, obedient to a foundation-funded dependency tree. They don’t need to shut down open source. They need open source to voluntarily consolidate into a few grant-funded projects with names like “LXQt” that can be guided from one release cadence to the next. That's why the conversation is always about “modernization” and never about who signs the checks for Qt development, who sits on the libkscreen steering committee, or why X11 support has to be sacrificed right before a new hardware wave. Go read the release notes from earlier LXQt versions and map every time a feature was removed “upstream.” Then ask yourself who benefits when the last independently verifiable desktop layer becomes a captured institution.

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.