Counter-Strike Global Offensive freezes in gnome-shell

[Linus]

After upgrade to ubuntu 19.10, when I launch counter strike global offensive from steam the game is frozen. I can alt-tab and close the game. Tried in fluxbox window manager where the game works, changed fullscreen to windowed fullscreen in the options and tried on gnome again, now the desktop isn't responding after launching the game and I had to ctrl-alt-f3 to reboot my machine.
Using a Radeon RX 580 video card.

[Linus (linusfolke)]

Looks like it's worked on:
https://github.com/ValveSoftware/csgo-osx-linux/issues/2187
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1607

[Daniel van Vugt (vanvugt)]

Tracking in:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1673

[Daniel van Vugt (vanvugt)]

But just to be sure, please also follow these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[Linus (linusfolke)]

Tried it again and it didn't give me a crash report, then i tried it and it launched but the game frooze, was able to open gnome activities and close the game but then the main screen in the game was still on half of the screen frozen.
However if i click to launch the game, then directly open the gnome activities and have it opened until the game has fully launched, i can play the game without a problem.

[Marco Trevisan (Treviño) (3v1n0)]

Could this be somewhat related to https://gitlab.gnome.org/GNOME/gnome-shell/issues/1788 ?

[kisak (kisak)]

Hello, one of the potentially related upstream bug reports was closed (gnome#1607). I've grabbed the fix and built mutter with it at https://launchpad.net/~kisak/+archive/ubuntu/lp-1848852/ , but I don't have an Ubuntu 19.10 test box deployed yet.

Can someone try it out and report back if it has an effect for this bug report?

Note: Launchpad thinks it's older than the distro package so there might need some extra manipulation to try.

[uriel (urychdz)]

I hope someone can fix this, is very annoying.

[Ben Romer (bromer)]

I can confirm both the bug with CS:GO (and several other games that go non-responsive for a short while after starting) and that the fix works.

I installed the packages from the ppa and have tested with CS:GO and a couple of others I was experiencing the problem on (Dying Light and TF2 behave similarly) and the games start correctly now and do not block the UI or crash gnome-shell, though they still display the Force Quit dialog.

I can do any further testing needed but this LGTM.

[Emanuele (emanuc)]

I have the same problem, I start CS: GO, after a while I see a warning window that the game is locked, so click "careful" or "force shut", but it is not clickable and nothing happens. I have to force the game to close.
I attach the logs.

GPU: NVIDIA GTX 750 ti
Driver: nvidia-driver-435 / eoan, now 435.21-0ubuntu2 amd64 [installed]

[Emanuele (emanuc)]

I noticed right now that in the logs I keep spam:

ott 29 13:16:33 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 ==
ott 29 13:16:33 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:33 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392)
ott 29 13:16:33 emanuc gnome-shell[2708]: Object St.Button (0x561e09289ca0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:33 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 ==
ott 29 13:16:33 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:33 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392)
ott 29 13:16:33 emanuc gnome-shell[2708]: Object St.Button (0x561e0c6b33d0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:33 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 ==
ott 29 13:16:33 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:33 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392)
ott 29 13:16:34 emanuc gnome-shell[2708]: Object St.Button (0x561e09289ca0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:34 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 ==
ott 29 13:16:34 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:34 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392)
ott 29 13:16:34 emanuc gnome-shell[2708]: Object St.Button (0x561e0c6b33d0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:34 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 ==
ott 29 13:16:34 emanuc gnome-shell[2708]: #0 7fff70acb170 b resource:///org/gnome/shell/ui/workspace.js:695 (7f659cb72c10 @ 15)
ott 29 13:16:34 emanuc gnome-shell[2708]: #1 7fff70acb220 b self-hosted:975 (7f659ca2dee0 @ 392)
ott 29 13:16:34 emanuc gnome-shell[2708]: Object St.Button (0x561e09289ca0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
ott 29 13:16:34 emanuc gnome-shell[2708]: == Stack trace for context 0x561e054d9590 ==
ott 29 13:16:34 emanuc gnome-shell[2708]: #0 ...

[Daniel van Vugt (vanvugt)]

Please comment in the upstream bug instead for now, since that's where it will be fixed:

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1673

[Michal Turecki (secure-pm)]

I have a similar problem after upgrading Ubuntu to have Gnome 3.34 installed.
The only difference is that Alt+Tab works until certain point when windows freeze and only Ctrl + Alt + F3 -> init 3 -> login -> init 5 cycle restores the desktop.

CS:GO clearly loads with a lag, takes longer to load waiting on a loading image with shutter fade-in.
Main CS:GO screen sometimes loads but mouse cursor after moving is resetted to previous position after around 0.1 sec. Mouse press/keyboard is unresponsive. Suggestion about mutter being stuck in the message loop seems plausible.

I tried ppa above, mutter won't update so I forced it to install yet it did not fix the problem. Steps taken:

sudo add-apt-repository ppa:kisak/lp-1848852
sudo apt install mutter=3.34.1-1ubuntu1~lp1848852

Do you have any suggestions what to do next?