Error: Received EOF from statusline process

asked 2013-12-24 19:57:54 +0000

Rob
1 ●1 ●1 ●2

updated 2013-12-24 19:58:33 +0000

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.

edit retag flag offensive close merge delete

Comments

were you expecting to see a statusline or a blank bar?

TonyC ( 2013-12-25 01:54:31 +0000 )edit

@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.

Rob ( 2013-12-25 03:09:54 +0000 )edit

add a comment

2 answers

Sort by » oldest newest most voted

answered 2013-12-25 03:30:08 +0000

TonyC
975 ●6 ●20 ●28

updated 2014-01-04 13:09:25 +0000

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 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.

edit flag offensive delete link

Comments

Thanks. I'll try that in the morning.

Rob ( 2013-12-25 03:38:19 +0000 )edit

I 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 }

Glisha ( 2013-12-26 10:05:59 +0000 )edit

Yeah 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.

TonyC ( 2013-12-26 21:43:05 +0000 )edit

add a comment

-1

answered 2014-01-05 00:22:56 +0000

Licaon_Kter
1 ●2 ●2 ●4

updated 2014-01-05 00:25:28 +0000

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:

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/parsejsonheader.c edits maybe.

edit flag offensive delete link

Comments

Please 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).

TonyC ( 2014-01-05 10:15:53 +0000 )edit

We just reverted that commit and it works fine now.

TonyC ( 2014-01-05 12:47:34 +0000 )edit

Yep, works ok now, and we got a **i3status** vers 2.8 build in Debian Sid too, nice.

Licaon_Kter ( 2014-01-05 15:45:52 +0000 )edit

add a comment

Error: Received EOF from statusline process

Comments

2 answers

Comments

Comments

Question Tools

Stats

Related questions