Bug 497872 - Krita crashes when creating new image with a Shader Compilation Failure
Summary: Krita crashes when creating new image with a Shader Compilation Failure
Status: RESOLVED DUPLICATE of bug 486596
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: 5.2.2
Platform: Snap Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-24 21:24 UTC by bj
Modified: 2024-12-27 20:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bj 2024-12-24 21:24:26 UTC
SUMMARY
When I create a new image in Krita, it crashes with the following output

Qt: Session management error: Could not open network socket
Qt: Session management error: Could not open network socket
Qt: Session management error: Could not open network socket
Qt: Session management error: Could not open network socket
Invalid profile :  "/snap/krita/104/usr/share/color/icc/colord/Crayons.icc"
Invalid profile :  "/snap/krita/104/usr/share/color/icc/colord/x11-colors.icc"
propsReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.272\" (uid=1001 pid=15281 comm=\"/snap/krita/104/usr/bin/krita \" label=\"snap.krita.krita (enforce)\") interface=\"org.freedesktop.DBus.Properties\" member=\"GetAll\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=653 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")"
nmReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.272\" (uid=1001 pid=15281 comm=\"/snap/krita/104/usr/bin/krita \" label=\"snap.krita.krita (enforce)\") interface=\"org.freedesktop.NetworkManager\" member=\"GetDevices\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=653 comm=\"/usr/sbin/NetworkManager --no-daemon \" label=\"unconfined\")"
"Object path cannot be empty"
QObject::startTimer: Timers cannot have negative intervals
krita.scripting: "Traceback (most recent call last):"
krita.scripting: "  File \"/snap/krita/104/usr/lib/x86_64-linux-gnu/krita-python-libs/krita/__init__.py\", line 11, in <module>"
krita.scripting: "    from .api import *"
krita.scripting: "  File \"/snap/krita/104/usr/lib/x86_64-linux-gnu/krita-python-libs/krita/api.py\", line 15, in <module>"
krita.scripting: "    from PyKrita.krita import *"
krita.scripting: "ModuleNotFoundError: No module named 'PyQt5'"
krita.scripting: "Could not import krita"
QOpenGLShaderProgram: could not create shader program
Shader Compilation Failure:  "Failed to add vertex shader source from file: matrix_transform.vert - Cause: "
Speicherzugriffsfehler (Speicherabzug geschrieben)

NOTE: "Speicherzugriffsfehler" is the german word for Segfault.

STEPS TO REPRODUCE
1. install the Krita 5.0.2 package via apt-get on a vanilla Ubuntu 22.04.2 LTS
2. start Krita from the command line without any arguments
3. In the window that opens, click "New Image" and then "User Defined" and "Create"
4. observe that Krita crashed and find the above output printed in the terminal window.


EXPECTED RESULT
I would have expected that Krita is able to create a new image without crashing.

SOFTWARE/OS VERSIONS
Linux: vanilla Ubuntu 22.04.2 LTS
Qt Version: 5.15.3+dfsg-2

ADDITIONAL INFORMATION
Since the error message "Shader Compilation Failure:  "Failed to add vertex shader source from file: matrix_transform.vert " is the same, this might be related to Bug 486596
Comment 1 Halla Rempt 2024-12-25 12:41:21 UTC
Please update to the latest version of Krita, 5.2.6. It is preferable to use the appimage from krita.org over the snap version since we do not maintain the snap version of Krita.

*** This bug has been marked as a duplicate of bug 486596 ***
Comment 2 bj 2024-12-27 20:15:53 UTC
I tried installing Krita via apt-get (the Ubuntu App Store uses snap by default) and it works. Only the snap version seems to be affected.

Maybe you should
- either make sure that the snap version is properly build (which implies that you are maintaining it)
- or make sure that no one else is publishing broken snap packages in your name [1]

References
[1] https://snapcraft.io/publisher/krita