Getting Krita logs

There are three different kinds of logs that Krita can produce. Depending on the issue, you might be asked for a specific one or for all of them. This page will tell you how to gather the necessary information to give to Krita developers or user supporters.

  1. Krita Usage Log – this log contains your last 10 Krita sessions (one session means opening Krita). 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.

  2. System information – this is not exactly a log, but a file that contains detailed system information related to Krita.

  3. Crash log/backtrace – this log is created when Krita closes incorrectly because of an internal issue. This log is often necessary to get the issue fixed if developers cannot reproduce issue (repeat steps to get the crash).

  4. Krita console output/Log Viewer output/DebugView output – this log contains anything random that Krita felt the need to report. It often contains some useful additional information that can help solving the issue.

Krita Usage Log

Through GUI

The easiest way to get Krita Usage Log is through Krita’s GUI. Go to Help ‣ Show Krita Log for bug reports. A new dialog will open, showing the content of the log.

Changed in version 4.2.9: In versions 4.2.0-4.2.9, Krita Usage Log is accessible through Help ‣ Show system information for bug reports. Note that for Krita versions 4.1.7 and below, no usage log is available and the menu entry only contains system information.

From the file system

Sometimes however it is not possible to use Krita’s GUI, for example when it doesn’t even open. Since logs are regular text files, you can get them from your file system by yourself.

The file is called krita.log. Location of the file:

Linux

$HOME/.local/share/krita.log

Windows

%LOCALAPPDATA%\krita.log

MacOS X

$HOME/Library/Application Support/krita.log

Note

In Windows you can simply paste this path into the Windows Explorer’s search box, on the top bar, and it will find the file for you.

Crash log and backtrace

Location and the way to get a backtrace is different on all systems.

Windows

Follow closely Dr. Mingw debugger guide.

Linux

On Linux it’s recommended to use gdb.

  1. Open Krita in gdb:

    # if you have Krita installed from repositories, you may need to only write 'gdb krita'
    # if not, write the path to the executable file
    gdb path/to/krita
    
  2. Disable pagination:

    set pagination off
    
  3. Run Krita:

    run
    
  4. Make it crash.

  5. Get the short backtrace:

    thread apply all bt
    
  6. Get the long backtrace:

    thread apply all bt full
    
  7. Short and long backtraces save to separate text files.

  8. From the short backtrace, it’s recommended to cut out all threads that are identical to some others or don’t seem to hold any additional information.

    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. Both backtraces still will be needed: attach them to the bug report as well.

    If you prefer not to make this decision, just attach both files with backtraces to the bug report.

Mac

On Mac it’s recommended to use lldb.

  1. Open Terminal.app

  2. Open Krita in lldb:

    lldb /Applications/krita.app/Contents/MacOS/krita
    
  3. Run Krita:

    run
    
  4. Make it crash.

  5. Get the backtrace:

    thread backtrace all
    
  6. Save the backtrace to a text file.

  7. From the backtrace it’s recommended to cut out all threads that are identical to some others or don’t seem to hold any additional information to put into the comment (so it’s easily accessible for the developer).

    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. The full backtrace still will be needed: attach it to the bug report as well.

    If you prefer not to make this decision, just attach the file with the backtrace to the bug report.

Krita’s text output

Most of Krita’s text output can be gathered using Log Viewer. 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.

Through GUI

  1. Go to Settings ‣ Dockers ‣ Log Viewer.

  2. The first button from the left enables and disables logging, so make sure it is pressed.

  3. Do the thing you want to get the output of.

  4. Use the third button (tooltip says: Save the log) to save the log to a file.

  5. Attach the file to the bug report.

From the console

Using the console is the most reliable way to get Krita’s text output. This way is similar on Mac and Linux. Unfortunately, it’s not possible on Windows. To check Windows’ equivalent, see DebugView guide.

  1. On Mac open Terminal.app, on Linux open your favourite terminal or console application.

  2. Write the path to the Krita executable.

    # On Linux, if installed from repositories:
    krita
    # On Linux, in all other cases:
    #  (remember that if you want to reference a file from the directory
    #   you're currently in, you need to write: './krita_filename' instead of 'krita_filename'
    #   and remember that this file need to have execution rights to be executed)
    path/to/krita
    # On Mac:
    /Applications/krita.app/Contents/MacOS/krita
    
  3. Do the thing you want to get the output of.

  4. Copy the content, save to a file and attach to the bug report.

From the DebugView

To get the text output of Krita on Windows, you need an external program called DebugView.

  1. Download DebugView if you haven’t already. Click on the blue bold Download DebugView text with underline, downloading should start immediately.

  2. The file you download is a .zip archive. Windows 10 has a zip archive opener already included. Just extract all of the files somewhere. You can learn more about extracing on Windows extracting manual page.

  3. There is a file inside the archive that is called DbgView.exe (which you can see as DbgView, depending on your system settings). Double-click on it.

  4. Let the program run and open Krita.

  5. Do things you want to get output of.

  6. Switch to DebugView and copy the content. Save to a file and attach to the bug report.