Bug 466552 - Kclock stays alive after closing it, without a way to shut it down.
Summary: Kclock stays alive after closing it, without a way to shut it down.
Status: RESOLVED WORKSFORME
Alias: None
Product: KClock
Classification: Applications
Component: General (other bugs)
Version First Reported In: 23.01.0
Platform: Flatpak Linux
: NOR normal
Target Milestone: ---
Assignee: Devin Lin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-27 18:32 UTC by Eridani Rodríguez
Modified: 2024-12-26 03:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eridani Rodríguez 2023-02-27 18:32:21 UTC
STEPS TO REPRODUCE
1. Install Kclock (I did from Flathub)
2. Start it and create a timer.
3. Close the app.

OBSERVED RESULT
1. Launch ´top´ in konsole to see that ´kclock´, ´kclockd´ and related processes are still running in the background, but there would be no visual indicator about this, nor a way to terminate the application from the graphic interface.
2. Opening the program again will spawn duplicated processes instead of reusing those that are still alive.

EXPECTED RESULT
1. The program should terminate cleanly without leaving any lingering background process.
2. There should be a configurable preference to keep it running in the background for tasks that may benefit from it, such as programmed alarms; optionally, this status should be indicated by an interactive icon in the system tray.

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.19.0-32-generic (64-bit)
Graphics Platform: X11
Comment 1 Devin Lin 2023-02-28 02:05:39 UTC
> Opening the program again will spawn duplicated processes instead of reusing those that are still alive.

I don't experience this with the Flatpak, there should only be one instance of /app/bin/kclockd running (and a bwrap process which is done by Flatpak)? The graphical app (kclock) also isn't running for me when the program is closed. 

It should be possible to implement it so that the daemon is running only if alarms/timers are active.
Comment 2 John Kizer 2024-11-26 19:38:55 UTC
Hi - are you able to try reproducing this on the current version? I tried the Flatpak and Fedora RPM and cannot reproduce the app process (kclock) staying open after being closed.
Comment 3 Bug Janitor Service 2024-12-11 03:46:33 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2024-12-26 03:47:34 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.