Choose any large long-lived open source project at random and search their issue tracker and I guarantee you can find at least 3 open bugs that are 5 years old or more. I know, because I've run into these bugs, as have dozens of others, and went to report them only to find they had already been reported years ago with no action taken by the developers.
Filing bugs takes time. You're going to want reproducible steps, you're going to want logs, you're going to want me to try different things. That's fine, and I'm willing to do that to get my bug fixed, but only if I think you actually give enough of a shit to fix it. I don't enjoy wasting my time any more than you do. When I see 5 year old open issues your tracker, where several users have chimed in, submitted logs, etc. and you've done nothing, I assume you don't care so neither do I.
Worse yet, many developers are downright hostile to users reporting bugs or, god forbid, making feature suggestions. Spend five minutes in GNOME's issue tracker to see what I mean.
* Create New Account
* Edit Bug
* Tracking Flags: $version => affected
* Save Changes
Do it for every version. It is extremely hard to know is issue resolved or not. I've tried to reproduce session restore on Developers Edition - nope, I can't. There is no minimal xmonad config attached. Is it solved by ewmh (helps at least with fullscreen)? If bug "is simple to fix" try to fix yourself.
I maintain such a project, and most bug reports I can fix in a few minutes. Others take a few days. Still others need to be deferred until some large refactoring is completed in coming months. Others still are involved to the extent that I'm not sure I'll ever fix them. But I value them all, and there are many more in the former categories than the latter.
Other... I can turn your rhetoric around: "Fixing bugs takes time. There is source code, yet in 5 years no one fixed. Looks like niche issue. You do not care about it so neither do developers."
Hey, it is not bad, at least you've confirmed you are not the only one. One can't even browse Opera issue tracker.
I have never had a Visual Studio or Windows bug report fixed and only a few JetBrains ones fixed. However, if it's a small tool or library then it's a different story, much higher response rate.
It does matter, you can't fix a problem with IntelliJ, you need to wait until the company considers it economically viable to fix, ie enough people report it or its critical.
But if something in an Open-source system pisses you off, you can fix it yourself.
It not for everyone, but at least it's possible to fix FOSS systems yourself...
> But if something in an Open-source system pisses you off, you can fix it yourself.
I'm literally doing that right now :)