*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. open krita 2. select past file from Open file dialog 3. click to open OBSERVED RESULT krita crashes on some files and doesn't crash on others, in particular image projects seem to open fine, animated ones crash EXPECTED RESULT any random opened past file opens no problem SOFTWARE/OS VERSIONS Ubuntu Mate 24.04.4 LTS Jammy main desktop is mate Krita is from snap ADDITIONAL INFORMATION $ snap info krita name: krita summary: Digital Painting, Creative Freedom publisher: Stichting Krita Foundation (krita✓) store-url: https://snapcraft.io/krita contact: https://krita.org/en/get-involved/overview/ license: unset description: | Krita is the full-featured digital art studio. It is perfect for sketching and painting, and presents an end–to–end solution for creating digital painting files from scratch by masters. Krita is a great choice for creating concept art, comics, textures for rendering and matte paintings. Krita supports many colorspaces like RGB and CMYK at 8 and 16 bits integer channels, as well as 16 and 32 bits floating point channels. Have fun painting with the advanced brush engines, amazing filters and many handy features that make Krita enormously productive. commands: - krita snap-id: r8Shy9i0XE50a3tUlChg3tvjSeLGJ4Za tracking: latest/stable refresh-date: today at 16:55 EET channels: latest/stable: 5.2.2 2024-03-29 (100) 504MB - latest/candidate: 5.2.2 2024-03-29 (100) 504MB - latest/beta: ↑ latest/edge: ↑ installed: 5.2.2 (100) 504MB -
Hi, have you tried to reproduce with the AppImage distributed by the Krita team on https://krita.org/en/download/ ? It might be an issue in the way the Snap is built (eg. not building well the module that can decompress stored data on Krita files). By testing the reproducibility with the official AppImage, it will remove this possibility from the list of probably culprit.
I'm not sure installing AppImage on this machine is a good idea. Nevertheless, I have uninstalled snap to try the APT version at least, only to learn there are only VERY outdated apt versions in backports like 5.0.2. I have installed snap again and now it starts and immediately crashes after I see briefly splash picture. If I start it from the command line, the console output looks like this: $ krita Qt: Session management error: Could not open network socket libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs '23.2.1-1ubuntu3.1~22.04.2') libGL error: failed to load driver: iris libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs '23.2.1-1ubuntu3.1~22.04.2') libGL error: failed to load driver: iris libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs '23.2.1-1ubuntu3.1~22.04.2') libGL error: failed to load driver: swrast libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs '23.2.1-1ubuntu3.1~22.04.2') libGL error: failed to load driver: iris libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs '23.2.1-1ubuntu3.1~22.04.2') libGL error: failed to load driver: iris libGL error: DRI driver not from this Mesa build ('23.0.4-0ubuntu1~22.04.1' vs '23.2.1-1ubuntu3.1~22.04.2') libGL error: failed to load driver: swrast Qt: Session management error: Could not open network socket Invalid profile : "/snap/krita/100/usr/share/color/icc/colord/Crayons.icc" Invalid profile : "/snap/krita/100/usr/share/color/icc/colord/x11-colors.icc" Cannot mix incompatible Qt library (5.15.11) with this library (5.15.12) Aborted (core dumped) It says there is coredump but it's certainly not in the usual place of /var/crash so I can't provide it. And /snap sub-tree doesn't have it either $ ll /snap/krita/current/var/ total 0 drwxr-xr-x 3 root root 26 maalis 29 10:49 ./ drwxr-xr-x 13 root root 195 maalis 29 10:49 ../ drwxr-xr-x 3 root root 27 maalis 29 10:49 lib/ I would like to avoid AppImage as in the past they were poorly behaving on this system.
> I would like to avoid AppImage as in the past they were poorly behaving on this system. Hi, unfortunately, this is the only official package provided by the Krita team for the Linux users. It is beta-tested and reduce the amount of bugs. All other packages are community based... You don't have to install the AppImage. Just download it from krita.org, then right click to make it executable and double-click the file to launch Krita. That's all, you can use this just to compare if the issue you have is Snap specific.
if you look at console lines, it looks like snap package has just used the wrong (previous) libraries so all that is needed is to inform the proper package manager but if I understood you correctly, it's not the KDE or Krita team, that builds snap images problem is that Snapcraft points https://snapcraft.io/krita me to Krita's 'get involved' page https://krita.org/en/get-involved/ which literally goes here :) can you help me to find where to (re)file the bug/issue again so they can build it normally or fix it?
Maybe try getting a crashlog. Help -> Show Krita log for bug reports might contain it (when you get some kind of Krita that works: appimage, or maybe a flatpak, or figure out how to fix that snap version). And this: > Cannot mix incompatible Qt library (5.15.11) with this library (5.15.12) Sounds like a snap/system configuration problem, not something in Krita at all. You should ask for help someone who knows how snaps operate (I don't) and what's the deal with the mismatched libraries and how to fix that. Most likely, you can just remove the system Qt libraries you installed to install that old Krita version - but why would a snap version require you to remove system libraries to work, I don't know.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!