Bug 109669 - Can't stop alarm daemon starting with Kontact
Summary: Can't stop alarm daemon starting with Kontact
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: reminder daemon (korgac) (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-26 22:15 UTC by Gogs
Modified: 2007-12-11 18:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gogs 2005-07-26 22:15:26 UTC
Version:           1.8.50 (using KDE 3.4.89 (>= 20050615), compiled sources)
Compiler:          gcc version 3.4.4
OS:                Linux (i686) release 2.6.11.11

No matter whether I select 'Start alarms client at login' or not, it ALWAYS starts up anyway. This is MOST annoying.....
Comment 1 Colin J Thomson 2005-11-27 14:05:26 UTC
I have noticed this with kde-3.5.0-rc1, using FC4 and kde-redhat RPMS,
Comment 2 Winfried Dobbe 2006-01-05 20:15:53 UTC
On Suse10 with KDE 3.5 Suse RPMs bug also exists. Changing the "Start Reminder daemon at login" doesn't change the following item in ~/.kde/share/config/korgacrc:

[General]
Autostart=true

Comment 3 Reinhold Kainhofer 2006-11-02 19:02:55 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 4 Colin J Thomson 2006-11-21 21:19:31 UTC
FYI, still seeing this with kde-3.5.5, FC6 using kde-redhat RPM's
Comment 5 Colin J Thomson 2007-01-12 01:09:11 UTC
This seems to work OK now with the latest KDE-Redhat-3.5.5-1.6.fc6 updates and a "fresh" .kde DIR
Comment 6 FiNeX 2007-12-11 18:33:31 UTC
It seems to be fixed on recent version such 3.5.8 or on the upcoming KDE 4.
Bug closed.