I have followed the instructions on the main website, tried the appimage and snap, and also go over threads on this website to fix this.
The version from the ubuntu app store (that the main website suggests I use), crashes when I open a new image. All of the recent reviews also say it does not work for them. The snap version crashes at the same place.
When I use the appimage and change the permissions, it just does nothing.
This is the last thing I can think of. I’m not sure if it just is no longer supported on Ubuntu.
Right clicked on the downloaded file and opened properties to edit the permissions to make it an executable and then you closed the properties. Then you double click on that executable appimage and nothing happens?
I also have Ubuntu and Krita works fine.
Maybe try installing it using Flatpak in the app store cause that’s how I installed it.
And I tried the appimage for some reason it wont run in Ubuntu…
Currently there is no other official release other that from Krita.org. All others, like FlatPak or from the Ubuntu repository (all the stuff you probably find in Ubuntu’s Software Center / App Store) are maintained by other people.
On my TuxedoOS (basically Kubuntu) the AppImage from the website works fine.
When using FlatPak (not recommended) make sure all FaltPak-Permissions are set correctly (most importantly file and device access).
If you could send us the crash log, that would perhaps help us see what’s the Issue.
Some log files can be viewed directly from Krita’s Help menu. More sophisticated logging:
Yes I did. I tried editing the properties via the terminal first. It didn’t work so I fully uninstalled (and verified) and then downloaded the appimage again and changed the settings via the properties menu.
I tried opening it by double clicking it, right clicking it and selecting “run”, and using the terminal.
It’s not failing or partially opening. I get a spinning wheel on my cursor for a second and then nothing.
I started with the appimage from Krita’s site. After about 40 minutes of trying to get that to work, I went through the documentation on Krita’s site that mentioned downloading through the Ubuntu Software Center. I also tried to download using snap.
The appimage failed silently with no errors (though I can dig through the logs and see if I can find anything). The version from the Ubuntu Store and Snap opened initially and then failed when I tried to make a new document.
I can post logs in a bit. I have a Christmas thing this morning though.
Download the official Linux 64-bit AppImage from krita.org
Open the terminal and cd to the directory with the appimage
Add the run permission chmod +x krita-5.2.6-x86_64.appimage
Run the appimage ./krita-5.2.6-x86_64.appimage (take note of the ./ at the beginning)
(sorry if I’m explaining something super basic to you)
If you run it this way, and anything goes wrong, you should see useful feedback like the error messages in the console. If you do get any, paste them here and we can try to debug the problem further.
I appreciate the concern about over explaining, but I also appreciate the exact directions. I work in Linux a lot, but I’m very dyslexic. Having an extra clear reference for spelling is awesome!
I’m planning on testing the solutions everyone has been suggesting tonight and I’ll update the thread with what worked and didn’t. I probably am missing a very small step or something!
It could be the case of version differences. Like one version of Ubuntu could have libfuse2, another could be on libfuse3. I had such problem before with other libraries.
Yes, an AppImage is a filesystem that is mounted with FUSE, so it’s impossible to open them without it (except for unpacking the FS and running the executable directly).
The thing is that fuse is not a dependency for any specific app image but for the format in general. According to the wiki fuse should be part of all major distros since it is used for mounting stuff (not only AppImages) and from my own experience if its version 2 or 3 of a library doesn’t really matter as long as the ABI is the same. It’s like you can’t really burn a CD in a way that a computer without a drive can read it, when there is nothing you could put the disk in, the same way you can’t make an AppImage that works without fuse since it is out of control of the Application how it is put into the file system.
I checked this quickly in my WSL2 which is Ubuntu 24.04.1 based. I’m getting the same error and there’s already libfuse3-3 installed in the system (I presume, by default). So the issue here is that Krita appimage expects to work with libfuse2 specifically and will fail because of it.
This actually is a widespread issue with AppImage, for example see here:
I think we can resolve this problem by linking a static runtime, as described in that issue thread.
So it’s an issue with the tool that creates the AppImages. The problem with static linking directly to fuse2 is it wouldn’t work with fuse3 anymore, which seems to be exactly the problem OP has since they had to install fuse2 manually. Normally fuse2 and 3 are designed to be installed alongside each other and the AppImage should use whichever is there. Since it doesn’t, I assume it’s already hardlinked. We should perhaps ping one of the devs to get more insight or put this in the bug tracker?
