aboutsummaryrefslogtreecommitdiffhomepage
path: root/docs
diff options
context:
space:
mode:
authorvaxerski <[email protected]>2023-03-31 13:16:52 +0100
committervaxerski <[email protected]>2023-03-31 13:16:52 +0100
commit5688e24b8aa7333b606963f605161c96f510c84d (patch)
tree780c2f4975096860a6df177bad3d391fab71948e /docs
parent3d9bf17f117640edcb5efcc361fdff4096ee072d (diff)
downloadHyprland-5688e24b8aa7333b606963f605161c96f510c84d.tar.gz
Hyprland-5688e24b8aa7333b606963f605161c96f510c84d.zip
docs: update crash report dirs
Diffstat (limited to 'docs')
-rw-r--r--docs/ISSUE_GUIDELINES.md14
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/ISSUE_GUIDELINES.md b/docs/ISSUE_GUIDELINES.md
index 05adbe89..b8d007c2 100644
--- a/docs/ISSUE_GUIDELINES.md
+++ b/docs/ISSUE_GUIDELINES.md
@@ -45,6 +45,13 @@ cat /tmp/hypr/$(ls -t /tmp/hypr/ | head -n 2 | tail -n 1)/hyprland.log
basically, directories in /tmp/hypr are your sessions.
+## Obtaining the Hyprland Crash Report (v0.22.0beta and up)
+
+If you have `$XDG_CACHE_HOME` set, the crash report directory is `$XDG_CACHE_HOME/hyprland`. If not, it's `~/.hyprland`
+
+Go to the crash report directory and you should find a file named `hyprlandCrashReport[XXXX].txt` where `[XXXX]` is the PID of the process that crashed.
+
+Attach that file to your issue.
## Obtaining the Hyprland coredump (v0.21.0beta and below)
If you are on systemd, you can simply use
```
@@ -58,13 +65,6 @@ coredumpctl info [PID]
```
where `[PID]` is the PID you remembered.
-## Obtaining the Hyprland Crash Report (v0.22.0beta and up)
-Go to `~/.hyprland/` and you should find a file named `hyprlandCrashReport[XXXX].txt` where `[XXXX]` is the PID of the process that crashed.
-
-If you do not see it, make sure you have "show hidden files" enabled in your file manager.
-
-Attach that file to your issue.
-
## Obtaining the debug Hyprland coredump
A debug coredump provides more information for debugging and may speed up the process of fixing the bug.