As far as I understand it, this is a race condition inside PyQt5 related
to the order of destruction of Python-based QObject instances. Since the
call that trigger the crash is the destruction of the plugin itself
(which in turn stops the Python engine, etc... as your stacktrace
shows), I believe o
Reopening this bug because, with PyQt 5.15.4, PtQt5_sip 12.9 and SIP
6.1, this arose again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874096
Title:
Closing Krita normally always result in "Krit
Git commit a6296beb25c98d9a4b5a136e0088959bf51d550a by L. E. Segovia.
Committed on 18/06/2021 at 15:38.
Pushed by lsegovia into branch 'master'.
Apply the PyKrita workaround to Qt 5.12
This should've been done previously but it was marked as UPSTREAM.
M +2-2plugins/extensions/pykrita/pl
*** Bug 438842 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874096
Title:
Closing Krita normally always result in "Krita closed unexpectedly"
noti
