i3 FAQ - Individual question feed

i3 FAQ - Individual question feedhttps://faq.i3wm.org/questions/Frequently asked questions and answers about the i3 window managerenCopyright i3, 2012Thu, 03 Jul 2014 08:59:29 +0000How to enable logs in Ubuntuhttps://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/I wanted to check out the logs for a crash I could reproduce, but the command gives me: $ i3-dump-log i3-dump-log: Cannot get I3_SHMLOG_PATH atom contents. Is i3 running on this display? I read that we need to "active" the logging, but I did not understand how/where to do it. Do you know where should I place the command for logging (.xsession file did not work, .i3/config did not work): exec /usr/bin/i3 -V -d all >~/i3log-$(date +'%F-%k-%M-%S') 2>&1 thanks,Thu, 07 Jun 2012 06:02:11 +0000https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/Answer by Tucos for I wanted to check out the logs for a crash I could reproduce, but the command gives me: <pre><code>$ i3-dump-log i3-dump-log: Cannot get I3_SHMLOG_PATH atom contents. Is i3 running on this display? </code></pre> I read that we need to "active" the logging, but I did not understand how/where to do it. Do you know where should I place the command for logging (.xsession file did not work, .i3/config did not work): <pre><code>exec /usr/bin/i3 -V -d all >~/i3log-$(date +'%F-%k-%M-%S') 2>&1 </code></pre> thanks, https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?answer=81#post-id-81Shared memory logging is by default only enabled in development builds. If you're using a build from git, then you might simply need to run `DISPLAY=:0 i3-dump-log`. As for regular logging, your command should be fine and it should be in ~/.xsession if using a display manager and in ~/.xinitrc if using startx. For further info you can take a look at [the Debugging How To for development builds](http://build.i3wm.org/docs/debugging.html) or [the regular debugging howto](http://i3wm.org/docs/debugging-release-version.html)Thu, 07 Jun 2012 09:21:58 +0000https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?answer=81#post-id-81Comment by Michael for Shared memory logging is by default only enabled in development builds. If you're using a build from git, then you might simply need to run <code>DISPLAY=:0 i3-dump-log</code>. As for regular logging, your command should be fine and it should be in ~/.xsession if using a display manager and in ~/.xinitrc if using startx. For further info you can take a look at <a href="http://build.i3wm.org/docs/debugging.html">the Debugging How To for development builds</a> or <a href="http://i3wm.org/docs/debugging-release-version.html">the regular debugging howto</a> https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?comment=91#comment-91bruno: after entering your username, select the session type "custom" at the bottom of your screen.Thu, 07 Jun 2012 21:41:50 +0000https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?comment=91#comment-91Comment by bruno.braga for Shared memory logging is by default only enabled in development builds. If you're using a build from git, then you might simply need to run <code>DISPLAY=:0 i3-dump-log</code>. As for regular logging, your command should be fine and it should be in ~/.xsession if using a display manager and in ~/.xinitrc if using startx. For further info you can take a look at <a href="http://build.i3wm.org/docs/debugging.html">the Debugging How To for development builds</a> or <a href="http://i3wm.org/docs/debugging-release-version.html">the regular debugging howto</a> https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?comment=85#comment-85In Ubuntu, with gdm, .xsession is never called... any ideas?Thu, 07 Jun 2012 14:03:53 +0000https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?comment=85#comment-85Comment by Hibou57 for Shared memory logging is by default only enabled in development builds. If you're using a build from git, then you might simply need to run <code>DISPLAY=:0 i3-dump-log</code>. As for regular logging, your command should be fine and it should be in ~/.xsession if using a display manager and in ~/.xinitrc if using startx. For further info you can take a look at <a href="http://build.i3wm.org/docs/debugging.html">the Debugging How To for development builds</a> or <a href="http://i3wm.org/docs/debugging-release-version.html">the regular debugging howto</a> https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?comment=4106#comment-4106I run a session using “i3 (with debug long)”, and running `DISPLAY=:0 i3-dump-log` still give the same as the OP encountered. I wanted to submit a but report, but can't get a debug log. I installed i3 from Synaptic.Thu, 03 Jul 2014 08:59:29 +0000https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?comment=4106#comment-4106Comment by bruno.braga for Shared memory logging is by default only enabled in development builds. If you're using a build from git, then you might simply need to run <code>DISPLAY=:0 i3-dump-log</code>. As for regular logging, your command should be fine and it should be in ~/.xsession if using a display manager and in ~/.xinitrc if using startx. For further info you can take a look at <a href="http://build.i3wm.org/docs/debugging.html">the Debugging How To for development builds</a> or <a href="http://i3wm.org/docs/debugging-release-version.html">the regular debugging howto</a> https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?comment=110#comment-110Michael, the new Ubuntu 12.04 does not have the option Custom anymore. I got it working by entering into a terminal (Ctrl+Alt+F1) and: /etc/init.d/lightdm stop; startx (the i3 call must be in .xinitrc)Sun, 10 Jun 2012 09:54:23 +0000https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?comment=110#comment-110Answer by joepd for I wanted to check out the logs for a crash I could reproduce, but the command gives me: <pre><code>$ i3-dump-log i3-dump-log: Cannot get I3_SHMLOG_PATH atom contents. Is i3 running on this display? </code></pre> I read that we need to "active" the logging, but I did not understand how/where to do it. Do you know where should I place the command for logging (.xsession file did not work, .i3/config did not work): <pre><code>exec /usr/bin/i3 -V -d all >~/i3log-$(date +'%F-%k-%M-%S') 2>&1 </code></pre> thanks, https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?answer=88#post-id-88Please discriminate between a dump-log, and the lines that i3 is printing on STDOUT. The dump is some blob of data that records the state of i3, handy for developers to see what has been leading up to unexpected behavior. This is not intended to be read by mere mortals. For the dump-log: i3 needs to be compiled with support for this. This is disabled if you install your package from a repository, as the package is considered stable. The exec-line is about starting i3 manually. If you use xinit to launch i3, you should remove 'exec'. This line starts i3 in verbose mode, and sends STDOUT and STDERR to the mentioned file, in stead of cluttering your TTY. But it depends on how you launch i3 where you should put such a line. Thu, 07 Jun 2012 16:36:20 +0000https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?answer=88#post-id-88Comment by Michael for Please discriminate between a dump-log, and the lines that i3 is printing on STDOUT. The dump is some blob of data that records the state of i3, handy for developers to see what has been leading up to unexpected behavior. This is not intended to be read by mere mortals. For the dump-log: i3 needs to be compiled with support for this. This is disabled if you install your package from a repository, as the package is considered stable. The exec-line is about starting i3 manually. If you use xinit to launch i3, you should remove 'exec'. This line starts i3 in verbose mode, and sends STDOUT and STDERR to the mentioned file, in stead of cluttering your TTY. But it depends on how you launch i3 where you should put such a line. https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?comment=89#comment-89You are wrong in several points: i3-dump-log prints out the same text log that i3 logs to stdout. Also, it does not have to be compiled in, you can enable it in every version. It’s just enabled by default in the developer versions.Thu, 07 Jun 2012 21:39:55 +0000https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?comment=89#comment-89Answer by bruno.braga for I wanted to check out the logs for a crash I could reproduce, but the command gives me: <pre><code>$ i3-dump-log i3-dump-log: Cannot get I3_SHMLOG_PATH atom contents. Is i3 running on this display? </code></pre> I read that we need to "active" the logging, but I did not understand how/where to do it. Do you know where should I place the command for logging (.xsession file did not work, .i3/config did not work): <pre><code>exec /usr/bin/i3 -V -d all >~/i3log-$(date +'%F-%k-%M-%S') 2>&1 </code></pre> thanks, https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?answer=1373#post-id-1373I just learned that .xinitrc is never called, so .xsession should be just a symlink to .xinitrc (from thie [https://wiki.ubuntu.com/CustomXSession](https://wiki.ubuntu.com/CustomXSession)). So to make it just work properly on Ubuntu, follow these steps: 1. Create a *.xinitrc* file: exec /usr/bin/i3 -V >/tmp/i3-$(date +'%F-%k-%M-%S').log 2>&1 2. Create a symlink for *.xsession*: $ ln -s ~/.xinitrc ~/.xsession 3. Edit desktop options for lightdm, at: */usr/share/xsessions/i3.desktop* [Desktop Entry] Name=i3 Comment=improved dynamic tiling window manager Exec=/etc/X11/Xsession Type=Application And voila!Tue, 12 Mar 2013 10:03:32 +0000https://faq.i3wm.org/question/80/how-to-enable-logs-in-ubuntu/?answer=1373#post-id-1373