Krita Flatpack crashes (fixed now) when opening a file dialogue

Hi there,

I’m using Krita 5.2.2 installed via Flatpak on Linux Mint 21.3.
Today it started crashing / closing on me as soon as I open a file browser dialogue, e.g. when using “File > Open” or “Layer > Import > Import Layer”.
The error message looks like this:

(krita:2): GLib-GIO-ERROR **: 14:01:03.051: No GSettings schemas are installed on the system

The Appimage version runs fine. I’d prefer the Flatpak installation though, it ran absolutely fine before.

EDIT: Dragging and dropping images to add them as layers or opening them works fine with the Flatpak version, too. It’s just the File Browser that crashes.

There’s a bug report matching this here: 484060 – The Flatpak version of Krita 5.2.2 crashes when I try to use the "Save as" option
(As noted there, the Appimage is the only offically supported version of Krita on Linux, this issue should be reported to the Flatpak’s maintainers.)

Do you have Configure Krita->General->Miscellaneous->Enable native file dialogs enabled? If so, try disabling it.

Thanks a lot for the quick response.
The description of the bug you sent matches perfectly fine with what I’m getting here. I will investigate further over there.

I already had the hope that using native file dialogues could band-aid that problem but sadly to no avail. Same crash. But at least I’m not alone and I hope a fix is on the way.

Thanks again. :innocent:

Started having exactly the same problem with Flatpak version. You can not Export and Save either. And i really need it to finish work …

Hello @SreckoM and welcome to the forum :slight_smile:

Have you tried following the advice given earlier in this topic?

Hello,

I have Linux Mint 21.3 Cinnamon. Krita version (Krita (flatpak) 5.2.2)

Krita (Flatpak) closes as soon as I select “save as”.

The programme starts without any problems. Loading an image file is also no problem.

This problem only started yesterday. Presumably this has to do with an update.

If I install the normal (not flatpak / system package) Krita, “save as” works again without any problems. However, Krita is set to American English and cannot be changed. Neither in Krita itself under “switch application language”, nor the system-wide changes to the language settings under Settings → Language (in Linux itself) work here.

To test whether this has to do with admin rights, I wanted to open Krita via the terminal. But only the normal Krita works here. Krita (flatpak) cannot be found there.

On my laptop, which I haven’t updated since about January, Krita 5.2.2 still works with “save as” without any problems.

Does this possibly have to do with KDE?

Here is my error message:

KRITA DID NOT CLOSE CORRECTLY

================================================================================

SESSION: 22 Mar 2024 07:49:58 +0100. Executing krita

Krita Version: 5.2.2, Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 2


22 Mar 2024 07:49:58 +0100: Style: fusion. Available styles: Windows, Fusion

22 Mar 2024 07:49:59 +0100: Database is up to date. Version: 0.0.17, created by Krita 5.1.0, at Di. Aug. 23 08:54:02 2022

22 Mar 2024 07:50:01 +0100: Importing image/png to application/x-krita. Location: /home/phenom/Bilder/Bildschirmfoto vom 2024-03-21 14-01-02.png. Real location: /home/phenom/Bilder/Bildschirmfoto vom 2024-03-21 14-01-02.png. Batchmode: 0

22 Mar 2024 07:50:01 +0100: Loaded image from image/png. Size: 1920 * 1080 pixels, 1 dpi. Color model: 8-bit Ganzzahl pro Kanal RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2

KRITA DID NOT CLOSE CORRECTLY

================================================================================

SESSION: 22 Mar 2024 08:05:08 +0100. Executing krita

Krita Version: 5.2.2, Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 2


22 Mar 2024 08:05:08 +0100: Style: fusion. Available styles: Windows, Fusion

22 Mar 2024 08:05:09 +0100: Database is up to date. Version: 0.0.17, created by Krita 5.1.0, at Di. Aug. 23 08:54:02 2022

22 Mar 2024 08:05:24 +0100: CLOSING SESSION

================================================================================

SESSION: 22 Mar 2024 08:08:24 +0100. Executing krita

Krita Version: 5.2.2, Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 2


22 Mar 2024 08:08:24 +0100: Style: fusion. Available styles: Windows, Fusion

22 Mar 2024 08:08:25 +0100: Database is up to date. Version: 0.0.17, created by Krita 5.1.0, at Di. Aug. 23 08:54:02 2022

22 Mar 2024 08:12:02 +0100: Importing image/png to application/x-krita. Location: /home/phenom/Bilder/Bildschirmfoto vom 2024-03-21 14-01-02.png. Real location: /home/phenom/Bilder/Bildschirmfoto vom 2024-03-21 14-01-02.png. Batchmode: 0

22 Mar 2024 08:12:02 +0100: Loaded image from image/png. Size: 1920 * 1080 pixels, 1 dpi. Color model: 8-bit Ganzzahl pro Kanal RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2

KRITA DID NOT CLOSE CORRECTLY

================================================================================

SESSION: 22 Mar 2024 08:12:10 +0100. Executing krita

Krita Version: 5.2.2, Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 2


22 Mar 2024 08:12:10 +0100: Style: fusion. Available styles: Windows, Fusion

22 Mar 2024 08:12:10 +0100: Database is up to date. Version: 0.0.17, created by Krita 5.1.0, at Di. Aug. 23 08:54:02 2022

Hello @Humboldt and welcome to the forum :slight_smile:

I’ve moved your post to a more appropriate topic. You initially posted in a topic about a problem on Windows.

Please read the posts in this topic. It seems to be a Flatpack problem.
Try using the appimage.

Hello,

Unfortunately, your suggestion did not work for me.

Have you tried using the appimage?

The Appimage works, but I still wait for a Flatpak fix, because I don’t want to migrate all plugins and settings etc.

I received a notification from another place where users experience the same crash and the fix is here elements/components/glib.bst: fix manifest syntax (!18580) · Merge requests · freedesktop-sdk / freedesktop-sdk · GitLab
I don’t know when it will be merged or when we’ll receive the updates.

And it’s working again :slight_smile:

Back to work…

Perfect. Thanks all.