Guidelines and HOWTOs/Debugging/DrKonqi: Difference between revisions
Created page with "== Networking Issues == Note that network debugging may leak passwords and session tokens. You should check the output before posting it anywhere. Specifically the values fol..." |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
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> | 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. | To actually obtain the output please follow the instructions. | ||
| Line 33: | Line 35: | ||
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! | 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. | |||
Latest revision as of 10:52, 24 October 2023
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: &password=, Bugzilla_login_request_cookie=, and token=
Manual Tracing
To actually obtain the output please follow the instructions.
- Find your drkonqi binary,
which drkonqi /usr/lib/*/libexec/drkonqi /usr/lib/libexec/drkonqi /lib/libexec/drkonqimight 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:
export APP=__APPNAME_GOES_HERE__ export DRKONQI=__DRKONQI_PATH_GOES_HERE__
You'll also need to copy a bunch of boilerplate variables verbatim:
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
At this point you are able to start drkonqi with this command:
$DRKONQI --pid `pidof $APP` --restarted --bugaddress [email protected] --dialog --appversion 999
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
export DRKONQI_MINIMAL_MODE=1
This switches the UI into a minimal mode which may be preferable for use by developers.