https://bugs.kde.org/show_bug.cgi?id=388495
Boudewijn Rempt changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=388495
--- Comment #6 from Linus Larsson ---
(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
https://bugs.kde.org/show_bug.cgi?id=388495
Boudewijn Rempt changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=388495
--- Comment #4 from Linus Larsson ---
(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.c
https://bugs.kde.org/show_bug.cgi?id=388495
--- Comment #3 from Boudewijn Rempt ---
I have no idea how that's even possible...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=388495
--- Comment #2 from Linus Larsson ---
(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: Inval
https://bugs.kde.org/show_bug.cgi?id=388495
Boudewijn Rempt changed:
What|Removed |Added
CC||b...@valdyas.org
--- Comment #1 from Boudewij
