Package Details: polybar 3.4.1-1

Git Clone URL: https://aur.archlinux.org/polybar.git (read-only)
Package Base: polybar
Description: A fast and easy-to-use status bar
Upstream URL: https://github.com/polybar/polybar
Keywords: bar bspwm i3 lemonbar lemonbuddy polybar
Licenses: MIT
Conflicts: polybar-git
Submitter: jaagr
Maintainer: jaagr (NBonaparte, patrick96)
Last Packager: patrick96
Votes: 228
Popularity: 11.99
First Submitted: 2016-11-19 05:09
Last Updated: 2019-10-30 13:08

Pinned Comments

patrick96 commented on 2019-09-17 12:07

To solve the libjsoncpp issue you need to recompile polybar (particularly re-link). The easiest way to do that is to use a fresh clone of this AUR repo and run makepkg there. It is probably also possible with your AUR helper by telling it to remove existing build files (or deleting them yourself).

@victorz a clean installation will solve the issue. If it didn't for you, you likely reused an already compiled polybar executable when building the package.

TheGreatAndyChow commented on 2019-04-23 03:46

For problems with conda, simply "conda deactivate", it will install. No need to purge path or remove anaconda.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

patrick96 commented on 2019-10-31 07:41

@ak04nv I don't think you can install arch packages as if they were pip packages. However, many packages are available on pip as well, though xcbgen is not. In the issue you linked, they copy the xcbgen folder into their pyenv folder and that works. But I would suggest either building polybar in a clean chroot or temporarily deactivating pyenv with pyenv local system.

ak04nv commented on 2019-10-31 02:40

Building error:

CMake Error at lib/xpp/CMakeLists.txt:70 (message):
  Missing required python module: xcbgen

GitHub issue

BTW, is it possible to install all python-* packages in virtualenv folder for make package? Like this:

$ python3 -m venv .venv
$ source .venv/bin/activate
$ pip install sphinx
... // Run cmake

victorz commented on 2019-09-18 06:41

@patrick96, you're right. I should have rebuilt the package, rather than just reinstalling the package. Thanks!

patrick96 commented on 2019-09-17 21:46

@4shadoww You are correct. Added it to makedepends

4shadoww commented on 2019-09-17 17:47

Should python-sphinx be on make dependencies? Build doesn't succeed if it isn't installed.

patrick96 commented on 2019-09-17 12:07

To solve the libjsoncpp issue you need to recompile polybar (particularly re-link). The easiest way to do that is to use a fresh clone of this AUR repo and run makepkg there. It is probably also possible with your AUR helper by telling it to remove existing build files (or deleting them yourself).

@victorz a clean installation will solve the issue. If it didn't for you, you likely reused an already compiled polybar executable when building the package.

patrick96 commented on 2019-09-17 12:04

@qwertea i3 is not a hard dependency. It's an optional dependency because polybar can work without it (even if it is compiled with i3 support) and a build dependency because we want i3 support to be enabled in this package.

victorz commented on 2019-09-17 08:23

A clean installation of polybar did not fix the shared library issue for me. I had to do a # ln -s /usr/lib/libjsoncpp.so{,.20}.

awc commented on 2019-09-16 20:52

@kyechou I had this same issue. A clean installation of polybar fixed it.

kyechou commented on 2019-09-16 20:50

It fails to launch after I upgraded jsoncpp. (libjsoncpp.so.21)

polybar: error while loading shared libraries: libjsoncpp.so.20: cannot open shared object file: No such file or directory