Flatpak: "No units returned" since 2.24.2 on hosts with xdg-dbus-proxy < 0.1.6

Open
  • Is something wrong?
#86 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, rust
Domain
desktop, devtools

Research direction

Start by reading the Flatpak build configuration and the zbus dependency changes around version 2.24.2, then compare the Flatpak runtime’s xdg-dbus-proxy requirements with the reported 0.1.5 host version. The issue suggests keeping the Flatpak build on zbus 5 or showing a workaround hint; done means Flatpak installs with proxy 0.1.5 can load units or present a clear actionable message.

Written by the indexing model from the issue text.

Description

bug

Since 2.24.2 the Flatpak version shows "Something went wrong - No units returned" for me. Still happening on 2.24.5.

Setup: Pop!_OS 24.04 (Ubuntu 24.04 base), Flatpak 1.18.1, xdg-dbus-proxy 0.1.5, Flathub user install.

Log with RUST_LOG=info:

** (process:43659): WARNING **: 08:32:52.222: Invalid message header read
ERROR sysd_manager::widget::unit_list::imp: 2222: Unit List Call Error: ZBusError(InputOutput(Custom { kind: BrokenPipe, error: "failed to read from socket" }))
ERROR sysd_manager_comcontroler::sysdbus::watcher: 187: Tokio channel dropped RecvError(())

I think this comes from the switch to zbus 6. zbus 6 removed its xdg-dbus-proxy workarounds (z-galaxy/zbus#1965), and its upgrade guide says Flatpak apps now need xdg-dbus-proxy 0.1.6+. Flatpak uses the host's proxy, and Ubuntu 24.04 still ships 0.1.5, which drops the connection (that's where Invalid message header read comes from).

Bypassing the proxy fixes it, and all units load:

flatpak override --user --socket=system-bus --socket=session-bus io.github.plrigaux.sysd-manager

Maybe keep the Flatpak build on zbus 5 for now, or show a hint about the workaround instead of the generic error? Looks similar to #32.

Dominant language
Rust
Stars
251
Forks
11
Avg merge
7h 14m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from plrigaux/sysd-manager

All issues in plrigaux/sysd-manager

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.