2016-12-04 13:56:23 UTC
Recently, i3 has been unable to bring up status bar by itself.
Problems started without me having changed config or updated i3. I'm
wondering if it perhaps could have been triggered by video drivers or some
such (the only thing even vaguely relevant that's changed).
I encountered issues while on i3 4.10.4 and i3status 2.7. In trying to
solve it, I upgraded to i3 4.13-r1 and i3status 2.10-r1. It did not help.
I've tried starting i3 with no config; I've tried starting with clean
config from /etc. Including, of course, clean i3status conf. No difference;
I don't see a status bar.
I tried moving to i3blocks instead of i3status; no difference: no status
I do get a status bar if the bar block in config consists of "i3bar_command
i3bar" instead of status_command.
I have tried status_command "normal" and exec; no change. I have tried
status_command i3status, i3blocks, as well as to a script. Nothing works
--- if I just leave it at that, a working bar block in config.
In order to actually get a status bar, I need to start it with the command
"/usr/bin/i3bar --bar_id=bar-0" if I run it in the terminal or through
dmenu. I've created a script containing nothing but the line above. If I
run it in terminal or dmenu, I get a status bar.
*Since the command above works, config is set up correctly.* There is a bar
block. The bar block can be called manually. But i3 is not able to do it.
If I run the script (i3bar --bar_id....) through exec in i3, it does not
If I run the same script through a bindsym in i3, it does not work.
But, again, the same script in shell or dmenu? Works.
When trying through bindsym, I get the following in the session log:
(libev) epoll_wait: Invalid argument
[libi3] ../../i3-4.13/libi3/font.c Using Pango font DejaVu Sans Mono, size
[libi3] ../../i3-4.13/libi3/font.c X11 root window dictates 96.094581 DPI
/PATH/i3-mystatus.sh: rad 3: 4799 Avbruten (SIGABRT) i3bar --bar_id=bar-0
Exiting due to signal.
Here's a dwm log using configs straight from /etc:
Note lines 903 to 928. Status bar is initiated --- but is disconnected. The
result as seen on the display / from the users perspective. Nothing. No
Later (lines 1856 and forward) I start the status bar through dmenu; and
status bar is shown.
Regardless of how I try to start bar from within i3, if with a
status_command or a status_command exec or an command/exec to a script that
runs i3bar --- I get nothing. Even tried having an exec to script; nothing.
I tried to add a bindsym to i3bar, and/or to the script running it --- no
But if I run the script (containing 'i3bar --bar_id=bar-0') through either
dmenu or bash --- it works!
i3bar seems to SIGABRT when run through i3, but not when run through bash
or dmenu. What could cause this!?