X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=docs%2Fdebugging;h=7be7c8e5b37f2d4cd44134c30b9b6f32f4a3ea0a;hb=b5583d6cf4e0426d9aedd589f18e03407793199b;hp=cf61813d4789b52c1c4791f4b28f92698c73e4b2;hpb=e89f39158974e4d68491a8dcd471f6ee70f5b46f;p=i3%2Fi3 diff --git a/docs/debugging b/docs/debugging index cf61813d..7be7c8e5 100644 --- a/docs/debugging +++ b/docs/debugging @@ -93,10 +93,17 @@ issue with the software in question, not i3. == Obtaining the debug logfile -Please note that log files may contain sensitive data such as window titles. +[CAUTION] +================================================================================ +Logs may contain sensitive information, so please inspect the log before +submitting it. Logs may be viewed by anyone, once posted. If you choose to +redact the log, make an effort not to discard information which may be relevant +to the issue you are reporting. + The best way to avoid submitting such information is to only run the necessary -applications to reproduce the behavior when saving the log file. This will also -make analyzing the log file easier. +steps to reproduce the behavior when saving the log file. This will also make +analyzing the log file easier. +================================================================================ No matter whether i3 misbehaved in some way without crashing or whether it just crashed, the logfile provides all information necessary to debug the problem. @@ -153,10 +160,11 @@ length limitations) or flood kicks. == Debugging i3bar -To debug i3bar problems, add +verbose yes+ to all +bar {}+ blocks in your i3 config -and then restart all i3bar instances like this: +To debug i3bar problems, add +verbose yes+ to all +bar {}+ blocks in your i3 +config, reload your config and then restart all i3bar instances like this: --------------------------------------------------------------------- +$ i3 reload $ killall i3bar $ for c in $(i3-msg -t get_bar_config | python -c \ 'import json,sys;print("\n".join(json.load(sys.stdin)))'); do \