I've just bumped into something that I feel shouldn't have happened. Execute 32bit ELF on a 64bit ubuntu machine, getting segmentation fault
The question was IMO clear enough. The one request for source code to a "hello world" program was rather pointless given the problem faced. Yet two people voted the question closed as "unclear".
I then found a question / answer I thought might be effectively the same question asked a different way and voted duplicate... the question closed immediately as "unclear".
The only problem is I did not vote the question unclear and absolutely disagree with that. I'm a bit uncomfortable with my one vote being used to close this as duplicate either, I like the safety net of multiple votes being required. Voting duplicate is tricky and very error prone and it is surely good to let second opinions be cast on this.
I can see why other close votes are cumulative. These all easily overlap:
- Needs more focus
- Needs more clarity
- Opinion based
I really can't reconcile the idea that a question is both unclear and clearly a duplicate. Indeed it's hard for duplicates to be opinion based either since the other question would also have been opinion based and should have been closed.
Why do duplicate votes count as regular "close" votes? Could this group of votes (only) be maintained as a separate count, with separate trigger to close actually, rather than a cumulative trigger between them.
Note this is a different feature request to this one. I'm not talking about the close reason being displayed correctly. I'm talking about the actual trigger being split into two counts. Though both the other feature request and this one are derived from the same "bug".