Package Details: polybar 3.1.0-2

Git Clone URL: (read-only)
Package Base: polybar
Description: A fast and easy-to-use status bar
Upstream URL:
Keywords: bar bspwm i3 lemonbar lemonbuddy polybar
Licenses: MIT
Conflicts: polybar-git
Submitter: jaagr
Maintainer: jaagr (NBonaparte, patrick96)
Last Packager: NBonaparte
Votes: 67
Popularity: 10.028166
First Submitted: 2016-11-19 05:09
Last Updated: 2017-12-03 23:31

Dependencies (18)

Required by (0)

Sources (1)

Latest Comments

patrick96 commented on 2017-12-10 08:30

@bokal Are you actually running the binary you newly compiled against jsoncpp-1.8.3? The error message you get suggests the executed polybar binary was built against an older jsoncpp version

bokal commented on 2017-12-10 08:26

Polybar builds fine with jsoncpp-1.8.3, but I would still get this error:

% polybar  
polybar: error while loading shared libraries: cannot open shared object file: No such file or directory

Super ugly, but works:

% ln -s /usr/lib/ /usr/lib/

patrick96 commented on 2017-12-03 17:12

The jsoncpp build issues have been resolved in the new version

benoliver999 commented on 2017-12-03 15:51

The patched PKGBUILD builds for me then shits the bed at this when using pacaur:

:: polybar package(s) failed to install.

:: ensure package version does not mismatch between .SRCINFO and PKGBUILD

:: ensure package name has a VCS suffix if this is a devel package

However, doing it manually works fine.

You can still use pacaur if you really want to though, just replace the PKGBUILD with the patched one then:

cd .cache/pacaur/polybar makepkg -si

arvidsaur commented on 2017-12-02 12:22

@zopieux huh thats, weird what error did you get?

zopieux commented on 2017-12-01 17:57

For some reason the patched PKGBUILD linked by @arvidsaur did not work.

As a temporary fix, one can simply downgrade jsoncpp to 1.8.1:
$ pacman/pacaur -U /var/cache/pacman/pkg/jsoncpp-1.8.1-1-x86_64.pkg.tar.xz

arvidsaur commented on 2017-12-01 09:16

Don't know if this is the correct way to apply a patch, but it seems to work.

patrick96 commented on 2017-12-01 05:35

With the new jsoncpp version (1.8.3) the polybar build may fail, if that happens, you have to apply this [1] patch to the i3ipcpp submodule.


patrick96 commented on 2017-10-18 17:31

@Chais Yes any of the optional dependencies that are labeled with "module" support, are compile-time dependencies

Chais commented on 2017-10-18 16:03

According to [1] wireless_tools is a compile-time dependency, if the network module is to work at all.


All comments