![]() Registered Member ![]()
|
Hi, I'm working with the 64-bit AppImage, downloaded from the official site. The app occasionally crashes at random. It doesn't seem tied to specific tasks or time passed.
Ran it through a terminal to see if I could catch any error messages. A see a couple of messages being spammed continuously, and the last lines before the app closed was:
System specs are as follows:
I'm unsure if this is a bug with Krita in itself, or just some quirk in my current system setup. Many thanks! |
![]() KDE Developer ![]()
|
That looks pretty weird. The appimage isn't built with support for accessibility, yet that's where a crash is happening, and Ubuntu 16.04 is known to have a broken Qt when it comes to accessibility... But the appimage doesn't use the system's Qt. Right now, I haven't got any idea what might be going on, but you could try to remove Qt's accessibility package from your system and see if that helps.
|
![]() Registered Member ![]()
|
Thanks, I'll try to purge it. It might be a red herring, though, I got another crash without the preceding calls to QAccessibleTable:
The QIODevice is one of those messages that get spammed to the console continuously, so I doubt it contributes to the crashes, though I guess it support the theory that the AppImage tries to use older Qt packages lingering on the system. |
![]() KDE Developer ![]()
|
Um... You probably should disable performance logging.
|
![]() Registered Member ![]()
|
Aha, that's what that is, thanks! Ok, I've been running Krita a couple of times now (for multiple hours) after purging any lingering Qt-package I could find on my system, and I've thus far not encountered any segmentation faults (or other sudden app crashes). If you're interested in gathering info on AppImages conflicting with system Qt-packages, I'm happy to help out. If not, I've marked this thread as solved. Thank you very much for your feedback! ![]() |
![]() KDE Developer ![]()
|
Yes, we really should have a bug for this on bugs.kde.org with as exact a list as possible of what Qt packages you had got installed.
|
![]() Registered Member ![]()
|
Editing this post since my latest crash introduced a call to QAccessibleTable again.
I have not reinstalled the Qt-packages. I'm closing this thread in favour of the bug report at https://bugs.kde.org/show_bug.cgi?id=388495. |
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]