If you cannot open Krita because it crashes on startup, please provide the /Android/data/org.krita/files/kritacrashlog.txt. To get the logs using the GUI, share the content of Help ‣ Show crash log for bug reports. If you prefer not to make this decision, just attach the file with the backtrace to the bug report. The full backtrace still will be needed: attach it to the bug report as well. If you feel like you know which part of the backtrace is the most important (it’s usually the longest thread), then cut it out and put this fragment in the bug report in a comment. It often contains some useful additional information that can help solving the issue. Krita console output/Log Viewer output/DebugView output – this log contains anything random that Krita felt the need to report.
This log is often necessary to get the issue fixed if developers cannot reproduce issue (repeat steps to get the crash). System information – this is not exactly a log, but a file that contains detailed system information related to Krita.Ĭrash log/backtrace – this log is created when Krita closes incorrectly because of an internal issue. It shows times when you opened it, basic information about your system and Krita, and all files you created, opened and saved, including all auto-saves. Krita Usage Log – this log contains your last 10 Krita sessions (one session means opening Krita).
#Krita keeps crashing after trying to load an image how to#
This page will tell you how to gather the necessary information to give to Krita developers or user supporters.
Depending on the issue, you might be asked for a specific one or for all of them. There are three different kinds of logs that Krita can produce.
0 kommentar(er)
