/usr/share/doc/xorg/howto/report-bugs.txt is in xserver-xorg 1:7.7+7.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 | How to report bugs
==================
Cyril Brulebois <kibi@debian.org>
Report it upstream
------------------
In most cases, it is preferrable to report the bug upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg
See https://01.org/linuxgraphics/documentation/how-report-bugs-0 for a good
introduction on how to write useful bug reports. While the document is targeted
at Intel graphics hardware, it is a good guideline for other vendor’s hardware
as well.
Simple as reportbug
-------------------
Initial report
~~~~~~~~~~~~~~
Unless you know which package to report the bug against, you can
report the bug against the `xorg` metapackage:
----
reportbug xorg
----
Like most packages related to the X server, reporting a bug against
this package triggers a bug script which is going to collect X-related
information, be it installed packages, running kernel, X
configuration, X log, and so on.
****
.Note
In case this metapackage wasn’t used to install your X stack,
report a bug against `xserver-xorg` instead. And if that one isn’t
installed either, go for `xserver-xorg-core`.
****
If a backtrace shows up in the X log, it’s much appreciated to try and
get a link:use-gdb.html[full backtrace using gdb].
Follow-up with more info
~~~~~~~~~~~~~~~~~~~~~~~~
If you reported a bug against another package and if that bug was
reassigned to an X-related package, we might need more
information. You can run the bug script manually and attach its output
to your mail to the bug report:
----
/usr/share/bug/xserver-xorg-core/script 3>/tmp/script.log
----
****
.Note
Make sure there’s no space between `3` and `>`, that’s a shell
redirection.
****
|