https://bugs.kde.org/show_bug.cgi?id=420078
--- Comment #4 from Tymond <[email protected]> --- Exactly, but now in the single-instance mode, if Krita sees that another instance of Krita is already open, then it closes, calls the destructor, and the destructor tries to remove stuff from a database that wasn't open because, most probably, the opening calls are further down than checking whether we should close Krita early. So either in destructor or in the removeTemporary... call itself it should check if the database it tries to operate on is open and valid. -- You are receiving this mail because: You are watching all bug changes.
