Bug 140962 - korganizer will always autostart
Summary: korganizer will always autostart
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-31 17:12 UTC by Sergey Sedlovsky
Modified: 2009-05-19 14:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Sedlovsky 2007-01-31 17:12:26 UTC 
Version:           3.5.6 (using KDE Devel)
Installed from:    Compiled sources
Compiler:          4.1.2 
OS:                Linux

Korganizer will always autostart, regardless that I tell it not to.

how to reproduce:
At first startup of korganizer (clean/fresh install), shut it down, it will ask you if you would like to autostart it the next time. and has a checkbox with "Don't ask me again" or something of the sort. check this checkbox, and tell it to autostart (I did it by mistake). restart X or KDM, when it starts up next, tell it not to autostart, it won't ask you again, as you told it to. However, restart X or KDM again, and you can see that korganizer keeps starting up.

People told me to see if there's anything in the Autostart directory, and there's nothing.
Comment 1 Wouter Van Roeyen 2007-02-13 22:50:56 UTC 
I can confirm this, you disable the "start at login" option, but the Korganizer always starts at login.
Comment 2 Sindhu Sundar 2008-07-05 17:05:51 UTC 
Yes, I have the same problem too. I always check the "do not start at login" but irrespective of that, it always starts up at the next login.
Comment 3 Allen Winter 2008-07-05 17:15:53 UTC 
look in /usr/share/autostart/korgac.desktop  (or where you distro installs it)

and see if that file contains the line "NoDisplay=true".

let me know.
Comment 4 Christophe Marin 2008-11-19 00:49:12 UTC 
This issue should be fixed now. Can you confirm please ?
Comment 5 Christophe Marin 2009-05-19 14:13:55 UTC 
No feedback. Let's assume this issue couldn't be reproduced.