mirror of
https://github.com/swaywm/sway.git
synced 2024-11-06 00:13:13 +00:00
bac9559665
This utilizes the newer Github issue templates. They allow for the user to specify what type of issue they are submitting to allow for a more specific issue template to be shown. In addition to a hopefully easier to read/parse/follow bug report template, this also include templates for enhancements and i3 compatibility. This also includes a link to the IRC under the section title Questions. For the three templates, the labels bug, enhancement, and i3-compat will be automatically applied for the appropriate report to assist in triaging. Hopefully, this will result in less questions and issues for new window management functionality on Github and allow for better quality issues being submitted. At the very least, it allows us to outline our stances for bugs, enhancements, and i3-compatibility in an easier to read format.
1.6 KiB
1.6 KiB
name | about | labels |
---|---|---|
Bugs | Crashes and other bugs | bug |
Please read the following before submitting:
- Please do NOT submit bug reports for questions. Ask questions on IRC at #sway on irc.freenode.net.
- Proprietary graphics drivers, including nvidia, are not supported. Please use the open source equivalents, such as nouveau, if you would like to use Sway.
- Problems with the Wayland version of Firefox are likely to be Firefox bugs. Start by submitting your issue to the Firefox Bugzilla and come back here only after they confirm otherwise.
Please fill out the following:
-
Sway Version:
swaymsg -t get_version
orsway -v
-
Debug Log:
- Run
sway -d 2> ~/sway.log
from a TTY and upload it to a pastebin, such as gist.github.com. - This will record information about sway's activity. Please try to keep the reproduction as brief as possible and exit sway.
- Run
-
Configuration File:
- Please try to produce with the default configuration.
- If you cannot reproduce with the default configuration, please try to find the minimal configuration to reproduce.
- Upload the config to a pastebin such as gist.github.com.
-
Stack Trace:
- This is only needed if sway crashes.
- If you use systemd, you should be able to open the coredump of the most recent crash with gdb with
coredumpctl gdb sway
and thenbt full
to obtain the stack trace. - If the lines mentioning sway or wlroots have
??
for the location, your binaries were built without debug symbols. Please compile both sway and wlroots from source and try to reproduce.
-
Description:
- The steps you took in plain English to reproduce the problem.