Updated Known Issues (markdown)

Patrick Ziegler 2020-04-07 11:26:47 +02:00
parent 877e0a8776
commit ef65d76654
1 changed files with 0 additions and 2 deletions

@ -97,8 +97,6 @@ This issue occurs because `jsoncpp` changes the name of their `.so` file every r
**Fix:** You have to recompile polybar, so that it links to the new `.so` file. If you use precompiled binaries from a repository, you either have to compile polybar yourself or contact the packager so that they can recompile polybar and publish a package with proper linkage. **Fix:** You have to recompile polybar, so that it links to the new `.so` file. If you use precompiled binaries from a repository, you either have to compile polybar yourself or contact the packager so that they can recompile polybar and publish a package with proper linkage.
Alternatively you can symlink the `libjsoncpp.so.XX` file from the error message to `libjsoncpp.so` (most likely in the `/usr/lib` directory). **Warning:** This could potentially break other packages, only use this as a last resort, recompiling is preferable in every situation.
## 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.