diff --git a/doc/qtcreator/images/qtcreator-debugger-general-options.png b/doc/qtcreator/images/qtcreator-debugger-general-options.png
index 7823c7668d9..6ab957dd76a 100644
Binary files a/doc/qtcreator/images/qtcreator-debugger-general-options.png and b/doc/qtcreator/images/qtcreator-debugger-general-options.png differ
diff --git a/doc/qtcreator/src/debugger/creator-only/creator-debugger-settings.qdocinc b/doc/qtcreator/src/debugger/creator-only/creator-debugger-settings.qdocinc
index 3b62b68bf6b..72cd80d3a30 100644
--- a/doc/qtcreator/src/debugger/creator-only/creator-debugger-settings.qdocinc
+++ b/doc/qtcreator/src/debugger/creator-only/creator-debugger-settings.qdocinc
@@ -39,6 +39,14 @@
     \l{Specifying Breakpoint Settings}{specify settings for breakpoints},
     and map source paths to target paths.
 
+    You can view debug output in the \uicontrol {Debugger Log} view.
+    However, in some Linux distributions, such as Arch Linux, debug
+    output is sent to the system log. To override this behavior, select
+    the \uicontrol {Force logging to console} check box. This sets
+    \c QT_LOGGING_TO_CONSOLE=1 in the environment of the debugged
+    program, which effectively prevents storing debug output in
+    system logs.
+
     \section2 Mapping Source Paths
 
     To enable the debugger to step into the code and display the source code