Using Manjaro 26.1.0, Gnome, Wayland, Kernel ver 6.18.38-1. This started happening after the latest Stable update on July 11th. Hadn’t experienced it before then.
After drawing in Krita with a Wacom tablet for any amount of time, everything suddenly hangs for a second and then I am thrown back to the login screen. Krita’s logs don’t seem to show anything out of the ordinary; there is no apparent difference in logs between a normal save/close and an abnormal one. System logs show the below. Seems to be something about libmutter-clutter. I am using Wayland and several error messages mention it.
Is anyone else experiencing this? Any ideas how to diagnose/workaround? Tried all kinds of searches and found nothing useful.
To reproduce:
I can usually get this to happen by having a site in Firefox playing a video on the other screen, full screen.
Can’t stream; having OBS and Firefox open also reliably produces the crash when I use the stylus to focus back on Krita.
inxi:
CPU: 6-core AMD Ryzen 5 3600 (-MT MCP-) speed/min/max: 2200/2200/4208 MHz
Kernel: 6.18.38-1-MANJARO x86_64 Up: 25m Mem: 3.53/62.71 GiB (5.6%)
Storage: 2.28 TiB (16.1% used) Procs: 403 Shell: Zsh inxi: 3.3.41
System log at crash time:
4:54:49 PM kernel: gnome-shell[2597]: segfault at 0 ip 00007f3899e05134 sp 00007fffae0fe628 error 4 in libmutter-clutter-18.so.0.0.0[6b134,7f3899dbd000+c1000] likely on CPU 5 (core 6, socket 0)
4:54:49 PM kernel: Code: 84 00 00 00 00 00 f3 0f 1e fa 48 8b 07 48 8b 80 b8 00 00 00 48 85 c0 74 05 ff e0 0f 1f 00 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa <48> 8b 07 ff a0 98 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 48 8b 80
4:54:49 PM systemd-coredum: Process 2597 (gnome-shell) of user 1000 terminated abnormally with signal 11/SEGV, processing...
4:54:49 PM systemd: Created slice Slice /system/systemd-coredump.
4:54:49 PM systemd: Started Process Core Dump (PID 73715/UID 0).
4:54:49 PM systemd: Started Process Core Dump (PID 73715/UID 0).
4:54:51 PM systemd-coredum: Process 2597 (gnome-shell) of user 1000 dumped core.
Process 2597 (gnome-shell) of user 1000 terminated abnormally with signal 11/SEGV, processing…
Gnome crashed, that’s why your entire session ended. Krita can’t end your session and may not have anything to do with it, it could just be a tablet input handling bug or something.
You can try downgrading your Gnome packages or using a different window manager. You can also try reporting this problem to Gnome, they are often very nasty, but a straight crash like this should hopefully be safe.
Also, obligatory note: Krita 6 is not stable. What Arch and Manjaro is giving you is broken. Consider using the AppImage from krita.org instead. Probably won’t fix this Gnome crash, but avoids many other problems.
Oh hey, are you the original Drawpile dev? We talked a long time ago back when Drawpile first started.
Today was a big Manjaro update that included Krita. This update fixed one other bug that dealt with resizing dockers, but did not fix this bigger bug.
I’ve been wondering about that ever since they started packaging that version. Pretty discouraging to hear. One of the things that drew me to Manjaro was their handling of repos. I haven’t had to use snap, flatpak, appimages,etc, nor have I ever had to downgrade, and I hoped I would never have to.
Tried out the Krita 5.3.2.1 Appimage just now. Was happy to see that all the layout and preferences were kept – that was my main concern. Unfortunately the combo of OBS+Rhythmbox+Firefox+Krita and hovering the stylus over the tablet caused gnome-shell to crash again, libmutter again at fault.
EDIT: In fact, the crash happened even when Krita was not running, just OBS+Rhythmbox+tablet. So it does look like Krita is not to blame for this one.
I guess I’ll look at different window managers, though X is no longer supported, and installing multiple DE’s is an absolute mess…
Thanks for your thoughts!
No, I took over its development a few years ago from the original developer!
And yeah, if switching to a different window manager is a feasible option, it’s probably worth doing. I think KDE probably has the best tablet support out of the window managers on Wayland, in some respects probably better than on X at this point. Although the others tend to have very little in the way of support and in particular Gnome seems to break it a lot, but that may also be just skewed perception because of how popular it is.
I found out that my issue is the same as the one posted here: Gnome Display Manager crashes when using wacom tablet during online platform screen sharing - Fedora Discussion
I applied the prescribed fix (rolling back Mutter 50.3 to 50.1) and it seems to have solved it. Streamed drawing for an hour with no issues.