https://bugs.winehq.org/show_bug.cgi?id=37875
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #3 from Anastasius Focht focht@gmx.net --- Hello folks,
although emphasizing on logs is fine there are indeed other important aspects that should be given even higher priority.
Wine version -> proper selection should be much more emphasized, also a hint how to get this information (taking possibility of users with multiple active Wine versions into account).
A short descriptive summary, containing the application/game name(!), version/release and the symptom: "installer doesn't work", "crashes on startup", "<feature> doesn't work", "installer hangs/freezes" ...
A download link is also preferable and indeed the best option for guys like me.
Logs are nice but many times don't tell the real story, requiring in-depth tracing with dedicated debug channels and actual debugging. Yes, there are exceptions when logs are the only way to get information: no access to the software, OP's Linux/Wine/prefix is broken.
From my experience, the time I spend on the first iteration/ping-pong: "which
version, app name", "did you try X?", "please provide information X", <response>, "ok, please try X", "generate log X" could have already been used to work out the actual problem if the minimal set of information would have given when the report was created: app name+version, download and a short description of the problem and how to reproduce.
It's not very hard to provide this information with the benefit of much less triager time wasted and less frustration on both sides.
Regards