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

Separate Known Issues in runtime and build issues

patrick96 2020-11-26 14:06:22 +01:00
parent e874cae602
commit b005006957
No known key found for this signature in database
GPG Key ID: 521E5E03AEBCA1A7
1 changed files with 51 additions and 45 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

96
Known-Issues.md

@ -1,17 +1,20 @@
This page lists some of the issues one can encounter when using polybar. Either quirks in polybar's behaviour or actual bugs we haven't been able to fix yet. This page lists some of the issues one can encounter when using polybar. Either quirks in polybar's behaviour or actual bugs we haven't been able to fix yet.
# Contents # Contents
- [`Failed to get root pixmap, default to black (is there a wallpaper?)`](#failed-to-get-root-pixmap-default-to-black-is-there-a-wallpaper) - [Running Polybar](#running-polybar)
- [`Cannot find root pixmap, try a different tool to set the desktop background`](#cannot-find-root-pixmap-try-a-different-tool-to-set-the-desktop-background) * [`Failed to get root pixmap, default to black (is there a wallpaper?)`](#-failed-to-get-root-pixmap--default-to-black--is-there-a-wallpaper---)
- [Building with Anaconda installed](#building-with-anaconda-installed) * [`Cannot find root pixmap, try a different tool to set the desktop background`](#-cannot-find-root-pixmap--try-a-different-tool-to-set-the-desktop-background-)
- [Huge Emojis](#huge-emojis) * [Huge Emojis](#huge-emojis)
- [Click Commands are not Executed](#click-commands-are-not-executed) * [Click Commands are not Executed](#click-commands-are-not-executed)
- [With multiple modules of the same type, actions on those modules always control the leftmost module](#with-multiple-modules-of-the-same-type-actions-on-those-modules-control-the-leftmost-module) * [With multiple modules of the same type, actions on those modules control the leftmost module](#with-multiple-modules-of-the-same-type--actions-on-those-modules-control-the-leftmost-module)
- [Error While Loading Shared Libraries: libjsoncpp](#error-while-loading-shared-libraries-libjsoncpp) * [Error While Loading Shared Libraries: libjsoncpp](#error-while-loading-shared-libraries--libjsoncpp)
- [Setting Module Backgrounds when using Gradients](#setting-module-backgrounds-when-using-gradients) * [Setting Module Backgrounds when using Gradients](#setting-module-backgrounds-when-using-gradients)
- [`override-redirect` in i3](#override-redirect-in-i3) * [`override-redirect` in i3](#-override-redirect--in-i3)
- [Mouse Interactions not Working in AwesomeWM](#mouse-interactions-not-working-in-awesomewm) * [Mouse Interactions not Working in AwesomeWM](#mouse-interactions-not-working-in-awesomewm)
- [Compiling Polybar](#compiling-polybar)
* [Building with Anaconda installed](#building-with-anaconda-installed)
# Running Polybar
## `Failed to get root pixmap, default to black (is there a wallpaper?)` ## `Failed to get root pixmap, default to black (is there a wallpaper?)`
Polybar prints this warning when there is no wallpaper set and `pseudo-transparency = true` is set. Polybar will still Polybar prints this warning when there is no wallpaper set and `pseudo-transparency = true` is set. Polybar will still
@ -28,41 +31,6 @@ when rendering transparent colors.
with a tool like `feh` or `nitrogen` with a tool like `feh` or `nitrogen`
## Building with Anaconda installed
**Problem:** On systems using Anaconda compiling polybar will likely fail with one of these error messages:
* `Missing required python module: xcbgen`
* `ERROR: could not calc required_start_align of Struct "xcb.Setup"`
* `Cairo was not compiled with support for the xcb backend`
The general issue is that the libraries and programs provided by Anaconda cannot be used to build polybar in many cases.
**Fix:** The easiest fix is to uninstall Anaconda if you don't need it.
If you can't/don't want to uninstall Anaconda, we need to force polybar to not use any resources provided by Anaconda.
This can be done by temporarily removing any paths that point to anaconda from both the `$PATH` and `$PKG_CONFIG_PATH` environment variables in the terminal before building polybar.
People have reported that `conda deactivate` does that for you for the currently open terminal. If that doesn't work, try doing it manually:
For example if your `PATH` variable contains:
```
/home/<user>/anaconda2/bin:/home/<user>/bin:...:/usr/bin
```
Remove `/home/<user>/anaconda2/bin` and reexport the variable:
```
export PATH=/home/<user>/bin:...:/usr/bin
```
Do the same thing for `PKG_CONFIG_PATH` (though this variable is often already empty). Now you should be able to build
polybar with either the `build.sh` script or `cmake` and `make`. Make sure that you do a clean build (redownload all
polybar sources).
This was reported in [`#502`](https://github.com/polybar/polybar/issues/502),
[`#733`](https://github.com/polybar/polybar/issues/733), [`#659`](https://github.com/polybar/polybar/issues/659),
[`#1629`](https://github.com/polybar/polybar/issues/1629)
## Huge Emojis ## Huge Emojis
**Problem:** When using the Noto Emoji font, Emojis appear extremely big on the bar. Setting the `size` property doesn't help. **Problem:** When using the Noto Emoji font, Emojis appear extremely big on the bar. Setting the `size` property doesn't help.
@ -122,3 +90,41 @@ mouse events on the bar once polybar is the focused window.
**Solution:** The only fix for this seems to be to set `override-redirect = **Solution:** The only fix for this seems to be to set `override-redirect =
true` in your bar section. This tells AwesomeWM to not manage the polybar true` in your bar section. This tells AwesomeWM to not manage the polybar
window. window.
# Compiling Polybar
## Building with Anaconda installed
**Problem:** On systems using Anaconda compiling polybar will likely fail with one of these error messages:
* `Missing required python module: xcbgen`
* `ERROR: could not calc required_start_align of Struct "xcb.Setup"`
* `Cairo was not compiled with support for the xcb backend`
The general issue is that the libraries and programs provided by Anaconda cannot be used to build polybar in many cases.
**Fix:** The easiest fix is to uninstall Anaconda if you don't need it.
If you can't/don't want to uninstall Anaconda, we need to force polybar to not use any resources provided by Anaconda.
This can be done by temporarily removing any paths that point to anaconda from both the `$PATH` and `$PKG_CONFIG_PATH` environment variables in the terminal before building polybar.
People have reported that `conda deactivate` does that for you for the currently open terminal. If that doesn't work, try doing it manually:
For example if your `PATH` variable contains:
```
/home/<user>/anaconda2/bin:/home/<user>/bin:...:/usr/bin
```
Remove `/home/<user>/anaconda2/bin` and reexport the variable:
```
export PATH=/home/<user>/bin:...:/usr/bin
```
Do the same thing for `PKG_CONFIG_PATH` (though this variable is often already empty). Now you should be able to build
polybar with either the `build.sh` script or `cmake` and `make`. Make sure that you do a clean build (redownload all
polybar sources).
This was reported in [`#502`](https://github.com/polybar/polybar/issues/502),
[`#733`](https://github.com/polybar/polybar/issues/733), [`#659`](https://github.com/polybar/polybar/issues/659),
[`#1629`](https://github.com/polybar/polybar/issues/1629)