You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don’t see a link to logs.i3wm.org. Did you follow https://i3wm.org/docs/debugging.html? (In case you actually provided a link to a logfile, please ignore me.)
Alternatively, strings could be accepted and interpreted as plain text blocks.
So does i3bar if you specify that you want that version of the protocol. It's essentially deprecated, though.
I agree that i3bar should not crash, though I think exiting with an error is acceptable. The status program should never generate invalid protocol messages.
I'm submitting a…
Current Behavior
i3bar crashes when encountering invalid input, such as when encountering a string instead of an object representing a block.
Core Dump: https://drive.google.com/open?id=1AbmEqk5rEXIsDYvd9U-yiA1dPibCnIpj
Expected Behavior
i3bar should not crash.
The invalid input should be reported as an error.
Alternatively, strings could be accepted and interpreted as plain text blocks. (swaybar does this)
Reproduction Instructions
use this i3 config and status command:
https://gist.github.com/Ferdi265/dc6c2ebbd5d21970df02caa7f5685827
Environment
Output of
i3 --moreversion 2>&-
:The text was updated successfully, but these errors were encountered: