Comment 6 for bug 378333

No, my behaviour is not confrontational. In fact, to be honest, I found your behaviour (just closing the bug without any useful information at all) quite aggressive.

* If the bug is not a bug, then by all means close it (and state why, so that everyone else who is affected by this problem and finds this bug by Google/... will understand).

* If the bug is a duplicate, mark it as such, and state which specific bug it's a duplicate of. You need to state why so that (a) I can go subscribe to the "parent" bug. (b) Everyone else who finds this bug by Google/... will find useful information, not just yet another dead-end. Calling a dup "invalid" is also pretty insulting.

* Otherwise, the bug must stay open; it's a valid bug that needs to be fixed. I can't see why this isn't self-evident.

This is simply normal bug processing practice!