X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=docs%2Fdebugging.html;h=b84cff841ae75965a7d217465603d4f6bf9d3c6c;hb=1192fdf4b6df07734626617389fc161d31c45a85;hp=c36b28d9da567a6ed8a0398284f4a226126dcdb0;hpb=f6ac7e334743f04fa3bbc7c1ad713762d4076c73;p=i3%2Fi3.github.io diff --git a/docs/debugging.html b/docs/debugging.html index c36b28d..b84cff8 100644 --- a/docs/debugging.html +++ b/docs/debugging.html @@ -4,7 +4,7 @@ - + i3: Debugging i3: How To @@ -22,7 +22,7 @@ document.addEventListener("DOMContentLoaded", function(){asciidoc.footnotes();}, @@ -44,7 +44,7 @@ process and/or need further help, do not hesitate to contact us!

-

1. Verify you are using i3 ≥ 4.11

+

1. Verify you are using i3 ≥ 4.16.1

Only the latest major version of i3 is supported. To verify which version you are running, use:

@@ -74,8 +74,8 @@ if you can.

Your version is 85 commits newer than 4.7, and the git revision of your -version is 9c15b95. Go to http://code.i3wm.org/i3/commit/?h=next and see if -the line "commit" starts with the same revision. If so, you are using the +version is 9c15b95. Go to https://github.com/i3/i3/commits/next and see if +the most recent commit starts with the same revision. If so, you are using the latest version.

@@ -181,7 +181,7 @@ crashed, the logfile provides all information necessary to debug the problem.

To upload a compressed version of the logfile (for a bugreport), use:

-
DISPLAY=:0 i3-dump-log | bzip2 -c | curl --data-binary @- http://logs.i3wm.org
+
DISPLAY=:0 i3-dump-log | bzip2 -c | curl --data-binary @- https://logs.i3wm.org

This command does not depend on i3 (it also works while i3 displays the crash dialog), but it requires a working X11 connection.

@@ -221,16 +221,17 @@ starting at 0.

When sending bug reports, please attach the whole log file. Even if you think you found the section which clearly highlights the problem, additional information might be necessary to completely diagnose the problem.

-

When debugging with us in IRC, be prepared to use a so called nopaste service -such as http://nopaste.info or http://pastebin.com because pasting large -amounts of text in IRC sometimes leads to incomplete lines (servers have line -length limitations) or flood kicks.

+

When debugging with us in IRC, be prepared to use a so-called nopaste service +such as https://pastebin.com because pasting large amounts of text in IRC +sometimes leads to incomplete lines (servers have line length limitations) or +flood kicks.

7. Debugging i3bar

-

To debug i3bar problems, add verbose yes to all bar {} blocks in your i3 +

To debug i3bar problems, use the --verbose commandline parameter, +or add verbose yes to all bar {} blocks in your i3 config, reload your config and then restart all i3bar instances like this:

@@ -248,7 +249,9 @@ in your bug report.