From e3f084a36aa5759e68888e447e904d5aa3f10c51 Mon Sep 17 00:00:00 2001 From: Michael Catanzaro Date: Wed, 30 May 2018 15:52:57 -0500 Subject: Add GitLab issue template --- .gitlab/issue_templates/bug.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .gitlab/issue_templates/bug.md (limited to '.gitlab') diff --git a/.gitlab/issue_templates/bug.md b/.gitlab/issue_templates/bug.md new file mode 100644 index 000000000..ed31f9b2e --- /dev/null +++ b/.gitlab/issue_templates/bug.md @@ -0,0 +1,23 @@ +Hey, thanks for reporting your problem with Epiphany. + +# Software versions + +Please include the following in your report: + +Epiphany version: +WebKitGTK+ version: +Operating system and version: + +Check the About dialog if you're not sure what software versions you have. + +# Web content bugs + +This is the wrong place to report bugs with web content (e.g. incorrect rendering, broken JavaScript, problems with video playback). These problems should be reported directly on https://bugs.webkit.org. To ensure we see your bug, be sure to select the 'WebKit Gtk' component when reporting, and prefix the bug title with [GTK]. + +In general, only problems with the GTK+ user interface around the web view (e.g. menus, preferences dialog, window chrome) or Epiphany features (e.g. Firefox Sync, adblocker, web apps) should be reported here. + +# Crashes + +If Epiphany crashed, then we really need a backtrace taken in gdb with 'bt full' in order to solve the problem. Be sure to install the necessary debuginfo packages for all frames that appear in the crashing thread. [Learn how to include a good backtrace.](https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces) + +If you see the message "Oops! Something went wrong while displaying this page," that means WebKit has crashed. Please follow the steps above to take a quality backtrace and to report it on WebKit Bugzilla. -- cgit v1.2.1