25 ms·

I've had a bunch of my valid bug reports closed by Ubuntu. I've switched to Debian, and every one of them is being closed unless I go and reproduce the issue ag

by avar 15y ago

I've had a bunch of my valid bug reports closed by Ubuntu. I've switched to Debian, and every one of them is being closed unless I go and reproduce the issue again in later versions of Ubuntu. Some of them are general issues that won't have been fixed in later versions.

ecaron 15y ago
I'm pretty sure every OS follows this practice, here's my personal example from Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=219715 https://bugzilla.redhat.com/show_bug.cgi?id=219715
- silvestrov 15y ago
  Not my experience with Apple: I've had years-old bug reports where Apple suddenly emailed me and asked me to confirm that the bug was fixed in the latest developer preview (for an major OS version later).
  - hboon 15y ago
    Same experience here, I have 2 year old bugs fixed 2 major version later. Unfortunately the official bug report system is opaque though.
  - smackfu 15y ago
    Unfortunately the other common case for Apple is that your bug just gets marked as a duplicate, and since you only have visibility to the bugs you opened, you lose all tracking.
    - DrJokepu 15y ago
      Filing a bug for Apple is worth the effort even if they mark it as duplicate. Duplicate reports count as "votes", the more people file the same bug the higher priority it enjoys. Apple employees mention this regularly on the Apple Developer Forums and encourage everyone to file bugs.
- streptomycin 15y ago
  To be fair, testing a hardware-specific bug is a bit more complex.
- lamby 15y ago
  In case it wasn't clear from the parent, Debian doesn't do this (at least not automatically).
Luyt 15y ago
jwz wrote on this: http://www.jwz.org/doc/cadt.html http://www.jwz.org/doc/cadt.html "This is, I think, the most common way for my bug reports to open source software projects to ever become closed. I report bugs; they go unread for a year, sometimes two; and then (surprise!) that module is rewritten from scratch -- and the new maintainer can't be bothered to check whether his new version has actually solved any of the known problems that existed in the previous version. "
- j_baker 15y ago
  What's most annoying is the combination of this issue and the one the author writes about: the ticket sits around for a year and then gets closed a year later for some silly reason (like lack of a test program).
- po 15y ago
  I'm willing to accept that a rewrite might have fixed my issue and am willing to accept a close resolution until I retest and reopen. In this case it's, "nope, I don't believe you and you're up shit-creek until you can really prove it to me."
- jff 15y ago
  And your bug reports just sit there, with people popping in every few months saying they have the same problem and asking for help... but nothing ever comes of it.

by avar 15y ago

ecaron 15y ago

I'm pretty sure every OS follows this practice, here's my personal example from Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=219715 https://bugzilla.redhat.com/show_bug.cgi?id=219715

silvestrov 15y ago
Not my experience with Apple: I've had years-old bug reports where Apple suddenly emailed me and asked me to confirm that the bug was fixed in the latest developer preview (for an major OS version later).
- hboon 15y ago
  Same experience here, I have 2 year old bugs fixed 2 major version later. Unfortunately the official bug report system is opaque though.
- smackfu 15y ago
  Unfortunately the other common case for Apple is that your bug just gets marked as a duplicate, and since you only have visibility to the bugs you opened, you lose all tracking.
  - DrJokepu 15y ago
    Filing a bug for Apple is worth the effort even if they mark it as duplicate. Duplicate reports count as "votes", the more people file the same bug the higher priority it enjoys. Apple employees mention this regularly on the Apple Developer Forums and encourage everyone to file bugs.
streptomycin 15y ago
To be fair, testing a hardware-specific bug is a bit more complex.
lamby 15y ago
In case it wasn't clear from the parent, Debian doesn't do this (at least not automatically).

Luyt 15y ago

jwz wrote on this: http://www.jwz.org/doc/cadt.html http://www.jwz.org/doc/cadt.html "This is, I think, the most common way for my bug reports to open source software projects to ever become closed. I report bugs; they go unread for a year, sometimes two; and then (surprise!) that module is rewritten from scratch -- and the new maintainer can't be bothered to check whether his new version has actually solved any of the known problems that existed in the previous version. "

j_baker 15y ago
What's most annoying is the combination of this issue and the one the author writes about: the ticket sits around for a year and then gets closed a year later for some silly reason (like lack of a test program).
po 15y ago
I'm willing to accept that a rewrite might have fixed my issue and am willing to accept a close resolution until I retest and reopen. In this case it's, "nope, I don't believe you and you're up shit-creek until you can really prove it to me."
jff 15y ago
And your bug reports just sit there, with people popping in every few months saying they have the same problem and asking for help... but nothing ever comes of it.