Game freezes while ATL+TAB under GNOME Shell and Cinnamon (Compositing DE) #520

Closed
linuxrecon opened this Issue Jan 13, 2014 · 3 comments

Comments

Projects
None yet
2 participants

Hello everbody,

when I try to ALT+TAB in Games (with wine or native) they freezing, when I starting them under GNOME Shell or Cinnamon (Tested with the GNOME Shell series 3.8.x and 3.10.x / Cinnamon series 2.x), with primusrun.

The console output is like the following (in this example I started Crusader Kings II on Steam with primusrun):

Focused window is now 0, 0
OnFocusWindowChanged to unknown window type: k_EWindowTypeNonSteamDesktop, 0
primus: warning: dropping a frame to avoid deadlock
Focused window is now 3, 203770
OnFocusWindowChanged to unknown window type: k_EWindowTypeGame, 203770
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
Focused window is now 1, 0
OnFocusWindowChanged to unknown window type: k_EWindowTypeSteamDesktop, 0
Focused window is now 3, 203770
OnFocusWindowChanged to unknown window type: k_EWindowTypeGame, 203770
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
Focused window is now 1, 0
OnFocusWindowChanged to unknown window type: k_EWindowTypeSteamDesktop, 0
primus: warning: dropping a frame to avoid deadlock
Focused window is now 0, 0
OnFocusWindowChanged to unknown window type: k_EWindowTypeNonSteamDesktop, 0
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock
primus: warning: dropping a frame to avoid deadlock

If I start Crusader Kings II with optirun the game screen freezes directly after the loading screen. The console says:

OnFocusWindowChanged to unknown window type: k_EWindowTypeGame, 203770

Tested this on two distributions yet (openSUSE 12.3 / 13.1 and Debian Sid). As I stated above, the game just freezes or to be exact, the screen freezes. I can click around and hear "the click sounds" while I'm doing this. Same with pressing Escape for menu and so on ...
Also this does exactly happen after the second ALT+TAB!

Also tested this with KDE. Starting games with primusrun or optirun under KDE does not show up this effect.

If I can give you some more output than just let me know.

Greetings
ReCon

Graphiccard: nvidia 650m GT

I just want to come back to say that I figured out that this has something to do with the Compositing and Bumblebee. Due to the problem that Cinnamon and GNOME Shell are always running with (more or less) compositing effects I'm unable to completely turn them off. That's seems the reason why KDE has no problems here (I can turn this permanently off here).

Is it possible that anyone can say something about that issue? Is anybody out there who can say that this issue does not exist at his or her machine?

Owner

ArchangeGabriel commented Oct 26, 2014

Sorry for that no one has answered you. Compositing desktops are indeed known to cause several issues with Bumblebee. I’m not sure, but I think that most major desktop today have an option to disable compositing when something is running fullscreen.

Anyway, are you still facing this issue?

@ArchangeGabriel ArchangeGabriel changed the title from Game freezes while ATL+TAB under GNOME Shell and Cinnamon to Game freezes while ATL+TAB under GNOME Shell and Cinnamon (Compositing DE) Oct 26, 2014

Sorry for the late respone.

Well, no, with openSUSE 13.2 (which comes with a newer GNOME Shell Version / GTK Version as well as new driver versions), everything works now at least for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment