Perhaps the problem is that in large projects, many areas don't have someone who feels ultimately responsible for making sure each bug gets a response. It's ver

Perhaps the problem is that in large projects, many areas don't have someone who feels ultimately responsible for making sure each bug gets a response. It's very easy to glance over a list of new bugs and leave the ones you don't know anything about for someone else to tackle, but inevitably there are bugs that no-one really feels comfortable tackling. Hardware specific stuff is especially bad, because device interfaces do some crazy things, and only someone with the same model can investigate it. Kudos for being willing to dive into the code, though, and I'm sorry to hear no-one offered advice with that.