Rooba
/
polybar
mirror of https://github.com/polybar/polybar.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Known Issues (markdown)

Patrick Ziegler 2020-06-05 21:50:45 +02:00
parent 1c6471063e
commit df08b4f70c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Known-Issues.md

@ -112,7 +112,7 @@ This behaviour was introduced in [`#831`](https://github.com/polybar/polybar/pul
**Workaround:** The workaround that some people use, is to create a full-width fully transparent dummy bar on the same monitor and in the same position (with `override-redirect = false`), so that i3 reserves space for this dummy bar, effectively also reserving space for our actual bar. The real bar may need to have `wm-restack = i3` set for it to not overlap with fullscreen windows. **Note:** This requires that you have a composition manager running because the dummy bar may overlap the real bar. **Workaround:** The workaround that some people use, is to create a full-width fully transparent dummy bar on the same monitor and in the same position (with `override-redirect = false`), so that i3 reserves space for this dummy bar, effectively also reserving space for our actual bar. The real bar may need to have `wm-restack = i3` set for it to not overlap with fullscreen windows. **Note:** This requires that you have a composition manager running because the dummy bar may overlap the real bar.
If you are using i3-gaps (branch `gaps-next` or version `4.17` once it's released), you can set `gaps top X` or `gaps bottom X` in your i3 config to reserve space for the bar where `X` is the number of pixels you want to reserve. **Note:** On multi-monitor setups this will be applied to all monitors. If you are using i3-gaps (>= 4.17), you can set `gaps top X` or `gaps bottom X` in your i3 config to reserve space for the bar where `X` is the number of pixels you want to reserve. **Note:** On multi-monitor setups this will be applied to all monitors.
## Version Mismatch between `xcb-proto` and `libxcb-randr0-dev` on Ubuntu 17.04 ## Version Mismatch between `xcb-proto` and `libxcb-randr0-dev` on Ubuntu 17.04
**Problem:** On Ubuntu 17.04 (and possibly others), the `xcb-proto` version does not match the version of the `libxcb-*` packages, especially `libxcb-randr0-dev`. This creates problems with the header files. If you get the following or a similar compiler error, this fix may be for you: **Problem:** On Ubuntu 17.04 (and possibly others), the `xcb-proto` version does not match the version of the `libxcb-*` packages, especially `libxcb-randr0-dev`. This creates problems with the header files. If you get the following or a similar compiler error, this fix may be for you: