https://bugs.kde.org/show_bug.cgi?id=397062
Igor Kushnir <igor...@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |igor...@gmail.com --- Comment #8 from Igor Kushnir <igor...@gmail.com> --- Created attachment 131727 --> https://bugs.kde.org/attachment.cgi?id=131727&action=edit [PATCH] Execute Launch: show Qt log output in Run tool view I have spent several hours testing when the output appears or not until I found this bug report. This bug only happens if KDevelop itself is started from a graphical environment rather than from a terminal, and the user launches a Qt application via "Execute Launch" KDevelop action rather than "Debug Launch" action. The issue is inherited by another KDevelop instance Execute-Launched from KDevelop (a recursion of sorts). I just implemented a fix for this issue that sets QT_FORCE_STDERR_LOGGING to 1 in the initial default environment profile and when the user creates a new environment profile: see the attached 0001-Execute-Launch-show-Qt-log-output-in-Run-tool-view.patch. However now I realize that a better fix is possible: add a checkbox on Launch Configuration page with text "Show Qt log messages in Run tool view" and a tooltip "Sets QT_FORCE_STDERR_LOGGING environment variable to 1" (or maybe a more detailed explanation in the tooltip). The checkbox should be checked by default. When KDevelop applies the selected environment profile to a launched program and this new option in its launch configuration is on, it will silently set one more hidden environment variable. This way the fix is retroactively applied to all existing launch configurations without the need to manually add the environment variable to all environment profiles configured in the past. Plus the checkbox provides an opportunity to explain why the environment variable is needed, as opposed to simply specifying it in the unconfigured default and new environment profiles. -- You are receiving this mail because: You are watching all bug changes.