Add note about AUR helpers to jsoncpp issue

patrick96 2020-12-01 11:43:23 +01:00
parent 5a3be7d07f
commit 8996801f8e
No known key found for this signature in database
GPG Key ID: 521E5E03AEBCA1A7
1 changed files with 6 additions and 0 deletions

@ -68,6 +68,12 @@ 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.
**Note:** If you are using a program to automatically compile polybar for your
(for example an AUR helper), just reinstalling may not solve this problem, the
program may just reuse already compiled binaries. You need to make sure that
polybar is *recompiled*. How to do that depends on the program, but most offer a
way to force a rebuild or a way to clear the cache for certain packages.
## 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.