https://bugs.kde.org/show_bug.cgi?id=521020

            Bug ID: 521020
           Summary: --headless-update hangs indefinitely on broken flatpak
                    remotes, blocking all GUI launches via single-instance
                    mechanism
    Classification: Applications
           Product: Discover
      Version First unspecified
       Reported In:
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: discover
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

When DiscoverNotifier spawns plasma-discover --headless-update at login, and a
broken user flatpak remote exists (e.g. one pointing at a local flatpak-builder
build cache with no summary file), Discover hangs indefinitely trying to
refresh that
  remote. Because Discover enforces a single-instance via D-Bus
(org.kde.discover), every subsequent GUI launch is silently absorbed by the
stuck headless process — Discover appears to simply not launch with no error
shown to the user.

  The stuck process can run for days. The only fix is to kill it manually.

  Steps to reproduce:

  1. Have a user flatpak remote pointing at a local path that is not a valid
flatpak repository (e.g. a flatpak-builder build cache created by
flatpak-builder --install). These remotes are named *-origin and *-debug-origin
and are auto-created by
  flatpak-builder.
  2. Log in to a KDE Plasma session — DiscoverNotifier spawns plasma-discover
--headless-update at startup.
  3. Observe that plasma-discover --headless-update runs indefinitely (visible
in ps), never exiting.
  4. Attempt to launch Discover from the application menu or taskbar — nothing
happens, no window appears, no error.

  Expected behavior:

  --headless-update should time out or skip remotes that fail to refresh (e.g.
return "server has no summary file"), then exit cleanly so the D-Bus name is
released and GUI launches work normally.

  Actual behavior:

  --headless-update hangs indefinitely on the broken remote. The D-Bus
single-instance name is held, silently swallowing all GUI launch attempts.


i am sorry this descption was largely ai generated. but is an actual issue i
ran it. discover never opens until i kill it first

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to