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, 2012Sun, 05 Jan 2014 15:45:52 +0000Error: Received EOF from statusline processhttps://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/i3 was either reinstalled or upgrade to version 4.7 on my system today and, for the first time, I see an error in the lower right corner, stating what's in the title of this thread. I notice there is something in the bugtracker about giving better error messages for the status line when it fails and I'm wondering if this is the result of that. If so, it's distracting, but I don't know how to solve the problem. I'm running plain vanilla, nothing changed in the default config file, on FreeBSD 9.2.Tue, 24 Dec 2013 19:57:54 +0000https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/Comment by TonyC for i3 was either reinstalled or upgrade to version 4.7 on my system today and, for the first time, I see an error in the lower right corner, stating what's in the title of this thread. I notice there is something in the bugtracker about giving better error messages for the status line when it fails and I'm wondering if this is the result of that. If so, it's distracting, but I don't know how to solve the problem. I'm running plain vanilla, nothing changed in the default config file, on FreeBSD 9.2. https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3092#comment-3092were you expecting to see a statusline or a blank bar?Wed, 25 Dec 2013 01:54:31 +0000https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3092#comment-3092Comment by Rob for i3 was either reinstalled or upgrade to version 4.7 on my system today and, for the first time, I see an error in the lower right corner, stating what's in the title of this thread. I notice there is something in the bugtracker about giving better error messages for the status line when it fails and I'm wondering if this is the result of that. If so, it's distracting, but I don't know how to solve the problem. I'm running plain vanilla, nothing changed in the default config file, on FreeBSD 9.2. https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3093#comment-3093@TonyC The bottom of the screen, where the desktop numbers are shown but on the right side, is where the error message is in red. I've never seen anything there in the past.Wed, 25 Dec 2013 03:09:54 +0000https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3093#comment-3093Answer by TonyC for i3 was either reinstalled or upgrade to version 4.7 on my system today and, for the first time, I see an error in the lower right corner, stating what's in the title of this thread. I notice there is something in the bugtracker about giving better error messages for the status line when it fails and I'm wondering if this is the result of that. If so, it's distracting, but I don't know how to solve the problem. I'm running plain vanilla, nothing changed in the default config file, on FreeBSD 9.2. https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?answer=3094#post-id-3094We had a lot of people coming into the chat having problems with special statusline configuration or getting i3status to work with some locales. The lack of an error message made debugging these problems very difficult, so we decided to display a message on the bar whenever the bar config specifies a `status_command` and no statusline can be made from running this command. If you received this error and you would like to know how you can resolve this issue, you can get a detailed error message from running your `status_command` in a terminal. In the default case, use `$ i3status` If you prefer not to have a status command, find the bar directive in your config and comment out the `status_command` line. The default location for the config is `~/.i3/config`. It should look like this: bar { #status_command i3status } For more information on configuring i3bar, see [the page in the manual.](http://i3wm.org/docs/userguide.html#_configuring_i3bar)Wed, 25 Dec 2013 03:30:08 +0000https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?answer=3094#post-id-3094Comment by TonyC for We had a lot of people coming into the chat having problems with special statusline configuration or getting i3status to work with some locales. The lack of an error message made debugging these problems very difficult, so we decided to display a message on the bar whenever the bar config specifies a <code>status_command</code> and no statusline can be made from running this command. If you received this error and you would like to know how you can resolve this issue, you can get a detailed error message from running your <code>status_command</code> in a terminal. In the default case, use <code>$ i3status</code> If you prefer not to have a status command, find the bar directive in your config and comment out the <code>status_command</code> line. The default location for the config is <code>~/.i3/config</code>. It should look like this: <pre><code>bar { #status_command i3status } </code></pre> For more information on configuring i3bar, see <a href="http://i3wm.org/docs/userguide.html#_configuring_i3bar">the page in the manual.</a> https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3106#comment-3106Yeah this doesn't work correctly on some systems unfortunately. Here is the issue on the bug tracker: https://github.com/i3/i3/issues/1140 . If anyone with this issue can test patches, that would be appreciated.Thu, 26 Dec 2013 21:43:05 +0000https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3106#comment-3106Comment by Glisha for We had a lot of people coming into the chat having problems with special statusline configuration or getting i3status to work with some locales. The lack of an error message made debugging these problems very difficult, so we decided to display a message on the bar whenever the bar config specifies a <code>status_command</code> and no statusline can be made from running this command. If you received this error and you would like to know how you can resolve this issue, you can get a detailed error message from running your <code>status_command</code> in a terminal. In the default case, use <code>$ i3status</code> If you prefer not to have a status command, find the bar directive in your config and comment out the <code>status_command</code> line. The default location for the config is <code>~/.i3/config</code>. It should look like this: <pre><code>bar { #status_command i3status } </code></pre> For more information on configuring i3bar, see <a href="http://i3wm.org/docs/userguide.html#_configuring_i3bar">the page in the manual.</a> https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3100#comment-3100I have multimonitor setup and still get Error: Received EOF from statusline process on the second monitor where I don't want a status_command. bar { output HDMI1 output LVDS1 status_command i3status } bar { output VGA1 tray_output none } Thu, 26 Dec 2013 10:05:59 +0000https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3100#comment-3100Comment by Rob for We had a lot of people coming into the chat having problems with special statusline configuration or getting i3status to work with some locales. The lack of an error message made debugging these problems very difficult, so we decided to display a message on the bar whenever the bar config specifies a <code>status_command</code> and no statusline can be made from running this command. If you received this error and you would like to know how you can resolve this issue, you can get a detailed error message from running your <code>status_command</code> in a terminal. In the default case, use <code>$ i3status</code> If you prefer not to have a status command, find the bar directive in your config and comment out the <code>status_command</code> line. The default location for the config is <code>~/.i3/config</code>. It should look like this: <pre><code>bar { #status_command i3status } </code></pre> For more information on configuring i3bar, see <a href="http://i3wm.org/docs/userguide.html#_configuring_i3bar">the page in the manual.</a> https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3095#comment-3095Thanks. I'll try that in the morning. Wed, 25 Dec 2013 03:38:19 +0000https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3095#comment-3095Answer by Licaon_Kter for i3 was either reinstalled or upgrade to version 4.7 on my system today and, for the first time, I see an error in the lower right corner, stating what's in the title of this thread. I notice there is something in the bugtracker about giving better error messages for the status line when it fails and I'm wondering if this is the result of that. If so, it's distracting, but I don't know how to solve the problem. I'm running plain vanilla, nothing changed in the default config file, on FreeBSD 9.2. https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?answer=3171#post-id-3171Seems related to my problem: i3bar crash since build i3-wm_4.7.1-1+g4.7-**101-gb109b1b1** Debian Sid 64bit up to date, i3-wm Debian repo unstable builds, still crashing in build **106-g90e7c5c1**, going back to **98-gf78c1ba1** fixes it again. Error message in *~/.xsession-errors*: 04.01.2014 23:29:58 - [libi3] ERROR: IPC: received EOF instead of reply Segmentation fault Error message in **dmesg**: i3bar[19766]: segfault at 7f52eb858a40 ip 00007f52eb858a40 sp 00007fff1dba5b08 error 15 in libev.so.4.0.0[7f52eb858000+1000] Now, editing my *bar {}* settings isolated the problem to this line: *status_command i3status -c ~/.i3status*. My **i3status -c ~/.i3status** output: {"version":1} [ [{"name":"disk_info","instance":"/","full_text":"X,X GB"},{"name":"run_watch","instance":"/var/run/dhclient*.pid","color":"#00FF00","full_text":"DHCP: yes"},{"name":"ethernet","instance":"eth0","color":"#00FF00","full_text":"xxx.xxx.xxx.xxx (100 Mbit/s)"},{"name":"load","full_text":"0,01"},{"name":"time","full_text":"2014-01-05 02:05:11"}] Editing *~/.i3status* config yields that removing the *output_format = "i3bar"* line would make i3 not segfault, new **i3status -c ~/.i3status** output: i3status: trying to auto-detect output_format setting i3status: falling back to "none" X,X GB | DHCP: yes | xxx.xxx.xxx.xx (100 Mbit/s) | 0,01 | 2014-01-05 02:05:11 although I don't get any colors, at least it works. Looking in **git** I believe it's this commit: code.stapelberg.de/git/i3/commit/?h=next&id=705b43294add2fffede086c0c072dc5a849ffc49 the **/i3bar/src/parse_json_header.c** edits maybe. Sun, 05 Jan 2014 00:22:56 +0000https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?answer=3171#post-id-3171Comment by TonyC for Seems related to my problem: i3bar crash since build i3-wm_4.7.1-1+g4.7-101-gb109b1b1 Debian Sid 64bit up to date, i3-wm Debian repo unstable builds, still crashing in build 106-g90e7c5c1, going back to 98-gf78c1ba1 fixes it again. Error message in ~/.xsession-errors: <pre><code>04.01.2014 23:29:58 - [libi3] ERROR: IPC: received EOF instead of reply Segmentation fault </code></pre> Error message in dmesg: <pre><code>i3bar[19766]: segfault at 7f52eb858a40 ip 00007f52eb858a40 sp 00007fff1dba5b08 error 15 in libev.so.4.0.0[7f52eb858000+1000] </code></pre> Now, editing my bar {} settings isolated the problem to this line: status_command i3status -c ~/.i3status. My i3status -c ~/.i3status output: <pre><code>{"version":1} [ [{"name":"disk_info","instance":"/","full_text":"X,X GB"},{"name":"run_watch","instance":"/var/run/dhclient*.pid","color":"#00FF00","full_text":"DHCP: yes"},{"name":"ethernet","instance":"eth0","color":"#00FF00","full_text":"xxx.xxx.xxx.xxx (100 Mbit/s)"},{"name":"load","full_text":"0,01"},{"name":"time","full_text":"2014-01-05 02:05:11"}] </code></pre> Editing ~/.i3status config yields that removing the output_format = "i3bar" line would make i3 not segfault, new i3status -c ~/.i3status output: <pre><code>i3status: trying to auto-detect output_format setting i3status: falling back to "none" X,X GB | DHCP: yes | xxx.xxx.xxx.xx (100 Mbit/s) | 0,01 | 2014-01-05 02:05:11 </code></pre> although I don't get any colors, at least it works. Looking in git I believe it's this commit: code.stapelberg.de/git/i3/commit/?h=next&id=705b43294add2fffede086c0c072dc5a849ffc49 the /i3bar/src/parsejsonheader.c edits maybe. https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3175#comment-3175We just reverted that commit and it works fine now.Sun, 05 Jan 2014 12:47:34 +0000https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3175#comment-3175Comment by TonyC for Seems related to my problem: i3bar crash since build i3-wm_4.7.1-1+g4.7-101-gb109b1b1 Debian Sid 64bit up to date, i3-wm Debian repo unstable builds, still crashing in build 106-g90e7c5c1, going back to 98-gf78c1ba1 fixes it again. Error message in ~/.xsession-errors: <pre><code>04.01.2014 23:29:58 - [libi3] ERROR: IPC: received EOF instead of reply Segmentation fault </code></pre> Error message in dmesg: <pre><code>i3bar[19766]: segfault at 7f52eb858a40 ip 00007f52eb858a40 sp 00007fff1dba5b08 error 15 in libev.so.4.0.0[7f52eb858000+1000] </code></pre> Now, editing my bar {} settings isolated the problem to this line: status_command i3status -c ~/.i3status. My i3status -c ~/.i3status output: <pre><code>{"version":1} [ [{"name":"disk_info","instance":"/","full_text":"X,X GB"},{"name":"run_watch","instance":"/var/run/dhclient*.pid","color":"#00FF00","full_text":"DHCP: yes"},{"name":"ethernet","instance":"eth0","color":"#00FF00","full_text":"xxx.xxx.xxx.xxx (100 Mbit/s)"},{"name":"load","full_text":"0,01"},{"name":"time","full_text":"2014-01-05 02:05:11"}] </code></pre> Editing ~/.i3status config yields that removing the output_format = "i3bar" line would make i3 not segfault, new i3status -c ~/.i3status output: <pre><code>i3status: trying to auto-detect output_format setting i3status: falling back to "none" X,X GB | DHCP: yes | xxx.xxx.xxx.xx (100 Mbit/s) | 0,01 | 2014-01-05 02:05:11 </code></pre> although I don't get any colors, at least it works. Looking in git I believe it's this commit: code.stapelberg.de/git/i3/commit/?h=next&id=705b43294add2fffede086c0c072dc5a849ffc49 the /i3bar/src/parsejsonheader.c edits maybe. https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3173#comment-3173Please post bugs to the bug tracker in the future at http://bugs.i3wm.org (the faq is not designed to handle this). I do not believe these issues are related. The errors appear to be similar, but are coming from different places (in your case, the IPC, and in this case the status process).Sun, 05 Jan 2014 10:15:53 +0000https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3173#comment-3173Comment by Licaon_Kter for Seems related to my problem: i3bar crash since build i3-wm_4.7.1-1+g4.7-101-gb109b1b1 Debian Sid 64bit up to date, i3-wm Debian repo unstable builds, still crashing in build 106-g90e7c5c1, going back to 98-gf78c1ba1 fixes it again. Error message in ~/.xsession-errors: <pre><code>04.01.2014 23:29:58 - [libi3] ERROR: IPC: received EOF instead of reply Segmentation fault </code></pre> Error message in dmesg: <pre><code>i3bar[19766]: segfault at 7f52eb858a40 ip 00007f52eb858a40 sp 00007fff1dba5b08 error 15 in libev.so.4.0.0[7f52eb858000+1000] </code></pre> Now, editing my bar {} settings isolated the problem to this line: status_command i3status -c ~/.i3status. My i3status -c ~/.i3status output: <pre><code>{"version":1} [ [{"name":"disk_info","instance":"/","full_text":"X,X GB"},{"name":"run_watch","instance":"/var/run/dhclient*.pid","color":"#00FF00","full_text":"DHCP: yes"},{"name":"ethernet","instance":"eth0","color":"#00FF00","full_text":"xxx.xxx.xxx.xxx (100 Mbit/s)"},{"name":"load","full_text":"0,01"},{"name":"time","full_text":"2014-01-05 02:05:11"}] </code></pre> Editing ~/.i3status config yields that removing the output_format = "i3bar" line would make i3 not segfault, new i3status -c ~/.i3status output: <pre><code>i3status: trying to auto-detect output_format setting i3status: falling back to "none" X,X GB | DHCP: yes | xxx.xxx.xxx.xx (100 Mbit/s) | 0,01 | 2014-01-05 02:05:11 </code></pre> although I don't get any colors, at least it works. Looking in git I believe it's this commit: code.stapelberg.de/git/i3/commit/?h=next&id=705b43294add2fffede086c0c072dc5a849ffc49 the /i3bar/src/parsejsonheader.c edits maybe. https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3176#comment-3176Yep, works ok now, and we got a **i3status** vers 2.8 build in Debian Sid too, nice.Sun, 05 Jan 2014 15:45:52 +0000https://faq.i3wm.org/question/3090/error-received-eof-from-statusline-process/?comment=3176#comment-3176