Today I updated Krusader from "2.4 beta 3 single step" to 2.5 version. I lost all krusader config, including my bookmarks and last opened folders.
** Removed by KDE Sysadmin due to inclusion of sensitive information **
The path for configuration files changed in general for all KDE5 applications. No files are lost and you can manually copy the files to the new locations. The main config file for Krusader is saved at > /home/(user_dir)/.config/krusaderrc The new directory for additional config files (including bookmarks) is > /home/(user_dir)/.local/share/krusader About automatic migration: The main config file can be easily moved ( https://community.kde.org/Frameworks/Porting_Notes#Migrating_configuration ) but moving all other files must be done manually. This needs some work and must be done properly. I'm unsure if we should really do this. Opinions?
>[...] if we should really do this. Opinions? Probably yes, in my humble opinion :-), because normally, for example after an operating system update, users expect having Krusader with the same bookmarks and other settings. Meanwhile, users can utilize a web page with a basic explanation of how to do the data migration manually. Although it would be a task with less priority than some others that already exist, in my humble opinion :-)
I'm sure: YES, it should be an automatic task and transparent for the user. I'm an "experiencied" user and I had been able to fix the problem, but the average user need to update without doing anything more. A bad experience with an application, like to lost suddenly their Krusader bookmarks, for an average user is the best best way to lost him like an user ;)
*** Bug 371964 has been marked as a duplicate of this bug. ***
Especially this should be automagical, since the format of both krusaderrc and bookmarks (perhaps also other files?) are compatible, it should be migrated... In general, users shouldn't have to care about such low-level stuff, and it's only few lines of code, right?
> In general, users shouldn't have to care about such low-level stuff Yes >, and it's only few lines of code, right? No, not really. Migrating the rc file is easy but for everything else: if (upgraded Krusader): create (correct new dir) if not exists yet for (all files still used) in (correct old dir): move to (correct new dir) if not exists yet Note for myself: http://doc.qt.io/qt-5/qstandardpaths.html#details
Updating: To copy /home/(user_dir)/.config/krusaderrc file to new location doesn't not recover my bookmarks. Just now, I don't know where are my old bookmarks. Definitively, this need a fix. :(
Bookmarks are in another directory: Old path: /home/{user_directory}/.kde4/share/apps/krusader/ New path: /home/{user_directory}/.local/share/krusader/
Closing this. Version 2.5 is very old now.