Bug 180029 - Kontact does not save tab status upon exit & restart
Summary: Kontact does not save tab status upon exit & restart
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
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: 2009-01-08 14:44 UTC by John
Modified: 2017-01-07 22:25 UTC (History)
1 user (show)

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 John 2009-01-08 14:44:14 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Installed kontact & kdepim packages (Mandriva cooker):
libkontactinterfaces4-4.1.85-2mdv2009.1
kontact-4.1.85-2mdv2009.1
libkontactprivate4-4.1.85-2mdv2009.1
kdepimlibs4-core-4.1.85-2mdv2009.1
kdepim4-core-4.1.85-2mdv2009.1
libkpimidentities4-4.1.85-2mdv2009.1
libkpimutils4-4.1.85-2mdv2009.1
kdepim4-kresources-4.1.85-2mdv2009.1
kdepim4-4.1.85-2mdv2009.1
libkdepim4-4.1.85-2mdv2009.1

Steps to Reproduce:
1. Create some tabs in kontact, selecting different folders for each tab if desired
2. Read some mail
3. Quit kontact
4. Open kontact again, and only the one default tab for Inbox is there. The other tabs are gone

Expected behavior:
Tabs should be restored when kontact is opened again

Thinking about it some more:
Bug or wish? I did expect the tabs to be there again when I opened kontact, but maybe this is intended behavior? If so, maybe a "Save tab state" option?
Comment 1 Denis Kurz 2016-09-24 19:20:35 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:25:07 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.