Mirrors/gBar
1
0
Fork 0
mirror of https://github.com/scorpion-26/gBar.git synced 2024-11-22 03:02:49 +00:00
Code Issues Projects Releases Packages Wiki Activity

Update bug_report.md

Browse source
This commit is contained in:
scorpion-26 2023-11-01 17:40:15 +01:00 committed by GitHub
parent 1f6ad2aab7
commit 48c0f4814d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
.github/ISSUE_TEMPLATE/bug_report.md vendored
View file

@ -9,24 +9,30 @@ assignees: ''
*Please fill out this form and delete the defaults(everything not in bold font), so I can help you better* *Please fill out this form and delete the defaults(everything not in bold font), so I can help you better*
**Describe the bug** **Describe the bug**
What doesn't work? Please be as precise as possible. What doesn't work? Please be as precise as possible.
e.g.: gBar crashes on hovering e.g.: "gBar crashes on hovering the RAM sensor module. No other modules are affected."
**Steps to Reproduce** **Steps to Reproduce**
What did you do, that triggered the issue? What did you do, that triggered the issue?
e.g.: e.g.:
1. Open the bar 1. Open the bar
2. Hover over item 2. Hover over the RAM sensor module
3. gBar crashes 3. gBar crashes
**Expected behavior** **Expected behavior**
What do you expect should happen? What do you expect should happen?
e.g.: gBar shouldn't crash, but stay open e.g.: gBar shouldn't crash, but stay open
**Screenshots/Error logs** **Screenshots/Error logs**
Please include as much information about the crash as possible.
If it is a visual glitch, please include a screenshot/video. Please include as much information about the crash/bug as possible.
If it is a crash, please include the logs. - If it is a visual glitch, please include a screenshot/video as well as any modifications to the css (if any).
- If it is a *crash* (e.g. ```Segmentation fault (Core dumped)``` in the console), please include the log (```/tmp/gBar-<pid>.log``` or from the console) and a crash stack trace. They can e.g. be found via journalctl (```journalctl --boot=0 --reverse```) if systemd-coredump is used.
- If it is an *assert failed* (Last line in the log reads ```[Exiting due to assert failed]```) please include the log (```/tmp/gBar-<pid>.log``` or from the console).
- The config (```~/.config/gBar/config```) used is always valuable to diagnose an issue, so please include it.
**Information about your system and gBar** **Information about your system and gBar**
- OS: [e.g. Arch, Ubuntu, ...] - OS: [e.g. Arch, Ubuntu, ...]