Bug 486379

Summary: When opening Krita it gives me a black screen and a pop-up saying "Your application encountered a fatal error and cannot continue." and then closes.
Product: [Applications] krita Reporter: 499671
Component: * UnknownAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: halla
Priority: NOR    
Version First Reported In: 5.2.2   
Target Milestone: ---   
Platform: Android   
OS: ChromeOS   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description 499671 2024-05-01 05:35:24 UTC
SUMMARY
Krita crashes when trying to be opened and is unusable.

STEPS TO REPRODUCE
1.  Download google play version of Krita
2.  Open it

OBSERVED RESULT
It crashes

EXPECTED RESULT
It opens normally

SOFTWARE/OS VERSIONS
ChromeOS: Version 122.0.6261.137 (Official Build) (64-bit)

ADDITIONAL INFORMATION
I have checked the forums and this has been happening to everyone using the google play version of krita for about a month now.
Comment 1 Halla Rempt 2024-05-01 06:43:17 UTC
It happened to about 5% of people, according to Google Play Console. We released an update yesterday that should fix the problem, though. Now all depends on Google's review process and roll-out process so people get the updates. My own test device is still on 5.2.1 because of the roll-out alogorithm -- which we cannot influence.
Comment 2 499671 2024-05-11 07:37:59 UTC
(In reply to Halla Rempt from comment #1)
> It happened to about 5% of people, according to Google Play Console. We
> released an update yesterday that should fix the problem, though. Now all
> depends on Google's review process and roll-out process so people get the
> updates. My own test device is still on 5.2.1 because of the roll-out
> alogorithm -- which we cannot influence.

The same problem is still happening
Comment 3 499671 2024-05-11 07:39:06 UTC
(In reply to Halla Rempt from comment #1)
> It happened to about 5% of people, according to Google Play Console. We
> released an update yesterday that should fix the problem, though. Now all
> depends on Google's review process and roll-out process so people get the
> updates. My own test device is still on 5.2.1 because of the roll-out
> alogorithm -- which we cannot influence.

The same problem is still happening