Bug 182534

Summary: digiKam does not remember its location with session management
Product: [Applications] digikam Reporter: Anders Lund <anderslund>
Component: Albums-MainViewAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, marcel.wiesweg
Priority: NOR    
Version: 1.8.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In: 5.1.0
Sentry Crash Report:

Description Anders Lund 2009-01-31 07:23:25 UTC 
Version:           0.10.0-rc2 (rev.: 917004) (using 4.2.00 (KDE 4.2.0), Arch Linux)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.28-ARCH

When digiKam is stopped/started by the session manager, it does not store its loction (album/search...). Instead it goes to the location used last time it was closed by the user.

This is a long standing issue, it has been there for as long as I can remember.
Comment 1 caulier.gilles 2009-01-31 10:28:57 UTC 
When you said "Location", you want mean sidebar tab selected ? If yes, here digiKam remember the last tab selected between sesion...

Gilles Caulier
Comment 2 Anders Lund 2009-01-31 22:36:44 UTC 
Between sessions, yes, but when closed and started by the session mannager, no. (That means left open when KDE is shut down, and reopened by KDE next time i log on).

By location, i mean specific album/date/tag/search/whatever is in the left sidebar tabs where i selece a location.
Comment 3 Marcel Wiesweg 2009-02-07 17:40:09 UTC 
SVN commit 922834 by mwiesweg:

First parts for proper session management support

CCBUG: 182534

 M  +17 -0     digikamapp.cpp  
 M  +1 -0      digikamapp.h  
 M  +3 -1      main.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=922834
Comment 4 Marcel Wiesweg 2009-02-07 17:43:01 UTC 
Session management is not working even after this commit. DigikamView::saveViewState is not called at session logout, or at least changing the config there does not take effect.

I am not feeling well to take deeper changes at the current release stage of 0.10, postponing to 0.11.
Comment 5 Anders Lund 2009-02-07 18:03:04 UTC 
Good to know that you are looking at it, Marcel :)
Comment 6 Marcel Wiesweg 2009-02-07 18:05:51 UTC 
It will be required to implement KMainWindow::saveProperties and readProperties for our main window. It seems session management closes a window by calling QCoreApplication::quit which is effectively exit(0). In this case probably windows are not closed which is required for our destructor-based config writing to take effect.
Comment 7 Andi Clemens 2009-10-08 01:26:36 UTC 
What is the status with this report...?
Comment 8 Anders Lund 2009-10-08 07:37:14 UTC 
Using digikam 0.10 from kdemod (archlinux) packages, still the same.
Comment 9 caulier.gilles 2009-10-08 08:25:53 UTC 
Anders,

Marcel as commited in current code from svn. You need to test with last digiKam 1.0.0-beta5...

Gilles Caulier
Comment 10 Marcel Wiesweg 2009-10-08 19:43:55 UTC 
It's not fixed yet and still on my TODO list (for 1.1 most likely)
Comment 11 Michael G. Hansen 2011-02-09 20:32:16 UTC 
*** Bug 265861 has been marked as a duplicate of this bug. ***
Comment 12 caulier.gilles 2011-12-14 09:40:19 UTC 
Anders,

It still valid using digiKam 2.x serie ?

Gilles Caulier
Comment 13 caulier.gilles 2013-11-25 17:16:39 UTC 
Anders,

It still valid using digiKam 3.5.0 ?

Gilles Caulier
Comment 14 caulier.gilles 2015-06-30 08:06:46 UTC 
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 15 caulier.gilles 2015-08-24 05:11:52 UTC 
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.
Comment 16 caulier.gilles 2016-07-14 16:52:39 UTC 
With digiKam 5.0.0  this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier