https://bugs.kde.org/show_bug.cgi?id=522122
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|REPORTED |CONFIRMED CC| |[email protected] --- Comment #5 from [email protected] --- I was able to reproduce the issue, on Krita 6.0.3, on ArchLinux, on the native build installed via the package manager. In short, this does seem like a bug with native file dialogs, as I can't reproduce the issue with that disabled both on the native package install or AppImage (where it is always disabled). Krita does warn the user about native dialogs potentially having issues depending on the system, however this message is only seen if you go to adjust the setting manually. I usually use the AppImage so I'm not sure if it is enabled by default or not. --- STEPS TO REPRODUCE 1. Create a new document 2. Enable native file dialogs (Settings > Configure Krita > General > Miscellaneous > Check "Enable native file dialogs" 3. File > Export... 4. Select any File Type option (eg. leaving as the default) 5. Type a filename (eg. "filename") 6. Check "Automatically select filename extension" 7. Change File Type to "All supported formats" 8. Type any valid filename extension Krita supports after the filename (eg. "filename.png") 9. Click Save. 10. The file will be saved: a. If "Export..." was used, the document will be saved immediately. b. If "Export Advanced..." was used, you will be prompted with the "Krita Document" popup dialog for resizing the exported canvas. Click Okay to save. 11. The saved file will be named whatever was typed + ".kra" appended to the end for its extension. (eg. "filename.png.kra") OBSERVED RESULT The saved file will be named whatever was typed + ".kra" appended to the end for its extension. (eg. "filename.png.kra") --- ADDITIONAL INFORMATION This can be chained, so going to export the document again will automatically fill the File Name field with the filename with extension as it was exported (so "filename.png.kra" in all these examples). This can also be extended to arbitrary lengths. For example, just before clicking save, one can name the file "filename.png.kra.kpg.avif.bmp", and it will be saved as such but with an additional ".kra" added following the steps above, and thus ultimately be saved as a Krita Document file. This can ALSO be done in a way that causes the document to be saved as any other supported filetype entirely. The exact steps I did not properly track, but in playing with the File Type options and checking/unchecking "automatically select filename extension", as well as typing different extensions, I managed to get a "filename.jpg.exr", with EXR being the filetype option just before finally switching to "All supported formats". Again though, I cannot reproduce this on Krita 6.0.3 with native file dialogs disabled, whether on a native install or on the AppImage. Krita does warn the user that this may not work correctly on some systems in the settings to enable it, but nevertheless this does not seem like intended behaviour. I am curious if this can be replicated in other software though using native file dialogs that also provide the same option. I tried doing so in Kate, but switching File Type to "All Files" there unchecks and disables "automatically select filename extension". The file dialog there also does look slightly different, though I'm unsure if that's due to the differing application theme I have selected. In any case, this appears to avoid the issue. Suffice to say, the native dialog option has some issues when automatically adding filename extensions. I think if it was changed to behave similarly to Kate, where the option is disabled when "All supported formats" is selected, then that would essentially fix the issue, as this only seems to occur as a result of being able to have it checked when switching to an "any format" option, and then editing the filename in a way it doesn't detect the intended filetype change. As this is an issue in the native dialog, I'm not sure if this would be some setting in Qt that needs to be changed, or something that is just system dependent and can't really be fixed. My limited experience in programming with Qt leads me to believe the former, but I'll leave it to a developer/maintainer to inspect things more closely! --- SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.7.3 KDE Frameworks Version: 6.28.0 Qt Version: 6.11.1 Kernel Version: 7.1.5-zen1-2-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor Memory: 32 GiB of RAM (31.2 GiB usable) Graphics Processor: AMD Radeon RX Vega -- You are receiving this mail because: You are watching all bug changes.
