[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to file a proper bug report



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Fri, 15 Feb 2019 11:20:54 +1100
Ben Finney <bignose@debian.org> wrote:
> t.j.duchene@gmail.com 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
> occurs.
> 
> 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
   first post.
   Describe your problem throughly.
   Don't post screen shots unless you have to.
   See these for examples:

https://bugs.freedesktop.org/show_bug.cgi?id=91251
https://bugs.freedesktop.org/show_bug.cgi?id=73739

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,
David
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEL2N7+xWmVOJDQxWGm3XCrhg2YP8FAlxmQeEACgkQm3XCrhg2
YP/Hlg//fjfjBZtQzs+JN5k14mGg1/TagkS6Q+ZB7fEgJC088/Vm0hcSnMlEZUsS
hffDU/UUG2sVbrqfHBLpmnGNZ5zTwQBUzJBujYUvoH4XFj0TWLA3zQW7MFPjO/kO
oZFNiBv0nHpJByT5ehVdRJT86fP4HYtPAm9WDBP7f05bAZdu48aMW3vD2QiZeg0Q
jA6Atv9He3AN7BXDJ+AGh8EpaKXDMOoAuk9bj+OXf81cthArXZaQ3rdqksVfqx0P
7Eoofg2dAS1sTNiq42h1PDpLG9GIpp+asYT2XIkwT9wJLnh8dvE6nKy8vVx4UNo5
GcqfMFPGxU3NGVoUqcXMCGPbvTZL/q6HQz1+A0gAfrh+/ikZPFviBTqjwdKnn8uu
5DZ7K9P8qtD2iB1U8rcjX6JFLmkSVnV9AhViT9xlHYoXxyv2HWDpBtiCJm8NVtQ2
W9quZJqlV/3vA7ncEH46LQCpS3Q+ZKqe83nwZxJ8ez7fFaH0Li9gWsveGmS99INn
EILNtq2X5leoS5vGuPZMCgo33VoLdeKwHR5iiTOoktjGP4pXuCvGi6mthLYWwrRP
Q68cCiZ7CouPWBlXdY6Emr9+zTGayrysUgXhubFiWjB8Zf8l8EqKk6RrmrIimsOP
gnEPCNHPI11NDdOQ2Z4UlF53YUtkgXildR/0DKv1HxsYAyXnKmA=
=aVk3
-----END PGP SIGNATURE-----

Reply to: