Bug 426785

Summary:	Krita always exits with Critical error. Cannot log into bug reporter.
Product:	[Applications] krita	Reporter:	andreimiculita
Component:	General	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	halla
Priority:	NOR
Version First Reported In:	4.2.9
Target Milestone:	---
Platform:	Mint (Ubuntu based)
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description andreimiculita 2020-09-20 19:15:28 UTC

SUMMARY
When exiting Krita 4.2.9, it always sends the notification "Krita closed unexpectedly". It is also not possible to report from the bug reporter.

STEPS TO REPRODUCE
1. Open Krita.
2. Close Krita.
3. Krita will send the notification "Krita closed unexpectedly".
4. Report bug, go into reporting assistant. Reporting assistant cannot be alt-tabbed to or minimized - this is happening as I am writing this bug report.
5. Select yes, "every time", check all boxes (note that if "custom settings" is not checked, a backtrace will still be generated in the next step, only to later be told that the report does not contain enough information).
6. Proceed to login with kde credentials (this is more of a general complaint but requiring someone to make an account just to report a bug will strongly discourage bug reporting).

OBSERVED RESULT
Error when trying to login: /[300] The login or password you entered is not valid./ 

If locked out of account after 3 wrong attempts, the error message is more cryptic (I can't lock myself out right now).

EXPECTED RESULT
Using the same credentials, I logged into bugs.kde.org successfully.

SOFTWARE/OS VERSIONS
Linux Mint 20
Cinnamon 4.6.7

Qt Version: 5.12.8

ADDITIONAL INFORMATION

Comment 1 Halla Rempt 2020-09-20 20:42:53 UTC

No, bugs.kde.org is not connected to the kde identity system, it needs a separate account for that.

Please update to the Krita 4.3.0 appimage or test the latest stable nightly build (https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/) -- instead of using a 4.2.9 distribution package.

Your distribution is repsonsible for making the crash handler work correctly; I am not sure whether that works with mint.

Comment 2 andreimiculita 2020-09-21 16:32:25 UTC

Right, everything's working properly in 4.3.0. Turns out the Mint Software Center version is just out of date :( Sorry for the bother.