This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

• Example C program (main.c, text/x-csrc, 2012-01-13 09:22:57 +0000, 2170 bytes)
• System Info Report (hardinfo_report.html, text/html, 2012-01-13 09:23:49 +0000, 17156 bytes)

Reported in version: HG 2.0
Reported for operating system, platform: Linux, x86_64

Comments on the original bug report:

On 2012-01-13 09:22:57 +0000, wrote:

Created attachment 767
Example C program

I'm trying to create a simple opengl window, but if I set SDL_WINDOW_OPENGL in SDL_CreateWindow() no window is created, and unfortunately SDL_GetError() does not return anything...
I'm on Arch Linux, Mesa 7.11.2, Intel Ironlake Mobile, SDL-hg rev6209

On 2012-01-13 09:23:49 +0000, wrote:

Created attachment 768
System Info Report

On 2012-01-13 18:03:12 +0000, Sam Lantinga wrote:

Have you tried debugging it?
That's a very thorough system info report, thanks!

On 2012-01-14 09:11:09 +0000, wrote:

(In reply to comment # 2)

Have you tried debugging it?
That's a very thorough system info report, thanks!

Yes, I tryed to debug it in Eclipse, but it wasn't very helpful... However, it seems that SDL_CreateWindow() returns NULL while SDL_GetError() returns 0x7ffff7bcc2e0 ""

On 2012-02-19 12:14:09 +0000, wrote:

The problem is that SDL is configured with both SDL_VIDEO_OPENGL_GLX and SDL_VIDEO_OPENGL_ES (it's installed because of KDE >= 4.8).

That's why SDL initialises OpenGL ES instead of OpenGL & GLX, so window initialisation fails in video/x11/SDL_x11window.c:283 as X11_GL_GetVisual() returns NULL.

On 2018-08-06 21:20:21 +0000, Ryan C. Gordon wrote:

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.