Bug 492636 - Even uncheck Kalarm always starts up again with the system
Summary: Even uncheck Kalarm always starts up again with the system
Status: RESOLVED DUPLICATE of bug 489963
Alias: None
Product: kalarm
Classification: Applications
Component: general (other bugs)
Version First Reported In: 3.9.0
Platform: Fedora RPMs Linux
: NOR grave
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-04 08:06 UTC by quanticcpu2100
Modified: 2024-09-04 18:59 UTC (History)
0 users

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 quanticcpu2100 2024-09-04 08:06:43 UTC
Among the many bugs that Kalarm has that the developer has not been able to solve, we would like to report another bug in the hope that someone will be able to solve it someday. In the settings, when you uncheck the "Start at Login" option, even if you uncheck this option, Kalarm always starts up again with the system and does not respect the user's decision not to want Kalarm to start at system boot. You can always see in KDE > Settings > Autostart that Kalarm creates a new entry even if the user unchecks the "Start at Login" option in the Kalarm settings.
One of the biggest problems is that the Kalarm developer is stubborn and cannot understand and accept the bugs reported by users.

EXPECTED RESULT

When unchecking the "Start at Login" option, Kalarm should not create the entry again in KDE > Settings > Autostart.


SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.7 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor
Memory: 31,3 GiB of RAM
Graphics Processor: AMD Radeon RX 6800 XT
Manufacturer: ASUS
Comment 1 David Jarvie 2024-09-04 18:59:11 UTC
Finally you have answered the question which asks for more information in bug 489963. That is what was preventing that bug from being investigated further.

*** This bug has been marked as a duplicate of bug 489963 ***