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 1585 - Black screen on iPAD (4.3.3) and Simulator (5.x)
Summary: Black screen on iPAD (4.3.3) and Simulator (5.x)
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.0
Hardware: iPhone/iPod touch iOS 5
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-27 02:55 UTC by Martin Gerhardy
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 Martin Gerhardy 2012-08-27 02:55:00 UTC 
Even after the fix Sam applied to the repository I still get a black screen when trying to render a rect. The only thing that works is the clear color. If i afterwards render a red rect, the rect is not visible. The used renderer is opengles2.
Comment 1 Martin Gerhardy 2012-11-06 11:44:17 UTC 
this can be closed - this works with the latest sdl version.
Comment 2 Sam Lantinga 2012-11-06 20:19:17 UTC 
Great, thanks!
Comment 3 fcjackson 2018-02-05 00:41:18 UTC 
This is the second time I’ve contacted you about this problem. The screen goes black and the game disappears when I’m playing Mahjong.
Comment 4 Sam Lantinga 2018-02-05 18:27:23 UTC 
Please contact the author of Mahjong. They may need to update to the latest SDL version to pick up any fixes.

If you're a developer, can you reproduce it with the testsprite2 test program in the SDL source archive here?
http://www.libsdl.org/tmp/SDL-2.0.zip
Comment 5 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.