Freeze when going full screen while watching video

Bug #2037121 reported by Johon Doee
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mutter
New
Undecided
Unassigned
mutter (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hi.

The screen freezes when I switch a running video into fullscreen mode. It happens with Gnome Totem, VLC, Firefox, so the issue is not connected to a certain app.

I can hear the audio playing in the background while the video output gets stuck. The keyboard keeps working but switching to another app via keyboard doesn't work because the screen keeps stuck with the video.

Way to reproduce:

1) Boot Ubuntu
2) Close lid and let the laptop go to sleep mode
3) Open the lid and login
4) Start a random video on Youtube/VLC/Totem
5) Switch to fullscreen
-> Immediate freeze of the screen

Workaround after the video froze:
1) Press ESC key (As if you would usually leave the fullscreen mode, however, the screen will stay stuck)
2) Close the lid
3) Wait until the laptop goes into sleep mode
4) Open the lid and login again

Step 1) is necessary to leave the fullscreen before going to sleep. Otherwise after sleep and logging in again the screen gets stuck again immediately because the video is continued in fullscreen.

Syslog tell me this:

gnome-shell[1744]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

Ubuntu 23.10 beta with all updates of 22.09.2023
Ryzen 7 PRO 6850U
Kernel 6.5.0-5-generic

Johon Doee (jodoee11)
description: updated
Revision history for this message
MasterCATZ (mastercatz) wrote (last edit ):

Mine has been doing this as well since kernel 6

 Ubuntu 22.04.3 LTS

 Device: AMD Radeon RX 6800 XT (navi21, LLVM 15.0.7, DRM 3.52, 6.3.7-060307-generic) (0x73bf)
 OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.2.5-0ubuntu0.1~22.04.3

Multi Display
seems to happen when ever something full-screen is used and then go click on an unfocused window and screen stops getting drawn clock and everything

then ctrl+alt+f1 / ctrl+alt+f7 back to desktop and it works again

however for me all syslog shows is

Sep 23 19:48:26 aio compiz[36136]: /usr/bin/compiz (core) - Warn: unhandled ConfigureNotify on 0x1d64bc9!
Sep 23 19:48:26 aio compiz[36136]: /usr/bin/compiz (core) - Warn: this should never happen. you should probably file a bug about this.
Sep 23 19:48:26 aio compiz[36136]: /usr/bin/compiz (core) - Warn: unhandled ConfigureNotify on 0x1c000f7!
Sep 23 19:48:26 aio compiz[36136]: /usr/bin/compiz (core) - Warn: this should never happen. you should probably file a bug about this.

Revision history for this message
Johon Doee (jodoee11) wrote (last edit ):

Hi. Would you mind clicking the button "This bug affects you"? This way the issue gets more attention.

Meanwhile, it seems I found a workaround. I installed an extension [0] which disables unredirect fullscreen windows in gnome-shell and so far the freeze has not happened again. Maybe you wanna give it a try too.

Still, this is something that needs to be fixed.

[0]: https://extensions.gnome.org/extension/1873/disable-unredirect-fullscreen-windows/

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mutter (Ubuntu):
status: New → Confirmed
Revision history for this message
MasterCATZ (mastercatz) wrote (last edit ):
Download full text (5.5 KiB)

well I am using "Unity" and the other seems to be using "Gnome"
this is the only other reported instance in the last year that is similar to whats happening

and nothing really shows in logs so no idea what the issue is

has been happening all year from kernel 6 - 6.4

pretty sure it did not happen with 5.18

still deciding if I should roll back kernel to 5's or try 6.5 on next reboot
to see if its kernel related or mesa / some other update related
but then my VR headsets will break again going back to 5's

I can trigger it every-time so if their are any commands to run for debugging let me know

other things that are in the logs when it happen are

connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Sep 23 22:11:53 aio cpufreq-applica[1406267]: The offending callback was SourceFunc().
Sep 23 22:11:53 aio compiz[1406267]: == Stack trace for context 0x55d2c20f1170 ==
Sep 23 22:11:53 aio compiz[1406267]: #0 55d2c21c0f60 i /usr/bin/cpufreq-application:51 (3054f38c600 @ 58)
Sep 23 22:11:53 aio compiz[1406267]: #1 55d2c21c0ed8 i /usr/bin/cpufreq-application:56 (3054f38c650 @ 170)
Sep 23 22:11:54 aio cpufreq-applica[1406267]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
Sep 23 22:11:54 aio cpufreq-applica[1406267]: The offending callback was SourceFunc().
Sep 23 22:11:54 aio compiz[1406267]: == Stack trace for context 0x55d2c20f1170 ==
Sep 23 22:11:54 aio compiz[1406267]: #0 55d2c21c0f60 i /usr/bin/cpufreq-application:51 (3054f38c600 @ 58)
Sep 23 22:11:54 aio compiz[1406267]: #1 55d2c21c0ed8 i /usr/bin/cpufreq-application:56 (3054f38c650 @ 170)
Sep 23 22:11:55 aio systemd[1]: collectd.service: Scheduled restart job, restart counter is at 710586.
Sep 23 22:11:55 aio systemd[1]: Stopped Statistics collection and monitoring daemon.
Sep 23 22:11:55 aio systemd[1]: Starting Statistics collection and monitoring daemon...
Sep 23 22:11:55 aio collectd[285530]: Parse error in file `/etc/collectd/collectd.conf', line 889 near `<newline>': block not closed
Sep 23 22:11:55 aio collectd[285530]: yyparse returned error #1
Sep 23 22:11:55 aio collectd[285530]: configfile: Cannot read file `/etc/collectd/collectd.conf'.
Sep 23 22:11:55 aio collectd[285530]: Unable to read config file /etc/collectd/collectd.conf.
Sep 23 22:11:55 aio collectd[285530]: Error: Parsing the config file failed!
Sep 23 22:11:55 aio collectd[285530]: block_begin = Plugin; block_end = Listen;
Sep 23 22:11:55 aio systemd[1]: collectd.service: Main process exited, code=exited, status=1/FAILURE
Sep 23 22:11:55 aio systemd[1]: collectd.service: Failed with result 'exit-code'.
Sep 23 22:11:55 aio systemd[1]: Failed to start Statistics collection and monitoring daemon.
Sep 23 22:11:55 aio compiz[36136]: /usr/bin/compiz (core) - Warn: unhandled ConfigureNotify on 0x1d5bd3a!
Sep 23 22:11:55 aio compiz[36136]: /usr/bin/compiz (core) - Warn: this should never happen. y...

Read more...

Revision history for this message
Jeremy Bícha (jbicha) wrote :

MasterCATZ, this bug is about Ubuntu 23.10; it is different than an issue affecting Ubuntu 22.04 LTS. Also, this is a bug about Mutter (or GNOME Shell), not about Compiz and Unity. Please file a new bug for your issue.

https://help.ubuntu.com/community/ReportingBugs

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Johon, we fixed a fullscreen freeze issue with mutter 45.0-2ubuntu1 several hours ago. Please check for and install updates, then restart your computer. If you still have an issue with the new mutter version, please open a new bug using

ubuntu-bug libmutter-13-0

Revision history for this message
Ayub Sourjah (ayubsourjah) wrote (last edit ):

I am faced with the same issue even with all the updates in place. The only work around is to close the laptop screen and reopen it and login. This is only evident when I have an additional screen.

Ubuntu 23.10
X11
Kernel 6.5.0-10generic
Lenovo V15 G3 IAP

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug is closed as a duplicate of bug 2035016 which is also closed. So if you have any ongoing issues please open new bugs for them.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.