![krita update 3.0.1.1 krita update 3.0.1.1](http://ultimateedition.info/Ultimate_Edition_3.0/3theme.png)
Windows 10 has a zip archive opener already included. Click on the blue bold Download DebugView text with underline, downloading should start immediately. Compared to using the console, DebugView has the benefit of including timestamps to the log entries.ĭownload DebugView if you haven’t already. To get the text output of Krita on Windows using the graphical program, you need an external program called DebugView. "C:\Program Files\Krita (圆4)\bin\"Ĭopy the content, save to a file and attach to the bug report. REM On Windows: REM By default, cmd.exe will prefer running the. Using the console is the most reliable way to get Krita’s text output. Use the third button (tooltip says: Save the log) to save the log to a file. The first button from the left enables and disables logging, so make sure it is pressed.ĭo the thing you want to get the output of. The only exception are messages from when Krita is starting up, so there is no GUI yet, or when it closes or crashes so no user interaction is possible after the event. Most of Krita’s text output can be gathered using Log Viewer. If you prefer not to make this decision, just attach the file with the backtrace to the bug report.
![krita update 3.0.1.1 krita update 3.0.1.1](https://storage.deepin.org/forum/201612/06/105343b3xa2c8y8drar3di.png)
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 update 3.0.1.1 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.