New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i3bar disappears after reloading configuration #2957

Open
nostdm opened this Issue Sep 16, 2017 · 3 comments

Comments

Projects
None yet
5 participants
@nostdm

nostdm commented Sep 16, 2017

Version:

Binary i3 version: 4.14 (2017-09-04)
i3bar version 4.14 (2017-09-04)

Problem:

i3bar crashes/disappears after reloading configuration or toggling its visibility settings.

This started a couple of weeks ago after updating my system and I'm not sure what the cause is.

Steps to reproduce:

Tested only on my system, with one terminal window open.

  1. Log into the i3 session.

  2. Reload the configuration either with the assigned hotkey or i3 reload command.

  3. The i3bar is no longer visible (either crashes or just disappears).

Notes:

  • System tray also disappears with the bar (the tray icons become windows).

  • When i3bar has some kind of output on the right side, e.g. status_command i3stauts then it doesn't disappear.

  • I tried setting the bar to different modes in the config file (dock, invisible, hide) which did not make any difference.

  • Trying to switch the i3bar to the 'dock' mode once it disappears doesn't bring the bar back.

  • I tested the i3bar with no statements inside the bar {} clause with the same result.

Logs:

The i3 log is the second half of the output after reloading the configuration. I omitted the first part of the log where the config file is being read.

i3 - https://gist.github.com/nostdm/7e4eb64fdfbff42924378a91f0735226

i3bar - https://gist.github.com/nostdm/0399ca2a6a77d8ca0de9d27412d2d110

@i3bot

This comment has been minimized.

Show comment
Hide comment
@i3bot

i3bot Sep 16, 2017

I don’t see a link to logs.i3wm.org. Did you follow http://i3wm.org/docs/debugging.html? (In case you actually provided a link to a logfile, please ignore me.)

i3bot commented Sep 16, 2017

I don’t see a link to logs.i3wm.org. Did you follow http://i3wm.org/docs/debugging.html? (In case you actually provided a link to a logfile, please ignore me.)

@dragon788

This comment has been minimized.

Show comment
Hide comment
@dragon788

dragon788 Dec 1, 2017

If you have output defined in your bar { } section try removing it, or try changing it from primary to another valid value (I think a specific screen name from xrandr may work.

I've seen where I need to set/unset the "output" option depending on whether I'm running i3 alongside gnome or standalone, and also depending on whether I have any external displays hooked up or if I'm using a system with an Nvidia or other discrete video card present.

dragon788 commented Dec 1, 2017

If you have output defined in your bar { } section try removing it, or try changing it from primary to another valid value (I think a specific screen name from xrandr may work.

I've seen where I need to set/unset the "output" option depending on whether I'm running i3 alongside gnome or standalone, and also depending on whether I have any external displays hooked up or if I'm using a system with an Nvidia or other discrete video card present.

@orestisf1993

This comment has been minimized.

Show comment
Hide comment
@orestisf1993

orestisf1993 Apr 27, 2018

Member

Can you still reproduce this? Could you possibly acquire a backtrace?

Member

orestisf1993 commented Apr 27, 2018

Can you still reproduce this? Could you possibly acquire a backtrace?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment