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.
When you said "Location", you want mean sidebar tab selected ? If yes, here digiKam remember the last tab selected between sesion... Gilles Caulier
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.
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
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.
Good to know that you are looking at it, Marcel :)
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.
What is the status with this report...?
Using digikam 0.10 from kdemod (archlinux) packages, still the same.
Anders, Marcel as commited in current code from svn. You need to test with last digiKam 1.0.0-beta5... Gilles Caulier
It's not fixed yet and still on my TODO list (for 1.1 most likely)
*** Bug 265861 has been marked as a duplicate of this bug. ***
Anders, It still valid using digiKam 2.x serie ? Gilles Caulier
Anders, It still valid using digiKam 3.5.0 ? Gilles Caulier
New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ?
digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance.
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