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 2093 - Fullscreen resolution do not resize back after I quit the application
Summary: Fullscreen resolution do not resize back after I quit the application
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.0
Hardware: x86_64 Linux
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-07 13:49 UTC by Oleg
Modified: 2018-08-06 21:20 UTC (History)
1 user (show)

See Also:

Attachments
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 Oleg 2013-09-07 13:49:59 UTC 
I'm running SDL2 application on Kubuntu 13.04 with proprietary nvidia drivers. Whenever I call SDL_CreateWindow with SDL_WINDOW_FULLSCREEN flag and close application, my screen resolution still has the size I passed to SDL_CreateWindow, so I have to open KDE settings and change resolution back. However fullscreen works properly if I use SDL_WINDOW_FULLSCREEN_DESKTOP flag.
Comment 1 Gabriel Jacobo 2013-09-29 14:26:51 UTC 
I've tried this on Kubuntu 13.04, nVidia binaries (nvidia-313-updates), using testrendercopyex, and failed to reproduce.

testrendercopyex --info all --fullscreen --display 0
testrendercopyex --info all --fullscreen --display 1

Both change the resolution of the desired monitor, and restore everything (minus some window rearrangements if they were placed on the resized monitor) if I switch focus or close the application. xrandr -q confirms the mode change as well.
Comment 2 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.