Comment 18 for bug 1623440

Revision history for this message
Robie Basak (racb) wrote :

This bug now contains too many conflicting statements for it to be useful to developers to fix any of the problems.

If you think you are affected by this bug, you probably aren't. Instead you're probably affected by the same *symptom* in that you see the same error message. This is not the same thing as being affected by the bug.

If you have to say "in my case ..." then you should be filing a separate bug report, not piling on to this bug, unless you know for certain that the *root cause* is the same.

If you can provide steps to reproduce a specific problem, please a separate bug with details for your case with a more helpful bug title. Then hopefully your report won't be piled on to by a bunch of other users affected by unrelated bugs, and then developers might be able to make progress with the underlying bug related to your specific case.

I'm changing the status of this report to Invalid, as the original report doesn't appear to related to a bug in Ubuntu.

Some subsequent comments from others do suggest that there may be a bug, but we need a separate report for each bug. Please do file these.