December 15, 2025
Next stop: bus fire
D-Bus is a disgrace to the Linux desktop
Author torches Linux's app bus; comments split between 'systemd panic' and 'Binder fix'
TLDR: A developer says Linux’s app-to-app message system (D‑Bus) is broken and plans a new one. Comments explode into systemd fears, calls to use Android’s Binder, and demands for documentation—important because this is how your apps talk, and changing it could reshape the Linux desktop’s everyday behavior.
Linux drama alert: a window‑manager dev calls D‑Bus—the “bus” where apps chat—a disgrace and vows to build a new one. He blasts loose “standards,” wild “variants,” and security holes, plus a spec snafu where apps ignore “restore_token” and send “restore_data” instead. That’s the setup; the comments are the show.
First laugh: ginko’s systemd jump scare, worrying the replacement would get swallowed by Linux’s biggest megaproject. Pragmatists pile in: jasonjayr pitches a per‑app firewall/translator so old apps can still talk, while charcircuit says, forget reinventing—use Android’s Binder, the message system shipped on billions of phones. Shots fired.
Then the accountability brigade arrives. _flux deadpans that the author’s own hyprwire and hyprtavern should come with docs, specs, and tests—otherwise it’s more bus‑stop poetry than protocol. publicdebates drops a meta‑mood: the “best” tech doesn’t always win; adoption is chaos, not merit. Memes fly: “Garbage in, garbage out? More like garbage bus, garbage route.” The crowd splits between excitement for a clean slate, fear of yet another Linux subsystem war, and a chorus demanding boring things—standards, permissions, and paperwork—before anyone boards the next bus. In short: the desktop’s group chat is on fire, and everyone’s arguing whether to call the fire department, rebuild the house, or move into Android’s.
Key Points
- •D‑Bus is presented as a useful concept for inter-application communication but criticized for lenient, unstructured implementation.
- •The article claims D‑Bus standards and documentation are fragmented and inconsistently followed by clients.
- •A case study with xdg-desktop-portal-hyprland shows divergence from documented portal specs, requiring mimicry of KDE behavior for compatibility.
- •The use of variants and a{sv} in D‑Bus is criticized for enabling unstructured data exchanges and ambiguity.
- •Security concerns are raised about D‑Bus permissions and broad visibility/callability, though details are partly truncated in the provided text.