https://bugs.kde.org/show_bug.cgi?id=326395
Bug ID: 326395 Summary: Export Key created in Location Other Than Specified Classification: Unclassified Product: kleopatra Version: 2.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: george.gil...@gmail.com CC: m...@kde.org In Kleopatra (v2.2.0 in GPG4WIN v2.2.0 on Windows 7 fully patched), when performing "Export Secret Keys", the file dialog box allows the user to select the location where the file is written. But when exporting a file in gpg format, the user's choice of "C:\" is ignored and the file is instead written in "%LOCALAPPDATA%\VirtualStore" (which on my system is C:\Users\{myusername}\AppData\Local\VirtualStore). The same is true for performing "Export Certificates". This is something that is only a trivial issue for technical users, but for non-technical people to whom I recommend using Gpg4win it would be very confusing when the software asks them where to save a file and then saves it somewhere else! As GPG4Win is the premier implementation of GPG on Windows, this would have a serious impact on usability and widespread adoption by non-technical users. Reproducible: Always Steps to Reproduce: 1. Select "Export Secret Keys" or "Export Certificates". 2. In the Save File dialog box instruct that the file be saved in "C:\". Actual Results: The file is NOT saved in "C:\", instead it is saved in "%LOCALAPPDATA%\VirtualStore" (which on my system is C:\Users\{myusername}\AppData\Local\VirtualStore). Expected Results: The file should have been saved in the location specified in the Save File dialog box. Tested using Windows 7 fully patched. This problem will have a serious impact on usability for non-technical users. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs