mirror of https://github.com/polybar/polybar.git
Describe libjsoncpp linkage issue
parent
bc6ce52058
commit
46e953e3bd
|
@ -1,11 +1,21 @@
|
|||
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
|
||||
- [Error While Loading Shared Libraries: libjsoncpp](#error-while-loading-shared-libraries-libjsoncpp)
|
||||
- [Setting Module Backgrounds when using Gradients](#setting-module-backgrounds-when-using-gradients)
|
||||
|
||||
## Error While Loading Shared Libraries: libjsoncpp
|
||||
**Problem:** When you update the `jsoncpp` package, you might get the following error, when trying to run polybar:
|
||||
```
|
||||
polybar: error while loading shared libraries: libjsoncpp.so.XX: cannot open shared object file: No such file or directory
|
||||
```
|
||||
This issue occurs because `jsoncpp` changes the name of their `.so` file every release and there really isn't anything we can do about that.
|
||||
|
||||
**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).
|
||||
|
||||
## 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.
|
||||
|
||||
**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.
|
||||
|
|
Loading…
Reference in New Issue