Re: How to file a proper bug report
- Date: Thu, 14 Feb 2019 23:36:49 -0500
- From: David Niklas <doark@xxxxxxxx>
- Subject: Re: How to file a proper bug report
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, 15 Feb 2019 11:20:54 +1100
Ben Finney <bignose@xxxxxxxxxx> wrote:
> t.j.duchene@xxxxxxxxx writes:
> > I have a user question on how to file a proper Debian bug report under
> > certain circumstances.
> Thank you for taking the care to find out what information is needed for
> a good bug report.
> Your specific use cases seem to involve non-free software (Steam games
> are, I assume, non-free in general, though there may be some exceptions)
> so that makes it particularly difficult to diagnose problems.
> If there are reproducible behaviours, it can be helpful to run the
> program under ‘strace’ and reproduce the behaviour, to get an extremely
> verbose log of system calls being made at the time when the behaviour
> When that is reproducible, it might be helpful to have two separate
> ‘strace’ log outputs: one from the environment where you don't get the
> buggy behaviour, one where you do.
I watch the mesa-dev ML. What you want to do is to log and post from both
systems the following:
1. Xorg log (Typically called Xorg.0.log) from /var/log.
2. Run the program dmesg from the cmdline and log it to a file.
HINT: Redirect to a file with > FILE. As in: PROG > FILE.txt
3. Install apitrace (cmdline command: apt install apitrace )
4. Run the program wile apitrace'ing it. (Normally you run the command in
the terminal wine example.exe) COMPRESS the output it will be HUGE!!!
HINT: apitrace wine example.exe | xz -9ecvCsha256 > FILE.txt.
5. Uname -a (This, in particular, will give you the kernel version.)
6. Programs and versions (wine, mesa, llvm, xorg, example.exe, libdrm).
Typically you run from the cmdline: PROG --version; apt show PROG.
The proprietary game will not accept this method of course.
7. Fill out a bug with this info at: https://bugs.freedesktop.org/. Use
attachments liberally with the add attachment feature. You can comment
and attach several times for 1 bug so not everything has to be in the
Describe your problem throughly.
Don't post screen shots unless you have to.
See these for examples:
Be aware that they might ask you to try a custom kernel/mesa/etc.. If you
cannot do this they might need a copy of the game in question. They are
friendly and will walk you through the above if you ask them to.
No, I have not run the above to check for errors but it looks correct and
I did check the man pages.
Thanks for your report,
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----