STEPS TO REPRODUCE 1. open through steam app OBSERVED RESULT the "launch" button goes to "stop" and almost instantly goes back to just "launch" and doesnt launch krita EXPECTED RESULT launch krita through steam SOFTWARE/OS VERSIONS Linux/KDE Plasma: fedora kde spin KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION It wont even launch to the art work loading pop up, but works perfectly if i launch with the .sh file or .appimage file in the steam directory. Also it works with proton but then it will have a messy file structure. No launch options are set and I’ve tried reinstalling. Steam is installed as a flatpak if that matters. Other native steam games work fine.
Hi Thomas. Thanks very much for the report, and sorry that you've run into this [really bad] bug. I can confirm this behavior on my Fedora Silverblue (Gnome) laptop as well, where Steam is also installed as a flatpak. I'll have to test to see if this is a problem with non-flatpak install of Steam as well, and I'll post my findings here. Emmet
Ok, so yeah. I've been able to confirm that this seems to be a problem that is relegated to Flatpak Steam installs. As you rightly pointed out, both the 'launch.sh' script and the AppImage itself run without issue. On top of that, I've installed the .deb version of Steam and Krita runs there without issue as well. So, it appears that mounting an appimage while Steam is contained in a flatpak is either broken or impossible right now... We might have to change our approach to distributing Linux binaries through Steam. The best workaround we have right now is to simply run the AppImage itself. Creating a .desktop file, symlinking it elsewhere, or adding it to your PATH may make that less of a hassle. (Also, if you have recently bought Krita on Steam and are disappointed that this bug has nullified the convenience of doing so... First, I'm sorry about that, and second, consider asking for a refund through Steam.) Anyway, sorry again for the nasty bug, and thanks a ton for letting us know and supporting the project in general.
Just a note: here is an upstream report for it: https://bugs.kde.org/show_bug.cgi?id=469116 We need to somehow add an environment variable to our **flatpack** packages of Krita on steam: ``` export APPIMAGE_EXTRACT_AND_RUN=1 ``` The most important thing is that non-flatpack packages of steam should **not** use this variable. I'm not sure if it is possible to implement that though. PS: I've tested this environment variable in the normal docker environment, and it seems to work correctly. **But** it make Krita's startup process a bit slower (due to unpack operation, obviously)
Hi, Emmet! To run the unpacked appimage you need to set up two variables: APPIMAGE=1 APPDIR=/extracted/path ./AppRun
Hi, Thomas! The bug should be fixed now, Emmet has reuploaded the new packaged. Please check if it works for you now :)