As a software engineer, I find it very odd, when someone logs a bug, for someone else to say, "Well, gee, I don't experience that, so you must be wrong." Software bugs are like that -- if they happened all the time for everyone, it's likely the developer would have found it first. Bugs usually result from boundary conditions -- circumstances which occur infrequently because they represent some kind of extreme -- and by definition, most of us drive down the middle of the road.
The next level of inappropriateness is to try to decide democratically whether a bug is actually a bug. So people keep piling on -- "I don't see that, either" -- until someone declares victory, because only one or two people actually see the problem, whereas a whole raft of people don't. People who drive down the middle of the road will always outnumber the pedestrians on the shoulder.
The final mistake is to change the state of a bug to a support request, or shift it to someone else's project, because you don't experience it -- especially when anecdotes of similar buggy behavior keep cropping up. It's like pulling the batteries out of a carbon monoxide detector because it's annoying, and it only goes off occasionally.
These things happen here all the time. As users, we are told incessantly (but appropriately) to search the database before filing a bug or support request. What one often finds when searching is not one thread on the subject, but many. Very often, those threads are curtailed by people who autocratically declare the issue dead, "because I don't experience the problem, and I have been using this for a long time." A short time later, someone else sees the same problem, and running across the closed issue, opens another one.