On Fri, 2019-02-15 at 11:20 +1100, Ben Finney wrote: > t.j.duch...@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. > Thank you for the suggestion, Ben. I really do appreciate it, and will try that as soon as I have some free time. I have seen videos of a similar effect in other Steam games ported to Linux, so I am actually concerned that this may be a regression in Mesa (which is free software) as Debian Stable's older version does not have the issue.
I spend most of my time working on Windows, so debugging Linux will be something new. Thanks for helping me on that! If you don't mind, I'll post back on what I find so I can do this the right way. Thanks again. T.J.
