Remove event struct key error

Was fixed in 3.2.0
patrick96 2019-01-17 14:24:02 +01:00
parent 421c4457f2
commit be574f717c
No known key found for this signature in database
GPG Key ID: 521E5E03AEBCA1A7
1 changed files with 0 additions and 19 deletions

@ -8,7 +8,6 @@ This page lists some of the issues one can encounter when using polybar. Either
- [Error While Loading Shared Libraries: libjsoncpp](#error-while-loading-shared-libraries-libjsoncpp) - [Error While Loading Shared Libraries: libjsoncpp](#error-while-loading-shared-libraries-libjsoncpp)
- [Setting Module Backgrounds when using Gradients](#setting-module-backgrounds-when-using-gradients) - [Setting Module Backgrounds when using Gradients](#setting-module-backgrounds-when-using-gradients)
- [`override-redirect` in i3](#override-redirect-in-i3) - [`override-redirect` in i3](#override-redirect-in-i3)
- [KeyError: 'eventstruct'](#keyerror-eventstruct)
- [Version Mismatch between `xcb-proto` and `libxcb-randr0-dev` on Ubuntu 17.04](#version-mismatch-between-xcb-proto-and-libxcb-randr0-dev-on-ubuntu-1704) - [Version Mismatch between `xcb-proto` and `libxcb-randr0-dev` on Ubuntu 17.04](#version-mismatch-between-xcb-proto-and-libxcb-randr0-dev-on-ubuntu-1704)
## `Missing required python module: xcbgen` with Anaconda ## `Missing required python module: xcbgen` with Anaconda
@ -74,24 +73,6 @@ This behaviour was introduced in [`#831`](https://github.com/jaagr/polybar/pull/
**Workaround:** The workaround that some people use, is to create a full-width fully transparent dummy bar on the same monitor and in the same position (with `override-redirect = false`), so that i3 reserves space for this dummy bar, effectively also reserving space for our actual bar. The real bar may need to have `wm-restack = i3` set for it to not overlap with fullscreen windows. **Note:** This requires that you have a composition manager running because the dummy bar may overlap the real bar. **Workaround:** The workaround that some people use, is to create a full-width fully transparent dummy bar on the same monitor and in the same position (with `override-redirect = false`), so that i3 reserves space for this dummy bar, effectively also reserving space for our actual bar. The real bar may need to have `wm-restack = i3` set for it to not overlap with fullscreen windows. **Note:** This requires that you have a composition manager running because the dummy bar may overlap the real bar.
## KeyError: 'eventstruct'
**Problem:** When building version 3.1.0, during `make` (or `sudo make install`), you may get the following error:
```python
Traceback (most recent call last):
File "/tmp/polybar/lib/xpp/generators/cpp_client.py", line 3163, in <module>
from xcbgen.state import Module
File "/usr/lib/python3.6/site-packages/xcbgen/state.py", line 7, in <module>
from xcbgen import matcher
File "/usr/lib/python3.6/site-packages/xcbgen/matcher.py", line 12, in <module>
from xcbgen.xtypes import *
File "/usr/lib/python3.6/site-packages/xcbgen/xtypes.py", line 1221, in <module>
class EventStruct(Union):
File "/usr/lib/python3.6/site-packages/xcbgen/xtypes.py", line 1239, in EventStruct
out = __main__.output['eventstruct']
KeyError: 'eventstruct'
```
**Fix:** You have to manually update the `xpp` submodule. To do that, go into the `lib/xpp` folder and execute `git checkout master` and `rm include/xpp/proto/*`, the second command deletes the already generated, but faulty, headers. After that you can go back into the `build` folder and run `make` again. **Note:** With this fix, you cannot use the `build.sh` script to build polybar.
## Version Mismatch between `xcb-proto` and `libxcb-randr0-dev` on Ubuntu 17.04 ## Version Mismatch between `xcb-proto` and `libxcb-randr0-dev` on Ubuntu 17.04
**Problem:** On Ubuntu 17.04 (and possibly others), the `xcb-proto` version does not match the version of the `libxcb-*` packages, especially `libxcb-randr0-dev`. This creates problems with the header files. If you get the following or a similar compiler error, this fix may be for you: **Problem:** On Ubuntu 17.04 (and possibly others), the `xcb-proto` version does not match the version of the `libxcb-*` packages, especially `libxcb-randr0-dev`. This creates problems with the header files. If you get the following or a similar compiler error, this fix may be for you:
~~~ ~~~