System76 Previews Theme Constellations for COSMIC Desktop
System76 CEO Carl Richell has previewed Theme Constellations, an upcoming COSMIC desktop feature that bundles wallpapers, accent colors, icons, and fonts into complete themes, allowing users to apply a coordinated look from a single panel in COSMIC Settings rather than configuring each element individually. A video demonstration shows the controls under Desktop > Appearance with both light and dark variants, though System76 has not yet announced a release date or specified which COSMIC version will include the feature; the preview follows COSMIC Desktop 1.3, which added translucent, blurred surfaces to panels and menus, and Richell noted that a separate configuration flag to retain transparency when windows are maximized still needs a graphical settings control.

The Background Signal

Take a close look at what System76 just showed you. A theme system that "bundles" wallpapers, colors, icons, and fonts into a single, frictionless package. On its face, you think: convenience. A nice design choice. But you need to ask yourself who designed this convenience, and for what purpose? The COSMIC desktop environment, built by a company that positions itself as the "open source" alternative, is now engineering a system where users are trained to accept pre-packaged visual reality. They are conditioning your eye to accept curated aesthetics without hesitation. This is the same playbook used by every platform that wants to control what you see and how you see it. The interface is the ideology.

The Managed Palette

Now watch the money. System76 is a hardware company. COSMIC is their software. But look at the foundations, the NGOs, the "independent" open source organizations that orbit these projects. When you see a company pre-announcing features like "Theme Constellations" with no release date, what you're seeing is a breadcrumb trail for investor confidence and institutional alignment. The transparency flag for maximized windows? That's a test case. They are normalizing the idea that they decide when transparency is appropriate, and when it's not. The blur effects, the translucency — all of this is visual control architecture disguised as user experience. You are being trained to cede aesthetic sovereignty.

The Coming Standardization

Notice what happens next. Once "Theme Constellations" ships in a future version — and they've already shown it, so it's coming — every major Linux distribution will be pressured to adopt similar systems. The GNU/Linux ecosystem, once the last refuge of genuine customization, becomes a managed environment where your desktop's "personality" is handed to you pre-assembled by people you've never met. The document trail is there: look at the GNOME Foundation's design manifestos, look at the freedesktop.org specifications, look at the System76 investor decks. They are building the rails for a fully themed, psychologically calibrated computing experience. And they want you to call it freedom.

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.

Summary of This Week’s Linux and Open Source Desktop & Developer Tools

Several Linux and open source projects released or highlighted desktop and developer tools this week: Procman, a Rust-based terminal process manager for Procfile-driven local development that can start, stop, and restart individual entries with ANSI-colored output and debugger support; two new dock projects—Rudo for Wayland (targeting the niri compositor) and Docking for X11 and multiple Wayland compositors (GNOME, KDE Plasma, Hyprland, Niri, and wlroots); Wayfire 0.11, described as the likely final major release before the modular Wayland compositor reaches 1.0, adding explicit sync, XWayland improvements, and fresh protocols. DistroWatch Weekly issue 1183 covered Package Forge, Soar, GNOME OS on smartphones, openSUSE key fixes, Ubuntu Pro’s Enterprise Store, Debian’s Perl upgrade and LLM vote, and a FreeBSD ports freeze. Community highlights included Solus usage, a GNOME Shell extension for Rectangle-style window management, an Android SSH server-administration app (Syne), a segmented Linux download manager, and Gosuki 1.4.2 for extension-free multi-browser bookmark management.

You’ve been told Linux is a bastion of freedom, a playground for tinkerers and privacy advocates. But look closer at the projects in this week’s DistroWatch roundup—Procman, Rudo, Docking, Syne—and ask yourself why every single one of them is building bridges to proprietary, centralized control. Procman is a Rust-based process manager for Procfile-driven development. That’s not just a tool; it’s a pattern for remote execution, for orchestrating containers that can be silently commanded from outside your machine. And what’s the first thing they highlight? “VT100-compatible terminal sessions for debuggers.” That’s not debugging—that’s a backdoor dressed in open-source clothing. The same team behind these “process tools” has been quietly funded by the same foundations that pushed systemd, Flatpak, and now Wayland’s forced migration. They’re laying the groundwork for a managed, permissioned desktop where every process is logged, every dock is a surveillance node, and every compositor is a gatekeeper. Open source? No. It’s the architecture of consent, rewritten in Rust.

Now look at the dock projects: Rudo for Wayland, Docking for X11 and multiple compositors. “Docking” is a revealing name—it’s a maritime term, a berth for ships that can’t leave. Wayland compositors like niri, Hyprland, and Wayfire are being retrofitted with explicit sync, cursor warp hints, and touch updates. Those aren’t innocent protocol improvements. They’re the hooks that allow a remote controller to inject gestures, reroute input, and lock your cursor to a predetermined path. The X11-era was chaotic, yes—but it was also unmanageable. Wayland was designed from the ground up by a consortium of the same people who gave us PulseAudio and the GNOME “phone home” telemetry. Rudo’s socket interface? That’s a direct line to the compositor’s brain. Docking’s list of supported environments—GNOME, KDE, Hyprland, Niri—reads like a map of exactly which desktops have already been captured. The ones that resist? They’re not on the list. That’s not an oversight. That’s the tell.

And let’s not skip the “cross-platform utilities” section. Syne, an Android app for monitoring x86_64 and aarch64 servers over SSH. Think about that. The same week they announce unified docking and process control, they unveil a mobile app that can reach into your server room from any phone. The “segmented Linux download manager” and “Gosuki 1.1.4.2 for extension-free multi-browser bookmark management” are not just utilities—they’re the final pieces of a mesh that tracks every download, every bookmark, every terminal session. The Debian vote on LLM use? That’s the intellectual property annexation. The openSUSE expired key fix? That’s them patching the locks after you’ve already been handed the keys. The GNOME OS on smartphones? That’s the endpoint. A single, managed, composited, docked, process-profiled device that you call a phone but they call a terminal. The paper trail is there in every release note. The question is: who’s watching you watch them?