https://bugs.kde.org/show_bug.cgi?id=347286
--- Comment #9 from stakano...@libero.it --- First of all my apologies that I did not respond on the request of Laurent (which never arrived at may desk, sometimes I do not receive he mail from kde bugzilla (which brought me to change several times provider)! I did run the exporter today with the standard kde 15.1, which I warn you in advance is quite outdated - but as it is shipped by default it is how the world sees you (at least using opensuse). As 15.2 Kmail/Pim is disfunctional and does break my system, I cannot provide feedback on that version. Currently this refers to: Opensuse 15.1 (with EOL on 31.01.2020 Plasma 5.12.8 Framework 5.55.0 QT 5.9.7 Under these conditions the KDE PIM software in general is functional (although subject to reported crashes and an apparent memory leak if used on a system for long time idling). That said, closing all applications of KDE PIM (by using exit) does not close all the application but leaves http instances belonging to Kontact in the memory. You have terminate them with sysgard. I did not try if that would have caused the exporter to crash and terminated instead. Once done the pimsettingsimporter seems to export without crash. It also does import without crashing in a vergin user but: creates entries without clear name or origin like 152040 and similar. Does not recreate all folders. Does represent alike the archiving tool a "local folder" pathology where you end up after two migrations using the default with: local folder/local folder/local folder/ importeduserfoldergoes here. You can change that by hand but for a lot "cryptic imports", that is without human readable name or without a destination folder were I found it quite difficult to understand what the program expected me to do. I was also asked to overwrite KDE PIMrc not one but several times, which may indicate a silent crash during import, but you may know, maybe it is normal. Once finished the import, starting the program KDE PIM, it crashes and is unusable because complaining of not being able to create the "resource 06 of the trash folder". akonadictl fsck and vaccum followed by a restart of the server did not help. I repaired finally, by eliminating the existing "trash" resource, on "good luck and boldly going were not user has gone before attitude" in akonadiconsole manually. Then the program KDE PIM started and seemed to have imported the rest of the resources conveniently. Personally I do not think that the exporter is currently functional in the good sense, but it does not crash while using it immediately! So we can say the bug is fixed. Or "that" bug is fixed. So feel free to close it as fixed, if you think it is applicable. I am currently considering changing distribution to find out if the sad status of the KDE PIM program is depending on a packaging / distribution problem or is inherent to the quality of the software. I am aware that the version used for this is old. I am uninformed if there have been major changes to the program since. It is also very difficult for me to "just to post the debugging" as I would have to edit all my sensitive data in the output by hand, since I do not wish to share these "details" on the internet. I can however, if you are interested, try to use the data of the exporter and import it in a instance of opensuse TW to see if the same issues present. I can confirm that the "local folder issue" has appeared at least by another user in the opensuse DE mailinglist for 15.2 (apparently that user was able to use it) and he faced the /local/local annoyance too. He also reported that not all folders were correctly restored, some were "invisible" after migration or "vanished". I think this corresponds to my import experience where some sources had cryptic names and some had (for unknown reason) no destination folder. -- You are receiving this mail because: You are watching all bug changes.
