aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLibravatar Tudor Brindus <me@tbrindus.ca>2020-04-27 00:52:16 -0400
committerLibravatar Simon Ser <contact@emersion.fr>2020-04-27 08:58:24 +0200
commit5cf5349cd79f57433c2539742f087259eee985a1 (patch)
tree4568c1600a25a45d9fa36d1746f757e730b0881d
parentinput/tablet: query tablet focused surface for cursor image check (diff)
downloadsway-5cf5349cd79f57433c2539742f087259eee985a1.tar.gz
sway-5cf5349cd79f57433c2539742f087259eee985a1.tar.zst
sway-5cf5349cd79f57433c2539742f087259eee985a1.zip
Add debug symbol stack trace note to ISSUE_TEMPLATE.md
-rw-r--r--ISSUE_TEMPLATE.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md
index 6014697e..5137decb 100644
--- a/ISSUE_TEMPLATE.md
+++ b/ISSUE_TEMPLATE.md
@@ -1,11 +1,11 @@
1If you are using the nvidia proprietary driver for any reason, you have two choices: 1If you are using the Nvidia proprietary driver for any reason, you have two choices:
2 2
31. Uninstall it and use nouveau instead 31. Uninstall it and use nouveau instead
42. Use X11+i3 and close your browser tab 42. Use X11+i3 and close your browser tab
5 5
6If `lsmod | grep nvidia | wc -l` shows anything other than zero, your bug report is not welcome here. 6If `lsmod | grep nvidia | wc -l` shows anything other than zero, your bug report is not welcome here.
7 7
8Additionally, problems with Firefox are almost certainly Firefox bugs, not sway bugs. Start by submitting your issue to the Firefox bugzilla and come back here only after they confirm otherwise. 8Additionally, problems with Firefox are almost certainly Firefox bugs, not sway bugs. Start by submitting your issue to the Firefox Bugzilla and come back here only after they confirm otherwise.
9 9
10Otherwise, please include the following four components in your bug report: sway version, debug log, configuration (if applicable), and an explanation of steps taken to reproduce the issue. If sway crashes, also include a stack trace. 10Otherwise, please include the following four components in your bug report: sway version, debug log, configuration (if applicable), and an explanation of steps taken to reproduce the issue. If sway crashes, also include a stack trace.
11 11
@@ -42,3 +42,5 @@ If you use systemd, you should be able to open the coredump of the most recent c
42 coredumpctl gdb sway 42 coredumpctl gdb sway
43 43
44And then type `bt full` to obtain the stack trace. 44And then type `bt full` to obtain the stack trace.
45
46If the lines mentioning sway/wlroots have "??" for the location, your binaries were built without debug symbols, and the stack trace is unlikely to be useful. You can find instructions to compile sway from source [here](https://github.com/swaywm/sway/wiki/Development-Setup#compiling-as-a-subproject). Note that debug symbols are included in Meson builds by default.