mirror of
https://github.com/polybar/polybar.git
synced 2024-11-11 13:50:56 -05:00
07913058fb
The issue tracker should be for bugs only. Right now actual bugs can easily fall through the cracks because we get stuck answering questions and basically providing tech support. This move is also intended to have more traffic to our subreddit and IRC channel with the hope that the community can also help itself out.
44 lines
1,019 B
Markdown
44 lines
1,019 B
Markdown
---
|
|
name: Bug Report
|
|
about: Create a report for something that misbehaves
|
|
|
|
---
|
|
|
|
## Describe the issue
|
|
*A clear and concise description of what the bug is.*
|
|
|
|
**Expected behavior:**
|
|
|
|
*A clear and concise description of what you expected to happen.*
|
|
|
|
**Actual behavior:**
|
|
|
|
*What actually happens*
|
|
|
|
**Was it working before?**
|
|
* Did you also experience this bug in an earlier version of polybar?
|
|
* If no, what was the last version where this worked correctly?
|
|
|
|
## To Reproduce
|
|
*A minimal but complete config with which the problem occurs:*
|
|
```dosini
|
|
|
|
```
|
|
*List any other steps needed to reproduce the issue besides starting polybar with the config you posted above.*
|
|
|
|
## Polybar Log
|
|
*Post everything polybar outputs to the terminal when you run it and the issue occurs below*
|
|
```
|
|
|
|
```
|
|
|
|
## Screenshots
|
|
*If applicable, add screenshots to help explain your problem.*
|
|
|
|
## Environment:
|
|
* WM:
|
|
* Distro:
|
|
* Output of `polybar -vvv`:
|
|
|
|
## Additional context
|
|
*Add any other context that you think is necessary about the problem here.*
|