| Summary: | Kclock stays alive after closing it, without a way to shut it down. | ||
|---|---|---|---|
| Product: | [Applications] KClock | Reporter: | Eridani Rodríguez <eridanired123> |
| Component: | General | Assignee: | Devin Lin <espidev> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | hanyoung, john.kizer, nate |
| Priority: | NOR | ||
| Version First Reported In: | 23.01.0 | ||
| Target Milestone: | --- | ||
| Platform: | Flatpak | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Eridani Rodríguez
2023-02-27 18:32:21 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.
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. 🐛🧹 ⚠️ 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! 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |