The 'open images/save as' dialogue for Krita on KDE itself... needs work

Krita user of 2 years, Kubuntu user of… pretty sure less than a month, here. I regularly draw using Krita, using old project files as basis for new projects, and I have to say that that’s admittedly one of the things that drew me to Kubuntu specifically— the fact that Krita was preinstalled immediately caught my eye.

But what I don’t like at all is the ‘open images/save as’ dialogue. Namely, the only two views supported by the dialogue are List View and Details View, with Dolphin’s Icon View– or an equivalent– nowhere in sight, and especially not with crucial-to-my-workflow features like Show In Groups/Sort By Type (which I use to segregate the .KRA and .PNG files, so I don’t accidentally click the wrong one).

Worse still, despite there seemingly being a pane on the right to display the currently selected file, this goes completely unused in ‘Open Images’ and ALMOST goes unused in ‘Save As’ due to a crucial flaw– the first click doesn’t select the file, it OPENS it (directly opening the image immediately in Open Images mode, or attempting to overwrite it in Save As mode; this is why it doesn’t technically go unused in Save As, because the ‘Filename.png already exists. Do you want to replace it?’ dialogue box pops up, allowing you to look past it to see the file popping up on the side pane.). This behavior is DESPITE me setting KDE to select on the first click and open on double-click in the System Settings app; a setting that Dolphin obeys but this dialogue doesn’t.

Between the lack of respect for “Select on single click, open on double-click” and the lack of icon view, this means that there is no way to SEE the contents of a given file before opening it. In ‘Save As’ mode this is… mostly fine-ish, as the typical use case for this dialogue in this mode is “Find the correct folder and type in a new filename”; in ‘Open Images’ mode this is nigh UNUSABLE, forcing me to instead open up Dolphin to find and open the file I want to open.

And this is in contrast to… well, I’ll say it, Windows, which seemingly just uses File Explorer straight-up, the icon mode and grouping are (as I remember it) right there, and if I want to open a file, it will behave the same way File Explorer does in that it wants me to double-click.

I get that I can’t simply set Dolphin to be the save/load dialogue; failing that, can the save/load dialogue at least be improved in some way?

For the record this is what it looks like. Ech.

that’s not what mine looks like?

what version of kubuntu and what version of krita are you running?

I’m using Kubuntu 24.04 LTE, with its pre-installed version of Krita, which is…

5.2.11-prealpha what, how’d I end up updating to a pre-alpha version without realizing/noticing/attempting to

Anyways, after some continued reading up on the issue, I learned of this setting here:

Which in turn, when enabled, changes the file-picker dialogue to:

A MUCH better– and far more usable– file picker, which fixes nearly every single issue I had with the ‘non-native’ file picker (icon view, obeying the double-click setting, ect), with the only caveat that it doesn’t include Grouping as far as I can tell. It’s also, interestingly enough, the same file picker that Firefox uses.

Which, I have a sneaking suspicion that this “native file picker” IS Dolphin??? Maybe??? It definitely feels like Dolphin in a way the other file picker didn’t

Also, for the record, I have uninstalled the pre-installed Krita version and reinstalled it through the Discover app. Doing this has downgraded me to 5.2.2, and either it has remembered that “Native file dialogues” should be enabled (not likely given it doesn’t remember my other settings) or they’re simply enabled by default on this version.

can confirm that setting is enabled on my 5.2.2 version of krita on kubuntu 24.04

don’t remember if krita came preinstalled or if i installed it shortly after installing the OS (at it is on my list of essential software).

definitely sounds like the presets for the alpha release are not yet potted.

Kubuntu is based on Ubuntu LTS with some backports, I believe. It’s had 5.2.2 for a long time. (It’s approaching 2 years old at this point.)

If you go through the Discover app, try selecting the Flatpak version from Flathub. (You might need to install flatpak, not 100% familiar with Kubuntu.) It’s always up to date and supports the native file dialogs.

Discover doesn’t have a way to select Flatpak from Flathub? Or at least I’m not seeing it. Am I looking in the wrong place?
…Also, if 5.2.11 is the version that’s supposedly in prealpha, why is Snap offering it– without a note that it’s in prealpha– instead of, say, 5.2.10?

Ah, I forgot about Snaps and Ubuntu. Snaps are like their version of Flatpaks, that would also work.

The current version is 5.2.11. 5.2.11-prealpha actually has 5.3 features. It’s confusing, I know. :stuck_out_tongue:

It should, in the Settings section. You will have an ‘enable flatpak’ option or maybe “missing Backends”. After enabling that (and possibly a reboot? I don’t recall), you will need to go back and ‘add flathub’ to add the standard repo for this. Sometines it can take a bit for this button to show, after Discover has loaded everything and checks for updates.

There should be a plasma-integration thing for snaps, I think, just like there is for the system, or you have to tell it to use the correct portal, just like it is done elsewhere. I just don’t yet know what to look for.

Also, there might be a setting in the application for this, if I recall – I don’t have it installed on this PC at the moment.

you need to install the discover - flatpak backend for flatpaks to appear under the sources menu

That’s what the button I showed does.

This just in; after a full reinstall of Kubuntu (in order to attempt to and fail to fix another issue), I attempted to install Krita using Flatpak after installing the discover-flatpak backend and enabling flathub as a source.

Concerningly enough, Flatpak apps don’t prompt the user to log in as admin in order to install apps; while 5.2.11 was installed, I was concerned for a good while that it wasn’t actually installing anything.

Oddly enough, though, it still had native file dialogues unselected– and selecting it produced… this???

I’m now EXTREMELY confused, this is a THIRD file picker that’s somehow WORSE than the first one???

Installing it via Snap instead produced 5.2.11-prealpha (which… explains how the fuc 5.2.11-prealpha ended up preinstalled in the first place; it grabs the Krita installation from Snap).

This has the issues mentioned prior, but also a new issue– namely, if I attempt to open a file via the native file dialogue (which at the very least is the ACTUAL native file dialogue–)

the entire program will lock up if the file picker is closed for any reason, from “hit the X button at the top” to “actually select a file”. This is not an issue with the non-native file picker. It locks up so bad that I need to open up System Monitor to end the Krita process.

I guess I’m going back to 5.2.2 lol

also if it’s not clear this thread is now VERY MUCH in the wrong category, this isn’t brainstorming so much as a Help thread crossed with a bug report thread

Changed to Help tag

That is the GTK file picker. This might mean you’re missing the package xdg-desktop-portal-kde, which is what usually allows flatpaks to use the right file picker.

Otherwise this sounds like it might be https://bugs.kde.org/show_bug.cgi?id=506926 ?

Also they look adorable :smiley:

Definitely not missing that package then. Looks like I’ll be avoiding flatpak because I do think that that bug is in play, ah well.

Also

(And thank you for fixing the category too :3 )

1 Like