View source for Guidelines and HOWTOs/Debugging/DrKonqi

== Networking Issues ==

Note that network debugging may leak passwords and session tokens. You should check the output before posting it anywhere. Specifically the values following the listed values should get removed: <code>&password=</code>, <code>Bugzilla_login_request_cookie=</code>, and <code>token=</code>

== Manual Tracing ==

To actually obtain the output please follow the instructions.

* Find your drkonqi binary, <code>which drkonqi /usr/lib/*/libexec/drkonqi /usr/lib/libexec/drkonqi /lib/libexec/drkonqi</code> might help locate it in some common paths. If that doesn't help, best consult your distribution. 
* Open a terminal
* Open an application (e.g. dolphin or kwrite)

In the terminal now set the drkonqi path and the app name:

{{Input|1=<nowiki>
export APP=__APPNAME_GOES_HERE__
export DRKONQI=__DRKONQI_PATH_GOES_HERE__
</nowiki>}}

You'll also need to copy a bunch of boilerplate variables verbatim:

{{Input|1=<nowiki>
export KDE_FORK_SLAVES=1
export QT_MESSAGE_PATTERN='[%{time process}](%{pid})/(%{category}) %{function}: %{message}'
export QT_LOGGING_RULES='org.kde.drkonqi.bugzilla=true;kf.kio.http=true;kf.kio.slaves.http=true;kf.kio.workers.http=true'
export DRKONQI_TEST_MODE=1
export DRKONQI_IGNORE_QUALITY=1
</nowiki>}}

At this point you are able to start drkonqi with this command:

{{Input|1=<nowiki>
$DRKONQI --pid `pidof $APP` --restarted --bugaddress submit@bugs.kde.org --dialog --appversion 999 
</nowiki>}}

Proceed to where the problem appears and then attach the output from the terminal to a bug report. DO NOT FORGET TO REMOVE THE AFOREMENTIONED SECRETS!

== Minimal Mode ==

{{Input|1=<nowiki>
export DRKONQI_MINIMAL_MODE=1
</nowiki>}}

This switches the UI into a minimal mode which may be preferable for use by developers.