49 lines
1.6 KiB
YAML
49 lines
1.6 KiB
YAML
name: Crash Report
|
|
description: Quickshell has crashed
|
|
labels: ["bug", "crash"]
|
|
body:
|
|
- type: textarea
|
|
id: userinfo
|
|
attributes:
|
|
label: What caused the crash
|
|
description: |
|
|
Any information likely to help debug the crash. What were you doing when the crash occurred,
|
|
what changes did you make, can you get it to happen again?
|
|
- type: textarea
|
|
id: report
|
|
attributes:
|
|
label: Report file
|
|
description: Attach `report.txt` here.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: logs
|
|
attributes:
|
|
label: Log file
|
|
description: |
|
|
Attach `log.qslog.log` here. If it is too big to upload, compress it.
|
|
|
|
You can preview the log if you'd like using `quickshell read-log <path-to-log>`.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: config
|
|
attributes:
|
|
label: Configuration
|
|
description: |
|
|
Attach your configuration here, preferrably in full (not just one file).
|
|
Compress it into a zip, tar, etc.
|
|
|
|
This will help us reproduce the crash ourselves.
|
|
- type: textarea
|
|
id: bt
|
|
attributes:
|
|
label: Backtrace
|
|
description: |
|
|
GDB usually produces better stacktraces than quickshell can. Consider attaching a gdb backtrace
|
|
following the instructions below.
|
|
|
|
1. Run `coredumpctl debug <pid>` where `pid` is the number shown after "Crashed process ID"
|
|
in the crash reporter.
|
|
2. Once it loads, type `bt -full` (then enter)
|
|
3. Copy the output and attach it as a file or in a spoiler.
|