https://bugs.kde.org/show_bug.cgi?id=370440
Bug ID: 370440 Summary: KML Export fails when destination directory partition differs then the temp directory partition. Product: kipiplugins Version: 5.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: KMLExport Assignee: kde-imag...@kde.org Reporter: met...@gmail.com The temp directory in windows 7 and above is usually in the C:\Users\[username]\AppData\Local\Temp directory. When you try use a 'destination directory' that is located on a drive/partition that is different then the C:\ drive (like the M:\ drive), the KML Export tools fails with the following error: "Cannot move data to destination directory" It looks the failure is on line 538 of the kmlexport.cpp file. The problem is that the QDir rename function can't handle a rename across partitions (see http://doc.qt.io/qt-4.8/qdir.html#rename). The actual creation of the KML file is successful, it is just not moved to the specified destination directory due to this issue. You will find the exported KML file and images in a the temp directory, for example: C:\Users\[username]\AppData\Local\Temp\kipi-kmlrexportplugin-8296 It took me awhile to figure out that the data was dumped to the temp directory. I actually had to look through the code to figure this out. So I doubt a non-programmer would be able to figure this out. Reproducible: Always Steps to Reproduce: 1. Select a image. 2. Select the Export > Export to KML... menu item. 3. Set the destination directory to something other then the C:\drive. 4. Click export. Actual Results: The actual creation of the KML file is successful, it is just not moved to the specified destination directory due to this issue. You will find the exported KML file and images in a the temp directory, for example: C:\Users\[username]\AppData\Local\Temp\kipi-kmlrexportplugin-8296 Expected Results: The KML file and images are moved to the destination directory. A possible workaround can be found here: http://stackoverflow.com/questions/15130840/qdirrename-doesnt-work I'm not sure if this is an issue on Unix based system, it just happens to me on a Windows 10 box. -- You are receiving this mail because: You are watching all bug changes.