[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[David Jarvie]

https://bugs.kde.org/show_bug.cgi?id=366562

David Jarvie  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[piedro via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

--- Comment #7 from piedro  ---
Fixed for me as well, thx a lot! 

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

Cheers and ty, p.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[David H . Gutteridge via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

--- Comment #6 from David H. Gutteridge  ---
Confirming this is fixed for me with the 16.08.1 release. Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[David Jarvie via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

David Jarvie  changed:

   What|Removed |Added

 CC||b...@gmx.at

--- Comment #5 from David Jarvie  ---
*** Bug 357653 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[David Jarvie via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

David Jarvie  changed:

   What|Removed |Added

   Version Fixed In||16.08.1
  Latest Commit||cc2d8bb39417b186bfe40470eba
   ||921a64ef6c6c8
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from David Jarvie  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[piedro via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

piedro  changed:

   What|Removed |Added

 CC||piedro.kul...@googlemail.co
   ||m

--- Comment #3 from piedro  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[David H . Gutteridge via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

David H. Gutteridge  changed:

   What|Removed |Added

 CC||dhgutteri...@hotmail.com

--- Comment #2 from David H. Gutteridge  ---
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".

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[Rex Dieter via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalarm] [Bug 366562] Kalarm starts in non-KDE desktop environments...

[David Jarvie via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366562

David Jarvie  changed:

   What|Removed |Added

  Component|kalarmd |general

--- Comment #1 from David Jarvie  ---
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=131410.

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

-- 
You are receiving this mail because:
You are watching all bug changes.