Hi,
I’m using krita on Nobara OS, after the last update when i try to add text to an image the interface just freezes and nothing responds anymore(it doesn’t crash out right it just stays there doing nothing). When i used this in the past it worked. currently i’m getting pass this by using a plugin to generate speech bubbles (Rogudator’s speech bubble generator).
currently i seem to be on version 5.2.13. not sure at which version i started att but i installed krita at the begining of september late august for the first time
go to help → Show Krita log for bug reports. Go all the way down, then scroll up until you find a session entry that isn’t for Krita 5.2.13, that would be the last version you were using before this one.
However, I am suspecting it was a variation of 5.1, as Nobara is a Fedora based distro, which means it might be anything at all in the new text layout. That in turn means I actually need a backtrace.
Can you try to run krita in gdb? Like the following:
in terminal “gdb krita”
type “y” for yes if it asks you whether to use extra debug info, and “r” for run if it prompts you.
do the things that make krita crash.
when krita has crashed, the terminal window will say something along the lines of krita segmentation error, and then a line.
At this point you will want to type “bt” for backtrace
keep pressing enter until it’s done.
Copy the whole backtrace and share.
Note that at best, I can see if the problem is a font or the like. And fix the bug of course, but I have no idea when it’ll trickle down to the Nobara repositories.
I have krita installed via flatpack so I had to run it like
gdb --args flatpak run org.kde.krita
GDB OUTPUT:
#0 __internal_syscall_cancel (a1=a1@entry=140732413528032, a2=a2@entry=2, a3=a3@entry=-1, a4=a4@entry=0, a5=a5@entry=0, a6=a6@entry=0, nr=7) at cancellation.c:44 #1 0x00007fca092b77a4 in __syscall_cancel (a1=a1@entry=140732413528032, a2=a2@entry=2, a3=a3@entry=-1, a4=a4@entry=0, a5=a5@entry=0, a6=a6@entry=0, nr=7) at cancellation.c:75 #2 0x00007fca0933129e in __GI___poll (fds=fds@entry=0x7ffed18447e0, nfds=nfds@entry=2, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #3 0x000055effcacfa18 in poll (__fds=0x7ffed18447e0, __nfds=<optimized out>, __timeout=-1) at /usr/include/bits/poll2.h:44 #4 monitor_child (event_fd=4, child_pid=48952, setup_finished_fd=-1) at ../bubblewrap.c:539 #5 main (argc=<optimized out>, argv=<optimized out>) at ../bubblewrap.c:3039
I checked the logs as well. it seems i started with version 5.2.13
I deactivated the Rogudator’s Speech Bubble Generator plugin after seeing the log, the interface is no longer freezing now.
the plugin seems to have been the cause.