We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 1941 - SDL_WINDOW_FULLSCREEN resizes all monitors on Linux
Summary: SDL_WINDOW_FULLSCREEN resizes all monitors on Linux
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: HG 2.0
Hardware: x86_64 Linux
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-04 00:59 UTC by Gerry JJ
Modified: 2018-08-06 21:20 UTC (History)
2 users (show)

See Also:

Attachments
fullscreen on multiple monitors (11.09 KB, text/plain)
2013-07-26 16:54 UTC, Sebastian Wick 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gerry JJ 2013-07-04 00:59:38 UTC 
If a window goes fullscreen with SDL_WINDOW_FULLSCREEN and SDL has to resize the display, it doesn't just resize the display of the monitor the window will go fullscreen on, but all monitors (probably. I've only got 2). I'd expect it to only resize the display that will contain the fullscreen window.

Can be reproduced with one of the standard SDL test programs, e.g. "./testrendercopyex --fullscreen --geometry 640x480"

(Ubuntu 13.04 64-bit, Unity desktop, nvidia drivers)
Comment 1 Gabriel Jacobo 2013-07-06 14:57:13 UTC 
This may be Unity related, I've tried this on Kubuntu 13.04, nVidia drivers with Twinview and it seems to work fine, using the position argument I can place the full screen window on either monitor and the other stays intact.
Comment 2 Gabriel Jacobo 2013-07-08 17:35:39 UTC 
Can you run (testrendercopyex is in the "test" directory, make sure you have the latest SDL from HG)...

xrandr -q

testrendercopyex --fullscreen --geometry 640x480 --display 0
xrandr -q  

testrendercopyex --fullscreen --geometry 640x480 --display 1
xrandr -q


(Make sure to run xrandr -q while the testrendercopyex app is running). It may also help if you #define X11MODES_DEBUG to get some more information about what's going on.
Comment 3 Sebastian Wick 2013-07-26 16:54:33 UTC 
Created attachment 1260 [details]
fullscreen on multiple monitors
Comment 4 Sebastian Wick 2013-07-26 16:56:55 UTC 
I'm also affected by this and uploaded the output of the requested commands.
Comment 5 Gabriel Jacobo 2013-07-26 17:12:09 UTC 
Sebastian, the log you attached seems to indicate that everything is working correctly at least on the XRandr level (one monitor goes to 640x480 while the other stays at the desktop res)...what do you see on screen? Are you using Unity?
Comment 6 Sebastian Wick 2013-07-27 08:52:53 UTC 
It's weirder than I thought. Starting the test program on screen 0 changes the resolution of screen 1 and not the resolution of screen 0. When the window hides and shows again, everything is like you would expect it to be.
Starting on screen 1, it sometimes changes to resolution of screen 0 and not the resolution of screen 1. The window randomly shows either at screen 0 or screen 1.
I'm using awesome wm.
Comment 7 Ryan C. Gordon 2018-08-06 21:20:20 UTC 
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.