Bug 366562

Summary:	Kalarm starts in non-KDE desktop environments...
Product:	[Applications] kalarm	Reporter:	piedro <piedro.kulman>
Component:	general	Assignee:	David Jarvie <djarvie>
Status:	CLOSED FIXED
Severity:	normal	CC:	buti, dhgutteridge, piedro.kulman, rdieter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:	cc2d8bb39417b186bfe40470eba921a64ef6c6c8	Version Fixed In:	16.08.1
Sentry Crash Report:

Description piedro 2016-08-09 17:58:10 UTC

Kalarm is by default set to start with every desktop environment. 

Please add 

X-GNOME-Autostart-enabled=false
OnlyShowIn=KDE

or something along these lines to the default autostart configuration file in /etc/xdg/autostart/. 

A KDE application should not be autostarted within other DEs unless explicitly asked for. 

It's just a little change to the default configuration and leads to less people wondering how to disable kalarm when starting Gnome which  has it's own calendar and reminder service. 

thx a lot, piedro 

Reproducible: Always

Comment 1 David Jarvie 2016-08-09 19:06:50 UTC

KAlarm is designed to autostart at login once it has been run, to ensure that alarms are not missed. But it shouldn't start if it has never been used, or if the user has explicitly disabled start-at-login for it.

What version of KAlarm are you using? What you report may well have been fixed in version 2.11.6 (KDE Applications 16.04.1). The fix prevents KAlarm autostarting in non-KDE desktops if KAlarm's start-at-login is disabled. See https://forum.kde.org/viewtopic.php?f=229&t=131410.

Please see further explanation of autostart in non-KDE desktops at https://bugs.kde.org/show_bug.cgi?id=357653.

Comment 2 David H. Gutteridge 2016-08-09 21:08:23 UTC

Under Gnome 3.20, KAlarm is starting for me when I've explicitly disabled start-at-login for it via the UI's settings panel. This is with KAlarm 2.11.7-5ak (KDE Applications 16.04.3) on Fedora 24. The final entry in /etc/xdg/autostart/kalarm.autostart.desktop is "X-KDE-autostart-condition=kalarmrc:General:AutoStart:false" but that has no effect (which is presumably because it's a KDE-specific directive). My .config/kalarmrc also contains "NoAutoStart=true".

Comment 3 piedro 2016-08-11 12:41:45 UTC

I use KDE and kalarm version16.4.3. 

(Well, I do not use it really but have it installed to check out KDE here and then to find out when it's good enough for productive ue for me...) 

So, same situation as for David. 

thx, p.

Comment 4 David Jarvie 2016-08-18 20:11:11 UTC

This is now fixed, for KDE Applications 16.08.1 release, so that KAlarm won't autostart on non-KDE desktops if it has never been run. Unfortunately, the KDE conditional autostart mechanism just isn't compatible with other desktops.

Commit cc2d8bb39417b186bfe40470eba921a64ef6c6c8 in kdepim.

Comment 5 David Jarvie 2016-08-18 20:13:46 UTC

*** Bug 357653 has been marked as a duplicate of this bug. ***

Comment 6 David H. Gutteridge 2016-09-14 15:48:44 UTC

Confirming this is fixed for me with the 16.08.1 release. Thanks!

Comment 7 piedro 2016-09-14 18:52:03 UTC

Fixed for me as well, thx a lot! 

Some other background services are still autostarting but kalarm isn't anymore. 

Cheers and ty, p.