From 663235c714762c069e660ffe14a8334f73365c1b Mon Sep 17 00:00:00 2001 From: Michael Stapelberg Date: Wed, 4 Feb 2015 19:54:07 +0100 Subject: [PATCH] docs/debugging: use logs.i3wm.org --- docs/debugging | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/debugging b/docs/debugging index 9dec3056..1253b0c5 100644 --- a/docs/debugging +++ b/docs/debugging @@ -72,15 +72,17 @@ i3-msg 'debuglog on; shmlog on; reload' 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. -To save a compressed version of the logfile (suitable for attaching it to a -bugreport), use: --------------------------------------------------------------------- -DISPLAY=:0 i3-dump-log | bzip2 -c > /tmp/i3.log.bz2 --------------------------------------------------------------------- +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 +------------------------------------------------------------------------------ This command does not depend on i3 (it also works while i3 displays the crash dialog), but it requires a working X11 connection. +After running it, you will get a URL to the logfile. Please include that URL in +your bug report. + == On crashes: Obtaining a backtrace When i3 crashes, it will display a dialog stating “i3 just crashed”, offering -- 2.39.2