![](https://seccdn.libravatar.org/avatar/d9f1bf0a7e7bcbfbcc9814ae89f062da.jpg?s=120&d=mm&r=g)
On Monday 05 January 2015 14.35:31 Doug wrote:
On 01/05/2015 02:17 PM, Per Jessen wrote:
Per Jessen wrote:
Bughandlers/developers that close reports just because they can't reproduce the issue. WORKSFORYOU != WORKSFORME.
Does anyone have a suggestion? It seems completely and utterly pointless to report a bug when it will only be looked at if it can be reproduced by the developer. If I had _ever_ taken this attitude in my 25+ years as a software engineer, my career would have been very quickly cut short. The mind boggles.
I don't blame you for your frustration. I'm not a programmer, but I have worked with programmers--I'm a hardware engineer. I think the problem is, that when you and your engineering team are all in one place, you can go look at the problem first had. When the developer sees a bug report that he can't duplicate, how is he going to a) fix it, and b) demonstrate that it is fixed? I wish I could suggest a solution, but short of shipping the whole computer with the offending software, I don't see one.
We have Internet. We shouldn't need to ship stuff around much. And why limit the tools to email and bugzilla only. I'm tempted to suggest that, in cases where the developer is unable (or unwilling, or too busy) to reproduce the bug himself, he may instead decide to offer to set up a quick video call with the bug reporter, using smartphones or something. Then bug reporter can demonstrate the bug, developer can ask questions, etc, etc., and progress may be expedited. As long as the developer takes the initiative to such a call, and is in charge throughout, it should be possible to stay out of unpaid support territory. Such interaction, even if rare, might pay back by improving community enthusiasm for testing the distro and filing bug reports. Just a thought... \Olav -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org