Debian
dosbox package

  1. Bug #498513
  2. Comment #5

Comment 5 for bug 498513

Revision history for this message
shankao (shankao) wrote : Re: dosbox changes setting to "mirror" while using two displays

- Being it old is not a reason to close it as long as the bug still happens in any supported version (as per Ubuntu support notes). Actually, it still happens in *any* of the currently supported Ubuntu versions. I like to close bugs too, but even the release having reached EOL does not recommend that (see (2)).

- It has not being asked for any details and that's the actual procedure to do: ask for details and mark as "incomplete" instead of directly closing it. This gives the reported time enough to update/improve/recheck the bug report and we don't loose them when they're still solvable.

- Launchpad does not track *upstream* dosbox bugs as you said, and few fixing intents will be find here. But usually they are kept in launchpad as they serve as reference (i.e. the bug could have being fixed upstream but for some reason is still not fixed in Ubuntu). The stated procedure in this case (see (1)), is report upstream (ideally passing through debian, where this package is sync'ed from) and then, add every upstream bug number in Ubuntu's launchpad bug.

- Setting the bug report back to "new" again, raises the fact that is a recognized pending bug, it's being already reported (so anybody else that experiences it will not do it again) and finally, easier to be found with the regular launchpad searches instead of being buried in the "advanced search" options.

Given the previous arguments, I consider the next actions would need to be done in order to help with the fix of this problem:

1) Keep the bug back as "new", for the reasons given before
2) Actually, you could also test it in your computer if you have a second monitor and, if it happens, set it as "confirmed" instead. :)
3) Report the bug upstream, as it looks like it, then add upstream's bug number here as of (1). This is my fault as I'm the original reported. I will remedy this now :)

If you still think that the bug has to be closed, we can try to raise the question to the crowd in the bugsquad mail list in order to get into an agreement :)

(1) - https://wiki.ubuntu.com/Bugs/Responses#A_bug_that_should_be_handled_upstream
(2) - https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_EOL