Ubuntu

dosbox changes setting to "mirror" while using two displays

Reported by shankao on 2009-12-19
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dosbox (Debian)
New
Unknown
dosbox (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: dosbox

Using dosbox and going fullscreen, sets display setting to "mirror" when I'm using an external monitor.

It should go fullscreen only in the corresponding display, and respect the current desktop settings.

ProblemType: Bug
Architecture: i386
Date: Sat Dec 19 15:06:13 2009
DistroRelease: Ubuntu 10.04
Package: dosbox 0.73-0ubuntu1
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-8.12-generic
SourcePackage: dosbox
Tags: lucid
Uname: Linux 2.6.32-8-generic i686

shankao (shankao) wrote :
shankao (shankao) on 2010-01-07
tags: added: dual-head usability
dino99 (9d9) wrote :
Changed in dosbox (Ubuntu):
status: New → Invalid
shankao (shankao) wrote :

Reopening again: It happens in the current development version (raring).

Then, as far as I know, given an old untouched bug (1) or a bug reported against an Ubuntu version that has reached EOL (2), it should be asked to be tested in any of the active releases and marked to Incomplete, instead of being closed. :)

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

Changed in dosbox (Ubuntu):
status: Invalid → New
dino99 (9d9) wrote :

a few notes:
- that report is more than 3 years old, and had never been "assigned" nor beeing asked for Apport details
- launchpad does not track "dosbox" bugs (yours is the only one inside the database), but is tracked on http://sourceforge.net/p/dosbox/bugs/

Thats said, setting that report "new" again, will not get more chance to get a fix, as there is no interest to work on it here.

Changed in dosbox (Ubuntu):
status: New → Invalid
shankao (shankao) wrote :

- 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

shankao (shankao) wrote :

Marked back as new for the reasons stated before. Also, attached the corresponding debian report

Changed in dosbox (Ubuntu):
status: Invalid → New
Changed in dosbox (Debian):
status: Unknown → New
shankao (shankao) wrote :

Upstream bug report: https://sourceforge.net/p/dosbox/bugs/389/

Sadly, launchpad does not support sourceforce as a bug report platform to automatically track the status upstream

dino99 (9d9) wrote :

Thanks for having pushed that issue in the right places; now some hope can be expected to get it fixed.

note: if you have reported some other bugs here, please check that they are still valid. (the dead cows list is way too long)

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dosbox (Ubuntu):
status: New → Confirmed
Joseph Gamble (jcg) on 2013-08-20
Changed in dosbox (Ubuntu):
status: Confirmed → Fix Released
description: updated
Joseph Gamble (jcg) wrote :

No Fix, can't remove tag

shankao (shankao) wrote :

I will check again when I'm back from my holidays, but looking to the debian and upstream bugs, it doesn't look as fixed. Maybe it would be worth to ask to some dosbox developer about their intentions about this instead.

Changed in dosbox (Ubuntu):
status: Fix Released → Confirmed
shankao (shankao) wrote :

After some investigation, this looks to be a problem in the SDL version that dosbox uses internally (1.2).
There is an ongoing effort to get dosbox working with SDL 2.0 [1], which has better multi monitor support as one of its main features and should improve the situation here.

[1] - http://www.vogons.org/viewtopic.php?t=34770

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.