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

Remove jsoncpp issue

Patrick Ziegler 2017-12-03 18:07:38 +01:00
parent c51e57761f
commit 9952c44f80
1 changed files with 1 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Known-Issues.md

@ -2,24 +2,10 @@ This page lists some of the issues one can encounter when using polybar. Either
# Contents # Contents
- [Setting Module Backgrounds when using Gradients](#setting-module-backgrounds-when-using-gradients) - [Setting Module Backgrounds when using Gradients](#setting-module-backgrounds-when-using-gradients)
- [libjsoncpp.so.11: cannot open shared object file](#libjsoncppso11-cannot-open-shared-object-file)
## Setting Module Backgrounds when using Gradients ## Setting Module Backgrounds when using Gradients
**Problem:** When you use a gradient as your polybar background, explicitly setting any module's background color to whatever you have set as `background-0`, either through the `-background` setting or the `%{B}` formatting tag, will not change the background color at all. **Problem:** When you use a gradient as your polybar background, explicitly setting any module's background color to whatever you have set as `background-0`, either through the `-background` setting or the `%{B}` formatting tag, will not change the background color at all.
**Workaround:** If you want to explicitly set a module's (or parts of its) background to `background-0`, use a color that is almost the same. E.g. if `background-0` is `#FFFF00` use `#FFFF01`. **Workaround:** If you want to explicitly set a module's (or parts of its) background to `background-0`, use a color that is almost the same. E.g. if `background-0` is `#FFFF00` use `#FFFF01`.
This behaviour was introduced in [`#831`](https://github.com/jaagr/polybar/pull/831), to resolve the issue described in [`#759`](https://github.com/jaagr/polybar/issues/759). There is no way to resolve this without some major code changes to the renderer. This behaviour was introduced in [`#831`](https://github.com/jaagr/polybar/pull/831), to resolve the issue described in [`#759`](https://github.com/jaagr/polybar/issues/759). There is no way to resolve this without some major code changes to the renderer.
## libjsoncpp.so.11: cannot open shared object file
**Problem:** On systems with newer versions of `jsoncpp` (1.8.3 and up) you will get an error along the lines of
```
polybar: error while loading shared libraries: libjsoncpp.so.11: cannot open shared object file
```
when running polybar.
**Workaround:** You have to recompile polybar against the new library. It is possible that recompilation fails with the following error:
```
error: ‘Reader’ is deprecated: Use CharReader and CharReaderBuilder instead [-Werror=deprecated-declarations]
```
If this happens, you have to apply the https://github.com/jaagr/i3ipcpp/pull/4 patch to the `i3ipcpp` submodule.