Package Details: polybar 3.0.5-4

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/jaagr/polybar
Keywords: bar bspwm i3 lemonbar lemonbuddy polybar
Licenses: MIT
Conflicts: polybar-git
Submitter: jaagr
Maintainer: jaagr (NBonaparte, patrick96)
Last Packager: patrick96
Votes: 57
Popularity: 8.657494
First Submitted: 2016-11-19 05:09
Last Updated: 2017-09-13 11:24

Dependencies (18)

Required by (0)

Sources (1)

Latest Comments

Jeston commented on 2017-09-23 13:38

@patrick96, thanks for the advice, that really helped. This is how I ended up getting it to work.

-- Did a fresh install of miniconda

-- Installed xcb-proto [conda install -c conda-forge xcb-proto] ( before i had xorg-xcb-proto)

-- Then I just deleted [usr/lib/python2.7/site-packages/xcbgen] and the build worked

I also had a second arch desktop that i didn't experiment with and all I had to do was install the correct xcb-proto package from conda-forge and it worked fine.

Thanks for the help!

patrick96 commented on 2017-09-22 18:19

@jeston, we've had the same issue before in issue 756 ([1]), it was because of an outdated version of xcb-proto. In your case, I think it's because for whatever reason xcbgen was found with python 2.7, jaagr pointed out in [2] that it requires python 3. You'll need to figure out what package those files belong to, if they come from pacman you can check this with

pacman -Qo /usr/lib/python2.7/site-packages/xcbgen/xtypes.py

but they also may come from another package manager (pip, anaconda etc), you'll need to figure this out. Wherever those files come from, you'll need to remove them by uninstalling the package. After that the build should work.

[1]: https://github.com/jaagr/polybar/issues/756
[2]: https://github.com/jaagr/polybar/issues/502#issuecomment-289754010

Jeston commented on 2017-09-22 03:01

I am using Anaconda and i didnt have that package, but did add it and im still getting an error. Im not really familiar with virtualenv or how they work so ive never intentionally created one.

[jeston@archlap ~]$ conda info
Current conda install:

platform : linux-64
conda version : 4.3.25
conda is private : False
conda-env version : 4.3.25
conda-build version : not installed
python version : 3.6.0.final.0
requests version : 2.12.4
root environment : /home/jeston/Apps/miniconda3 (writable)
default environment : /home/jeston/Apps/miniconda3
envs directories : /home/jeston/Apps/miniconda3/envs
/home/jeston/.conda/envs
package cache : /home/jeston/Apps/miniconda3/pkgs
/home/jeston/.conda/pkgs
channel URLs : https://repo.continuum.io/pkgs/free/linux-64
https://repo.continuum.io/pkgs/free/noarch
https://repo.continuum.io/pkgs/r/linux-64
https://repo.continuum.io/pkgs/r/noarch
https://repo.continuum.io/pkgs/pro/linux-64
https://repo.continuum.io/pkgs/pro/noarch
config file : None
netrc file : None
offline mode : False
user-agent : conda/4.3.25 requests/2.12.4 CPython/3.6.0 Linux/4.12.13-1-ARCH arch/ glibc/2.26
UID:GID : 1000:100


[jeston@archlap ~]$ conda list
# packages in environment at /home/jeston/Apps/miniconda3:
#
cffi 1.9.1 py36_0
conda 4.3.25 py36_0
conda-env 2.6.0 0
cryptography 1.7.1 py36_0
idna 2.2 py36_0
libffi 3.2.1 1
mkl 2017.0.3 0
numpy 1.13.1 py36_0
openssl 1.0.2k 0
pandas 0.20.3 py36_0
pip 9.0.1 py36_1
pyasn1 0.1.9 py36_0
pycosat 0.6.1 py36_1
pycparser 2.17 py36_0
pyopenssl 16.2.0 py36_0
python 3.6.0 0
python-dateutil 2.6.1 py36_0
pytz 2017.2 py36_0
readline 6.2 2
requests 2.12.4 py36_0
ruamel_yaml 0.11.14 py36_1
setuptools 27.2.0 py36_0
six 1.10.0 py36_0
sqlite 3.13.0 0
tk 8.5.18 0
wheel 0.29.0 py36_0
xorg-xcb-proto 1.12 py36_3 conda-forge
xz 5.2.2 1
yaml 0.1.6 0
zlib 1.2.8 3


==> polybar dependencies:
- cairo (already installed)
- xcb-util-image (already installed)
- xcb-util-wm (already installed)
- xcb-util-xrm (already installed)
- clang (already installed) [makedepend]
- cmake (already installed) [makedepend]
- git (already installed) [makedepend]
- python (already installed) [makedepend]
- python2 (already installed) [makedepend]
- pkg-config (already installed) [makedepend]


-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/yaourt-tmp-jeston/aur-polybar/src/polybar/build
Scanning dependencies of target xpp
[ 1%] Linking CXX static library libxpp.a
Traceback (most recent call last):
File "/tmp/yaourt-tmp-jeston/aur-polybar/src/polybar/lib/xpp/generators/cpp_client.py", line 3163, in <module>
from xcbgen.state import Module
File "/usr/lib/python2.7/site-packages/xcbgen/state.py", line 7, in <module>
from xcbgen import matcher
File "/usr/lib/python2.7/site-packages/xcbgen/matcher.py", line 12, in <module>
from xcbgen.xtypes import *
File "/usr/lib/python2.7/site-packages/xcbgen/xtypes.py", line 1221, in <module>
class EventStruct(Union):
File "/usr/lib/python2.7/site-packages/xcbgen/xtypes.py", line 1239, in EventStruct
out = __main__.output['eventstruct']
KeyError: 'eventstruct'
make[2]: *** [lib/xpp/CMakeFiles/xpp.dir/build.make:70: lib/xpp/libxpp.a] Error 1
make[1]: *** [CMakeFiles/Makefile2:385: lib/xpp/CMakeFiles/xpp.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

patrick96 commented on 2017-09-21 06:27

@jeston You probably are in a virtualenv as well or maybe you are using python anaconda. Building polybar won't work straight away with those. Either disable them when building or install xcb-proto in anaconda or your virtualenv

Jeston commented on 2017-09-21 01:20

Im seeing the same error.

-- Checking for module 'xcb-proto'
-- Found xcb-proto, version 1.12
-- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.13", minimum required is "2.7")
-- XCB[XCB]: Found component XCB
-- Found XCB_XCB: /usr/lib/libxcb.so
-- XCB[ICCCM]: Found component ICCCM
-- Found XCB_ICCCM: /usr/lib/libxcb-icccm.so
-- XCB[EWMH]: Found component EWMH
-- Found XCB_EWMH: /usr/lib/libxcb-ewmh.so
-- XCB[UTIL]: Found component UTIL
-- Found XCB_UTIL: /usr/lib/libxcb-util.so
-- XCB[IMAGE]: Found component IMAGE
-- Found XCB_IMAGE: /usr/lib/libxcb-image.so
-- Found XCB: /usr/lib/libxcb.so;/usr/lib/libxcb-icccm.so;/usr/lib/libxcb-ewmh.so;/usr/lib/libxcb-util.so;/usr/lib/libxcb-image.so
-- Searching for xcbgen with python2
-- Searching for xcbgen with python3
-- Searching for xcbgen with python
CMake Error at lib/xpp/CMakeLists.txt:55 (message):
Missing required python module: xcbge

apetresc commented on 2017-09-12 15:23

Whoops, please disregard my last comment... I managed to forget I was in a virtualenv on three different machines.

apetresc commented on 2017-09-12 15:22

As of the most recent pkgrel, I'm getting:

-- Searching for xcbgen with python2
-- Searching for xcbgen with python3
-- Searching for xcbgen with python
CMake Error at lib/xpp/CMakeLists.txt:55 (message):
Missing required python module: xcbgen

This happens on multiple machines. I can't figure out which package is supposed to be providing this Python module.

patrick96 commented on 2017-09-12 14:17

The issue with curl should now be fixed in the newest PKGBUILD

Zorbik commented on 2017-08-15 15:03

The curl issue was resolved, fixes are present in polybar-git. Just have to wait for jaagr to add the changes to polybar.
https://github.com/jaagr/polybar/issues/647

alcasa commented on 2017-08-06 13:08

I created a patch to remove the curlbuild include in this stable release, availabe here:
https://gist.github.com/xiamaz/d73327df155f4522367ef8de48f72203

All comments