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. you should probably file a bug about this. Sep 23 22:11:55 aio hud-service[36594]: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface “com.canonical.dbusmenu” on object at path /org/ayatana/bamf/window/228589571" Sep 23 22:11:55 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:55 aio cpufreq-applica[1406267]: The offending callback was SourceFunc(). Sep 23 22:11:55 aio compiz[1406267]: == Stack trace for context 0x55d2c20f1170 == Sep 23 22:11:55 aio compiz[1406267]: #0 55d2c21c0f60 i /usr/bin/cpufreq-application:51 (3054f38c600 @ 58) Sep 23 22:11:55 aio compiz[1406267]: #1 55d2c21c0ed8 i /usr/bin/cpufreq-application:56 (3054f38c650 @ 170) Sep 23 22:11:56 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:56 aio cpufreq-applica[1406267]: The offending callback was SourceFunc(). Sep 23 22:11:56 aio compiz[1406267]: == Stack trace for context 0x55d2c20f1170 == Sep 23 22:11:56 aio compiz[1406267]: #0 55d2c21c0f60 i /usr/bin/cpufreq-application:51 (3054f38c600 @ 58) Sep 23 22:11:56 aio compiz[1406267]: #1 55d2c21c0ed8 i /usr/bin/cpufreq-application:56 (3054f38c650 @ 170) Sep 23 22:11:57 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:57 aio cpufreq-applica[1406267]: The offending callback was SourceFunc(). Sep 23 22:11:57 aio compiz[1406267]: == Stack trace for context 0x55d2c20f1170 == Sep 23 22:11:57 aio compiz[1406267]: #0 55d2c21c0f60 i /usr/bin/cpufreq-application:51 (3054f38c600 @ 58) Sep 23 22:11:57 aio compiz[1406267]: #1 55d2c21c0ed8 i /usr/bin/cpufreq-application:56 (3054f38c650 @ 170) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2037121 Title: Freeze when going full screen while watching video Status in Mutter: New Status in mutter package in Ubuntu: Confirmed 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
