Bug 410042

Summary:	Krita has encountered an internal error:
Product:	[Applications] krita	Reporter:	rissa <ciesta.rissa>
Component:	Usability	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	griffinvalley, halla, korotkih.00, ReneeAKhan09
Priority:	NOR
Version:	4.2.3
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	error window

Description rissa 2019-07-20 18:05:52 UTC

SUMMARY
Krita has encountered an internal error:


Krita has encountered an internal error:

SAFE ASSERT (krita): "!m_d->readyShortcut" in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\libs\ui\input\kis_shortcut_matcher.cpp, line 579

Please report a bug to developers!

Press Ignore to try to continue.
Press Abort to see developers information (all unsaved data will be lost)

I'm using windows 10 and that message keeps coming up since I've updated to 4.2.3. Please help

Comment 1 rissa 2019-07-20 18:19:15 UTC

it only shows up on the latest version 4.2.3

Comment 2 WOAS 2019-07-26 08:50:31 UTC

Created attachment 121739 [details]
error window

yeah, I get the same thing sometimes and the app crashes

Comment 3 Ray 2019-07-31 09:46:34 UTC

this bug occurred about every 15 minutes for me for 2 days and would always show up after a previous popup which says 'waiting for image operation to complete.' After I try clicking 'x' or 'cancel', the popup which says internal error would occur. With only 2 options of 'Ignore' or 'Abort,' if I clicked either of them, the 'image operation' one would show again, then later close krita completely and all unsaved work would be lost :( Please fix this as best as you can!! Thanks for all of your hard work !! Very appreciated :)

Comment 4 Halla Rempt 2019-07-31 09:54:51 UTC

Could you please check whether the 4.2.4 release we just did (https://krita.org/en/item/krita-4-2-4/) fixes this for  you?

Comment 5 wolthera 2019-08-02 10:40:41 UTC

Setting this to waitingforinfo, please check 4.2.4 or higher (we're even releasing a 4.2.5 today!)

Comment 6 rissa 2019-08-02 12:50:02 UTC

(In reply to wolthera from comment #5)
> Setting this to waitingforinfo, please check 4.2.4 or higher (we're even
> releasing a 4.2.5 today!)

The updates fixed the bug! Thank you so much!!