> In theory, there should be no problem with having your bug marked as a duplicate of some other bug;
IMHO both in theory as in practice there is a problem. In theory each bug should have its own report. In practice often there is already a lot of tracking info in one bug, which gets lost ni the cross fire after merging. Second, it leads to conflicting reports, which makes it confusing for whoever is trying to verify, or fix it.
> Personally, I think bug trackers should have support for a "me too"
> feature, where you find a bug in the database that you think is happening
> to you, and file an intentional duplicate (already marked as such) with
> your particular conditions.
Actually launchpad has something like you describe, as users can subscribe to a bug. So you as a developer could choose to look first at the one bug with 25 subscribers, and not at the one with just 2.