-
-
Notifications
You must be signed in to change notification settings - Fork 723
Description
Describe the issue
I built polybar right after forking and cloning the repo. Now it doesn't start and in the log says [read below].
Expected behavior:
Polybar should start.
Actual behavior:
Polybar doesn't start.
Was it working before?
I downloaded, some days ago, the latest release (with sha256sum: 4d22c977969a561f561fdc7a609073854d8fea8a9eec6941e12a80457edcb63a) and building with that it was working.
Also with the AUR stable version (the one I use daily) it was working.
To Reproduce
Clone the repo with git clone --recursive https://github.com/polybar/polybar, and build with:
mkdir build
cd build
cmake ..
make -j$(nproc)
# Optional. This will install the polybar executable in /usr/local/bin
sudo make install(from the wiki)
Polybar Log
Post everything polybar outputs to the terminal when you run it and the issue occurs below
---
polybar|notice: Parsing config file: /home/koraynilay/.config/polybar/config
polybar|error: /home/koraynilay/.config/polybar/config:1: Key name '<feff>;' is empty or contains forbidden characters.
---
Environment:
- WM: i3
- Distro: Arch Linux
- Output of
polybar -vvv:
polybar 3.4.0-96-gfc42da8-dev
Features: +alsa +curl +i3 +mpd +network(libnl) +pulseaudio +xkeyboard
X extensions: +randr (+monitors) +composite +xkb +xrm +xcursor
Build type: Release
Compiler: /usr/bin/c++
Compiler flags: -Wall -Wextra -Wpedantic -O3 -DNDEBUG
Linker flags:
Additional context
I did a bit of research, and 0xFEFF is the Byte Order Mark. So there could be a problem while reading the encoding.