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 1601 - It's possible to switch to invalid video modes
Summary: It's possible to switch to invalid video modes
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: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-14 06:18 UTC by Sik
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 Sik 2012-09-14 06:18:35 UTC 
When I was testing to see if the latest snapshot (Sep 13 2012, 2.0.0-6419) fixed bug #1571 (it didn't) I accidentally forgot to set the resolution to 640×480 and instead my game tried to switch to 768×480, which doesn't exist in this system. What happened is that somehow SDL switched to fullscreen with a resolution of 800×500 instead of throwing out an error (as I'd expect).

- Ubuntu 11.04 64-bit
- Proprietary nvidia drivers

SDL was built from source with configure/make/make install from said snapshot taken from the site.
Comment 1 Gabriel Jacobo 2012-10-04 07:38:53 UTC 
Can you check if this is fixed now? I believe the patch for bug #1571 should solve this problem as well.
Comment 2 Sik 2012-10-05 01:45:01 UTC 
Just tried, it still switches even though 720×480 doesn't exist (and in fact the image gets stretched horizontally making it overflow the screen). May want to take into account my recent comment on bug #1611 though, since that may be obstructing it (it's the 10th comment there).
Comment 3 Ryan C. Gordon 2015-02-19 05:22:19 UTC 
Marking a large number of bugs with the "triage-2.0.4" keyword at once. Sorry if you got a lot of email from this. This is to help me sort through some bugs in regards to a 2.0.4 release. We may or may not fix this bug for 2.0.4, though!
Comment 4 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.