Summary: | AppImage conflicts with installed Qt libraries | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Linus Larsson <linus> |
Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | minor | CC: | halla |
Priority: | NOR | ||
Version First Reported In: | 3.3.2 | ||
Target Milestone: | --- | ||
Platform: | Appimage | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Linus Larsson
2018-01-03 14:44:28 UTC
I suspect it's the qt-at-spi package that gets loaded dynamically. (In reply to Boudewijn Rempt from comment #1) > I suspect it's the qt-at-spi package that gets loaded dynamically. I got a new crash with preceding calls to QAccessibleTable tonight: QAccessibleTable::child: Invalid index at: 31 0 Cannot creat accessible child interface for object: KisUndoView(0x15bb7f90) index: 31 Segmentation fault (core dumped) qt-at-spi is not reinstalled on the system. The following packages with "qt" in the name is installed on the system: ibus-qt4 install libdbusmenu-qt2:amd64 install libibus-qt1 install libntrack-qt4-1 install libpolkit-qt-1-1:amd64 install libpolkit-qt5-1-1:amd64 install libpoppler-qt4-4:amd64 install libqt4-dbus:amd64 install libqt4-declarative:amd64 install libqt4-designer:amd64 install libqt4-help:amd64 install libqt4-network:amd64 install libqt4-opengl:amd64 install libqt4-qt3support:amd64 install libqt4-script:amd64 install libqt4-scripttools:amd64 install libqt4-sql:amd64 install libqt4-sql-mysql:amd64 install libqt4-sql-sqlite:amd64 install libqt4-svg:amd64 install libqt4-test:amd64 install libqt4-xml:amd64 install libqt4-xmlpatterns:amd64 install libqt5clucene5:amd64 install libqt5core5a:amd64 install libqt5dbus5:amd64 install libqt5designer5:amd64 install libqt5gui5:amd64 install libqt5help5:amd64 install libqt5network5:amd64 install libqt5printsupport5:amd64 install libqt5script5:amd64 install libqt5sql5:amd64 install libqt5sql5-mysql:amd64 install libqt5sql5-sqlite:amd64 install libqt5svg5:amd64 install libqt5test5:amd64 install libqt5waylandclient5:amd64 install libqt5widgets5:amd64 install libqt5x11extras5:amd64 install libqt5xml5:amd64 install libqtassistantclient4:amd64 install libqtcore4:amd64 install libqtcore4:i386 deinstall libqtdbus4:amd64 install libqtglib-2.0-0:amd64 install libqtgstreamer-0.10-0:amd64 install libqtgui4:amd64 install libqtscript4-core:amd64 install libqtwebkit4:amd64 install libtelepathy-qt4-2:amd64 install oxideqt-codecs-extra:amd64 install pinentry-qt install pinentry-qt4 install python-qt4 install python-qt4-dbus install python3-dbus.mainloop.pyqt5 install python3-dbus.mainloop.qt install python3-pyqt4 install python3-pyqt5 install qtchooser install qtcore4-l10n install qtwayland5:amd64 install sni-qt:i386 deinstall I have no idea how that's even possible... (In reply to Boudewijn Rempt from comment #3) > I have no idea how that's even possible... Perhaps the error message is misleading. KisUndoView appear to work with the history docker in Krita: https://searchcode.com/codesearch/view/19399478/ (KisUndoView.h) https://searchcode.com/codesearch/view/19399475/ (KisUndoView.cpp) I have a couple of uneducated guesses: - I've previously had hardware memory related issues, where my Nvidia driver appear to taint the kernel, thus have turned off hardware acceleration in Krita. Could this be hardware related as well; the undo stack is becoming corrupted? - The history docker extension is using deprecated indexing config from a previous Krita install? - Undo stack set too large; or another memory allocation user-side snafu? Can you please check with http://rempt.xs4all.nl/~boud/Krita-4.0.0-beta1-9f3212b-x86_64.appimage -- that's built in a different way. (In reply to Boudewijn Rempt from comment #5) > Can you please check with > http://rempt.xs4all.nl/~boud/Krita-4.0.0-beta1-9f3212b-x86_64.appimage -- > that's built in a different way. Sadly no, I had to write over that Linux partition with another OS in the hopes of acquiring a more stable environ. to work with Krita in. You are welcome to close this ticket as unresolved/could not reproduce. Okay, I guess we'd better do that then. |