|
| 1 | +name: Crash Report |
| 2 | +description: Quickshell has crashed |
| 3 | +labels: ["bug", "crash"] |
| 4 | +body: |
| 5 | + - type: textarea |
| 6 | + id: crashinfo |
| 7 | + attributes: |
| 8 | + label: General crash information |
| 9 | + description: | |
| 10 | + Paste the contents of the `info.txt` file in your crash folder here. |
| 11 | + value: "<details> <summary>General information</summary> |
| 12 | +
|
| 13 | +
|
| 14 | + ``` |
| 15 | +
|
| 16 | + <Paste the contents of the file here inside of the triple backticks> |
| 17 | +
|
| 18 | + ``` |
| 19 | +
|
| 20 | +
|
| 21 | + </details>" |
| 22 | + validations: |
| 23 | + required: true |
| 24 | + - type: textarea |
| 25 | + id: userinfo |
| 26 | + attributes: |
| 27 | + label: What caused the crash |
| 28 | + description: | |
| 29 | + Any information likely to help debug the crash. What were you doing when the crash occurred, |
| 30 | + what changes did you make, can you get it to happen again? |
| 31 | + - type: textarea |
| 32 | + id: dump |
| 33 | + attributes: |
| 34 | + label: Minidump |
| 35 | + description: | |
| 36 | + Attach `minidump.dmp` here. If it is too big to upload, compress it. |
| 37 | +
|
| 38 | + You may skip this step if quickshell crashed while processing a password |
| 39 | + or other sensitive information. If you skipped it write why instead. |
| 40 | + validations: |
| 41 | + required: true |
| 42 | + - type: textarea |
| 43 | + id: logs |
| 44 | + attributes: |
| 45 | + label: Log file |
| 46 | + description: | |
| 47 | + Attach `log.qslog` here. If it is too big to upload, compress it. |
| 48 | +
|
| 49 | + You can preview the log if you'd like using `quickshell read-log <path-to-log>`. |
| 50 | + validations: |
| 51 | + required: true |
| 52 | + - type: textarea |
| 53 | + id: config |
| 54 | + attributes: |
| 55 | + label: Configuration |
| 56 | + description: | |
| 57 | + Attach your configuration here, preferrably in full (not just one file). |
| 58 | + Compress it into a zip, tar, etc. |
| 59 | +
|
| 60 | + This will help us reproduce the crash ourselves. |
| 61 | + - type: textarea |
| 62 | + id: bt |
| 63 | + attributes: |
| 64 | + label: Backtrace |
| 65 | + description: | |
| 66 | + If you have gdb installed and use systemd, or otherwise know how to get a backtrace, |
| 67 | + we would appreciate one. (You may have gdb installed without knowing it) |
| 68 | +
|
| 69 | + 1. Run `coredumpctl debug <pid>` where `pid` is the number shown after "Crashed process ID" |
| 70 | + in the crash reporter. |
| 71 | + 2. Once it loads, type `bt -full` (then enter) |
| 72 | + 3. Copy the output and attach it as a file or in a spoiler. |
0 commit comments