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 1234

Summary: Fullscreen broken with SDL_RENDERER_SOFTWARE in Gnome 3
Product: SDL Reporter: Jonas Thiem <contact>
Component: videoAssignee: Sam Lantinga <slouken>
Status: RESOLVED FIXED QA Contact: Sam Lantinga <slouken>
Severity: major    
Priority: P2 CC: etc0de
Version: HG 2.0   
Hardware: x86   
OS: Linux   

Description Jonas Thiem 2011-06-20 08:35:36 UTC 
When creating a fullscreen window and using a SDL_CreateRenderer() with SDL_RENDERER_SOFTWARE flag on it, the Linux Gnome 3 desktop environment doesn't properly fullscreen the window despite successful resolution change (window title bar and the desktop's top status bar stay visible, part of the window contents are not accessible). When picking a normal accelerated renderer with SDL_RENDERER_ACCELERATED (opengl), it works perfectly.

This makes using a fallback software renderer for users with problematic video drivers (not rare on linux) not feasible for fullscreen games which is a bit odd.
Comment 1 Jonas Thiem 2011-06-20 13:28:07 UTC 
This seems to be the output that identifies the current hg revision I use (sorry if it is not, I am not familiar with hg):

bash-4.2$ hg summary
parent: 5552:2167a41feefe tip
 Fixed gcc warnings for apps using SDL headers with -Wundef flag.
branch: default
commit: 3 modified, 2 deleted, 1 unknown
update: (current)
bash-4.2$
Comment 2 Jonas Thiem 2011-06-20 14:43:42 UTC 
I got a workaround:

Starting windowed and then after 5 seconds running SDL_SetWindowFullscreen(mainwindow, SDL_TRUE);
gets me a properly working fullscreen mode.

If I use SDL_SetWindowFullscreen(mainwindow, SDL_TRUE); right after SDL_CreateWindow()/SDL_CreateRenderer(), I get just the broken fullscreen though (so the same bugged behaviour as with  direct fullscreen as described in this bug report).
Comment 3 Ellie 2012-01-01 20:42:43 UTC 
The problem is seemingly resolved, probably due to a bugfix in gnome 3 itself.
Comment 4 Sam Lantinga 2012-01-01 21:39:55 UTC 
Great, thanks for the update!