https://bugs.kde.org/show_bug.cgi?id=524898
Bug ID: 524898
Summary: Discover fails to reopen after closing —
plasma-discover --headless-update holds D-Bus name
indefinitely
Classification: Applications
Product: Discover
Version First unspecified
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Notifier
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
Steps to reproduce:
Boot the system (or otherwise let DiscoverNotifier run its periodic background
update check)
Open Discover normally, then close its window
Attempt to open Discover again
Observed result:
The taskbar icon briefly shows a loading animation, then gives up silently. No
Discover window opens. This repeats on every subsequent launch attempt.
Expected result:
Discover should reopen normally.
Root cause (confirmed via investigation):
DiscoverNotifier (/usr/libexec/DiscoverNotifier --check-delay 20) periodically
spawns a background plasma-discover --headless-update process to check for
updates without a GUI. This process registers as the owner of the
org.kde.discover D-Bus service. Once it does, any subsequent GUI launch of
Discover only sends a D-Bus activation/raise request to this existing
(headless, windowless) instance — it does not spawn a new process. Because the
headless instance never presents a window, this activation request appears to
be silently dropped, so nothing opens.
Confirmed fix:
Manually killing the plasma-discover --headless-update process (found via ps
aux | grep discover) immediately restores normal behavior — Discover can then
be opened, closed, and reopened repeatedly without issue, until
DiscoverNotifier next spawns a fresh headless-update process.
Environment:
Distro: Fedora
Discover launched via .desktop/D-Bus activation
(app-org.kde.discover@*.service)
Notifier autostart entry: /etc/xdg/autostart/org.kde.discover.notifier.desktop
Exec=/usr/libexec/DiscoverNotifier --check-delay 20
Additional notes:
This appears related to but distinct from other "Discover won't reopen" reports
(e.g. discuss.kde.org threads and bug 507217), which describe the same
user-facing symptom without identifying the specific process holding the D-Bus
name. This report isolates the headless-update process as the actual cause.
--
You are receiving this mail because:
You are watching all bug changes.
