Bug 183402 - kontact does not start with the module set to always start with, if restored as part of the KDE session
Summary: kontact does not start with the module set to always start with, if restored ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-06 10:43 UTC by S. Burmeister
Modified: 2010-05-29 18:37 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 S. Burmeister 2009-02-06 10:43:55 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

By default kontact restores the module that was shown last, no matter whether you quit kontact and restart or whether it is quit because kde is shutting down and hence restored when the user logs back in.

So if a user sets the "always start with module x" in kontact this should be valid for both, restart after quit and restart as part of a kde session, yet the latter does not work. At least that is what "always" mediates.

Other "use on start" features such as kmail's check for new messages are applied on both start types as well, although they lack the "always". So if the "restart as part of a session" is seen as something not included in "always", then kmail should not check in that case either, which IMHO does not make sense.

Expected behaviour: If "start always with module x" is set, show that module on every start, no matter how kontact was quit.
Comment 1 S. Burmeister 2010-05-29 18:37:29 UTC
Works in KDE 4.4.x