Multi-Display Sleep Trouble: Screen Sleeps on Browser Window Maximize (work around fix)

This is driving me crazy!!! I'm hoping someone might know what this issue is, how to resolve it, or maybe that it is just a bug that needs to be fixed.

Thanks!

PREREQUISITES:

  • This only happens after the Displays have gone to Sleep at least once after a restart.
  • This DOESN'T happen if the Displays haven't gone to Sleep after a restart.
  • This mostly appears to happen with Chromium based Browser Windows. e.g. Brave, Edge, Edge WebApps, etc.
    • (Does also happen with Thunderbird and the Zorin Software App.)
  • This only happens on Displays connected to the Secondary Card on the top row (see Display Configuration).

SYSTEM SETUP:

        `osssssssssssssssssssso`           root@ZORIN-Z6 
       .osssssssssssssssssssssso.          ------------------------- 
      .+oooooooooooooooooooooooo+.         OS: Zorin OS 17.2 x86_64 
                                           Host: HP Z6 G4 Workstation SBKPF,DWKSBLF 
                                           Kernel: 6.8.0-45-generic 
  `::::::::::::::::::::::.         .:`     Uptime: 19 mins 
 `+ssssssssssssssssss+:.`     `.:+ssso`    Packages: 2703 (dpkg), 67 (flatpak) 
.ossssssssssssssso/.       `-+ossssssso.   Shell: bash 5.1.16 
ssssssssssssso/-`      `-/osssssssssssss   Resolution: 1600x900, 1600x900, 1600x900, 1600x900, 1600x900, 1600x900 
.ossssssso/-`      .-/ossssssssssssssso.   DE: GNOME 43.9 
 `+sss+:.      `.:+ssssssssssssssssss+`    WM: Mutter 
  `:.         .::::::::::::::::::::::`     WM Theme: ZorinBlue-Light 
                                           Theme: ZorinBlue-Light [GTK2/3] 
                                           Icons: ZorinBlue-Light [GTK2/3] 
      .+oooooooooooooooooooooooo+.         Terminal: gnome-terminal 
       -osssssssssssssssssssssso-          CPU: Intel Xeon Gold 6138 (40) @ 3.700GHz 
        `osssssssssssssssssssso`           GPU: AMD ATI Radeon RX 580 (radeonsi, polaris10, LLVM 17.0.6, DRM 3.57)
                                           GPU: AMD ATI Radeon RX 580 (radeonsi, polaris10, LLVM 17.0.6, DRM 3.57) 
                                           Memory: 7829MiB / 64086MiB

DISPLAY CONFIGURATION:

  • The bottom row of Displays are connected to the Primary Card set in the BIOS.
  • The top row of Displays are connected to the Secondary Card set in the BIOS.
  • The Bottom Left Display (6) is the Primary Display.

TROUBLE REPRODUCTION:

  • Allow the Displays Sleep (not the System itself).
  • Log back in (after screen lock).
  • Maximize a Chromium based Browser Window (or any problematic Application Window) on any of the susceptible Displays connected to the Secondary Card (top row), and the specific Display will Power Down (Power Save Mode),

WORK AROUND:
If I move the Mouse (guessing) where the Menubar for the problematic Application is, and triple-click it (or drag down) to get it to go back into Window mode, I can then get the Display to return to normal by:

  • Moving ANY Display slightly in the Display Settings, and clicking "Apply" will make the affected Display come back on.
  • Then the Display can be moved back into it's place, and Applied.
  • Everything will continue to work until another problematic Application Window is Maximized on any of the susceptible Displays.

MORE INFORMATION:
This specific trouble occurs with:

  • Brave Browser
    • Web Apps tied to Brave
  • Microsoft Edge
    • Web Apps tied to Edge
  • Thunderbird
  • The Software "App Store" (the one built-in Application I tested to also cause the trouble).

I did not test every built-in (included) App, but it seems most Application Windows will NOT produce the same Trouble. I've tested with:
Included with Zorin:

  • Audacity
  • Calculator
  • Calendar
  • Contacts
  • Disks
  • Evolution
  • Files
  • GIMP
  • HandBrake
  • Inkscape
  • Libre Office Apps
  • Maps
  • Photos
  • Settings
  • Software & Updates
  • System Monitor
  • Terminal
  • Text Editor
  • VLC
  • Weather

3rd Party:

  • CodeWeavers CrossOver
  • Microsoft Code
  • Piper
  • TeamViewer

THINGS I HAVE TRIED:
(Issue exists on both Zorin Pro 17.1 & 17.2)

  • Changing the Refresh Rate.
  • Downloaded and Installed open source graphics and ROCm Drivers from AMD.
    • amdgpu-install --usecase=graphics,rocm
  • Installed and activated Budgie Desktop Environment and LightDM Window Manager. <- Could not get Display Sleep to work at all with Budgie Desktop, so I just reverted back to Zorin and GDM3 (I tried to solve this issue for a while, but gave up because I don't really need to try to solve another issue for something I'm not going to use anyway).
  • Upgraded from Zorin Pro 17.1 to 17.2

GRAPHICS INFO:

glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: Radeon RX 580 Series (radeonsi, polaris10, LLVM 17.0.6, DRM 3.57, 6.8.0-45-generic) (0x67df)
    Version: 24.1.0
    Accelerated: yes
    Video memory: 8192MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 6222 MB, largest block: 6222 MB
    VBO free aux. memory - total: 31941 MB, largest block: 31941 MB
    Texture free memory - total: 6222 MB, largest block: 6222 MB
    Texture free aux. memory - total: 31941 MB, largest block: 31941 MB
    Renderbuffer free memory - total: 6222 MB, largest block: 6222 MB
    Renderbuffer free aux. memory - total: 31941 MB, largest block: 31941 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 8192 MB
    Total available memory: 40235 MB
    Currently available dedicated video memory: 6222 MB
OpenGL vendor string: AMD
OpenGL renderer string: Radeon RX 580 Series (radeonsi, polaris10, LLVM 17.0.6, DRM 3.57, 6.8.0-45-generic)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.1.0-devel
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.1.0-devel
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.1.0-devel
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

SPECIFIC SYSLOG OUTPUT FROM TROUBLE OCCURRENCE:

Failed to post KMS update: drmModeAtomicCommit: Invalid argument
Page flip discarded: drmModeAtomicCommit: Invalid argument
Failed to scan out client buffer: drmModeAtomicCommit: Invalid argument

DETAILED SYSLOG OUTPUT FROM TROUBLE OCCURRENCE:
Here is the last syslog from the following Steps:

  • Restart.
  • Login.
  • Wait for Display Sleep.
  • Unlock.
  • Maximize a Chromium based Browser Window on an affected Display (2). (Around 23.33.10)
  • Put the Chromium based Browser Window back into Window Mode.
  • Opened Settings -> Displays.
  • Move the affected Display slightly in the Display Settings, Apply. (Around 23:33:24-23:33:31)
  • Move the Display back into place, Apply. (Around 23:33:37)

You can see where the Display Sleep "Freak Out" happens around 23.33.10.

I shortened the repeating entries by about 600 lines!

tail -f /var/log/syslog
23:22:09 PackageKit: search-file transaction /1188_ceacdeea from uid 1001 finished with success after 489ms
23:22:10 PackageKit: get-updates transaction /1189_dcdccbed from uid 1001 finished with success after 494ms
23:22:10 PackageKit: get-updates transaction /1190_adbaadeb from uid 1001 finished with success after 573ms
23:22:11 snapd[5487]: overlord.go:515: Released state lock file
23:22:11 snapd[5487]: daemon stop requested to wait for socket activation
23:22:11 systemd[1]: snapd.service: Deactivated successfully.
23:22:17 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
23:22:31 geoclue[1502]: Service not used for 60 seconds. Shutting down..
23:22:31 systemd[1]: geoclue.service: Deactivated successfully.
23:22:33 systemd[1]: systemd-timedated.service: Deactivated successfully.
23:22:36 systemd[1]: systemd-localed.service: Deactivated successfully.
23:22:42 zeitgeist-datah[5580]: zeitgeist-datahub.vala:210: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required
23:22:42 systemd[1823]: Started Application launched by gnome-shell.
23:22:42 dbus-daemon[1113]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.116' (uid=1001 pid=5731 comm="/opt/brave.com/brave/brave " label="unconfined")
23:22:42 systemd[1]: Condition check resulted in Bluetooth service being skipped.
23:22:43 brave-browser.desktop[5730]: [5731:5731:0922/232243.679294:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented
23:22:45 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.28' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:22:45 systemd[1823]: Starting Virtual filesystem metadata service...
23:22:45 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'org.gtk.vfs.Metadata'
23:22:45 systemd[1823]: Started Virtual filesystem metadata service.
23:22:46 systemd[1823]: Started Application launched by gnome-session-binary.
23:22:46 systemd[1823]: Started Application launched by gnome-session-binary.
23:22:54 brave-browser.desktop[5730]: [5773:5773:0922/232254.001749:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
23:22:54 brave-browser.desktop[5730]: [5773:5773:0922/232254.006824:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
23:22:54 brave-browser.desktop[5730]: [5731:5731:0922/232254.870353:ERROR:interface_endpoint_client.cc(725)] Message 0 rejected by interface blink.mojom.WidgetHost
23:22:54 brave-browser.desktop[5730]: [5731:5731:0922/232254.987892:ERROR:interface_endpoint_client.cc(725)] Message 0 rejected by interface blink.mojom.WidgetHost
23:22:55 brave-browser.desktop[5730]: [5773:5773:0922/232255.394015:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
23:22:57 brave-browser.desktop[5730]: Warning: disabling flag --expose_wasm due to conflicting flags
23:23:08 gnome-shell[1949]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x638a51ec9c10), has been already disposed — 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.
23:23:08 gnome-shell[1949]: == Stack trace for context 0x638a50d804b0 ==
23:23:08 gnome-shell[1949]: #0   7ffd6ad4bdf0 b   resource:///org/gnome/shell/ui/workspacesView.js:639 (ce64aa2e470 @ 33)
23:23:08 gnome-shell[1949]: #1   7ffd6ad4bf40 b   resource:///org/gnome/shell/ui/workspacesView.js:686 (ce64aa2e510 @ 467)
23:23:08 gnome-shell[1949]: #2   7ffd6ad4d680 b   resource:///org/gnome/shell/ui/workspace.js:854 (3c28a87c18d0 @ 369)
23:23:08 gnome-shell[1949]: #3   7ffd6ad4d740 b   resource:///org/gnome/shell/ui/workspace.js:805 (3c28a87c1830 @ 17)
23:23:08 gnome-shell[1949]: #4   638a52317088 i   resource:///org/gnome/shell/ui/workspacesView.js:1016 (ce64aa2ef10 @ 124)
23:23:08 gnome-shell[1949]: #5   638a52316ff8 i   resource:///org/gnome/shell/ui/overviewControls.js:715 (3c28a87876a0 @ 39)
23:23:08 gnome-shell[1949]: #6   638a52316f70 i   resource:///org/gnome/shell/ui/layout.js:347 (f1b9d3cf1f0 @ 22)
23:23:08 gnome-shell[1949]: #7   638a52316ee0 i   resource:///org/gnome/shell/ui/overview.js:641 (3c28a8785510 @ 149)
23:23:08 gnome-shell[1949]: #8   638a52316e60 i   resource:///org/gnome/shell/ui/overview.js:627 (3c28a87854c0 @ 12)
23:23:08 gnome-shell[1949]: #9   638a52316de0 i   resource:///org/gnome/shell/ui/overviewControls.js:757 (3c28a8787880 @ 55)
23:23:08 gnome-shell[1949]: #10   7ffd6ad531d0 b   resource:///org/gnome/shell/ui/environment.js:150 (f1b9d38c9c0 @ 39)
23:23:08 gnome-shell[1949]: #11   638a52316d58 i   resource:///org/gnome/shell/ui/environment.js:316 (f1b9d38cec0 @ 14)
23:23:08 gnome-shell[1949]: == Stack trace for context 0x638a50d804b0 ==
23:23:08 gnome-shell[1949]: #0   7ffd6ad4bf40 b   resource:///org/gnome/shell/ui/workspacesView.js:688 (ce64aa2e510 @ 484)
23:23:08 gnome-shell[1949]: #1   7ffd6ad4d680 b   resource:///org/gnome/shell/ui/workspace.js:854 (3c28a87c18d0 @ 369)
23:23:08 gnome-shell[1949]: #2   7ffd6ad4d740 b   resource:///org/gnome/shell/ui/workspace.js:805 (3c28a87c1830 @ 17)
23:23:08 gnome-shell[1949]: #3   638a52317088 i   resource:///org/gnome/shell/ui/workspacesView.js:1016 (ce64aa2ef10 @ 124)
23:23:08 gnome-shell[1949]: #4   638a52316ff8 i   resource:///org/gnome/shell/ui/overviewControls.js:715 (3c28a87876a0 @ 39)
23:23:08 gnome-shell[1949]: #5   638a52316f70 i   resource:///org/gnome/shell/ui/layout.js:347 (f1b9d3cf1f0 @ 22)
23:23:08 gnome-shell[1949]: #6   638a52316ee0 i   resource:///org/gnome/shell/ui/overview.js:641 (3c28a8785510 @ 149)
23:23:08 gnome-shell[1949]: #7   638a52316e60 i   resource:///org/gnome/shell/ui/overview.js:627 (3c28a87854c0 @ 12)
23:23:08 gnome-shell[1949]: #8   638a52316de0 i   resource:///org/gnome/shell/ui/overviewControls.js:757 (3c28a8787880 @ 55)
23:23:08 gnome-shell[1949]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x638a51ec9c10), has been already disposed — 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.
23:23:08 gnome-shell[1949]: #9   7ffd6ad531d0 b   resource:///org/gnome/shell/ui/environment.js:150 (f1b9d38c9c0 @ 39)
23:23:08 gnome-shell[1949]: #10   638a52316d58 i   resource:///org/gnome/shell/ui/environment.js:316 (f1b9d38cec0 @ 14)
23:23:46 systemd[1823]: Started Application launched by gnome-session-binary.
23:26:07 zeitgeist-datah[5580]: zeitgeist-datahub.vala:210: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required
23:26:07 systemd[1823]: Started Application launched by gnome-shell.
23:26:08 dbus-daemon[1113]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.121' (uid=1001 pid=7026 comm="/opt/microsoft/msedge/msedge --profile-directory=D" label="unconfined")
23:26:08 systemd[1]: Condition check resulted in Bluetooth service being skipped.
23:26:13 msedge-bngdbpbgpaflcededbiphmicbhmcdbmf-Default.desktop[7033]: [7026:7026:0922/232613.162891:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented
23:26:25 msedge-bngdbpbgpaflcededbiphmicbhmcdbmf-Default.desktop[7033]: [7074:7074:0922/232625.713652:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
23:26:25 msedge-bngdbpbgpaflcededbiphmicbhmcdbmf-Default.desktop[7033]: [7074:7074:0922/232625.722238:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
23:26:28 systemd[1]: Starting Download data for packages that failed at package install time...
23:26:28 systemd[1]: update-notifier-download.service: Deactivated successfully.
23:26:28 systemd[1]: Finished Download data for packages that failed at package install time.
23:26:33 msedge-bngdbpbgpaflcededbiphmicbhmcdbmf-Default.desktop[7033]: [7074:7074:0922/232633.407769:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
23:26:51 zeitgeist-datah[5580]: zeitgeist-datahub.vala:210: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required
23:26:51 systemd[1823]: Started Application launched by gnome-shell.
23:26:51 microsoft-edge.desktop[7650]: Opening in existing browser session.
23:30:01 CRON[8011]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
23:31:56 systemd[1]: Started Run anacron jobs.
23:31:56 anacron[8059]: Anacron 2.3 started on 2024-09-22
23:31:56 anacron[8059]: Normal exit (0 jobs run)
23:31:56 systemd[1]: anacron.service: Deactivated successfully.
23:32:40 gnome-shell[1949]: Source ID 1083 was not found when attempting to remove it
23:32:40 gnome-shell[1949]: [x11gestures@joseexposito.github.io] Extension disabled
23:32:40 gnome-shell[1949]: [x11gestures@joseexposito.github.io] Building entry point for GNOME Shell 43.9
23:32:41 solaar[2266]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
23:32:41 polychromatic-t[2350]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
23:32:41 update-notifier[6066]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
23:32:41 dropbox[2315]: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
23:32:50 dbus-daemon[1113]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.83' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:32:50 systemd[1]: Starting Fingerprint Authentication Daemon...
23:32:50 dbus-daemon[1113]: [system] Successfully activated service 'net.reactivated.Fprint'
23:32:50 systemd[1]: Started Fingerprint Authentication Daemon.
23:32:50 gnome-shell[1949]: JS ERROR: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available#012asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
23:33:01 gnome-shell[1949]: loading user theme: /usr/share/themes/ZorinGrey-Dark/gnome-shell/gnome-shell.css
23:33:02 gnome-shell[1949]: [x11gestures@joseexposito.github.io] Extension enabled
23:33:02 gnome-shell[1949]: [x11gestures@joseexposito.github.io] This extension is only for X11
23:33:02 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating service name='org.freedesktop.FileManager1' requested by ':1.28' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:33:02 NetworkManager[1114]: <info>  [1727069582.3218] agent-manager: agent[091745ec9416245a,:1.83/org.gnome.Shell.NetworkAgent/1001]: agent registered
23:33:02 nemo[8111]: Current gtk theme is not known to have nemo support (ZorinGrey-Dark) - checking...
23:33:02 nemo[8111]: The theme appears to have no nemo support.  Adding some...
23:33:02 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'org.freedesktop.FileManager1'
23:33:03 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
23:33:03 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
23:33:03 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
23:33:03 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
23:33:03 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
23:33:03 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
23:33:03 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
23:33:03 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
23:33:03 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
23:33:10 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:10 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument

23:33:13 gnome-shell[1949]: Failed to scan out client buffer: drmModeAtomicCommit: Invalid argument
23:33:13 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:13 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument

23:33:17 gnome-shell[1949]: Failed to scan out client buffer: drmModeAtomicCommit: Invalid argument
23:33:17 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:17 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument

23:33:18 gnome-shell[1949]: Failed to scan out client buffer: drmModeAtomicCommit: Invalid argument
23:33:18 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:18 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument

23:33:18 gnome-shell[1949]: Failed to scan out client buffer: drmModeAtomicCommit: Invalid argument
23:33:18 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:18 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument

23:33:20 systemd[1]: fprintd.service: Deactivated successfully.
23:33:21 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:21 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument

23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating service name='org.gnome.ControlCenter.SearchProvider' requested by ':1.28' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating service name='org.gnome.Contacts.SearchProvider' requested by ':1.28' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating service name='org.gnome.Nautilus' requested by ':1.28' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.28' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating service name='org.gnome.Calendar' requested by ':1.28' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating service name='org.gnome.Characters.BackgroundService' requested by ':1.28' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating service name='org.gnome.clocks' requested by ':1.28' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating service name='org.gnome.seahorse.Application' requested by ':1.28' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating service name='org.gnome.Photos' requested by ':1.28' (uid=1001 pid=1949 comm="/usr/bin/gnome-shell " label="unconfined")
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'org.gnome.ControlCenter.SearchProvider'
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'org.gnome.clocks'
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'org.gnome.seahorse.Application'
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'org.gnome.Nautilus'
23:33:23 dbus-daemon[1113]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.127' (uid=1001 pid=8193 comm="/usr/bin/gnome-calendar --gapplication-service " label="unconfined")
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'org.gnome.Characters.BackgroundService'
23:33:23 systemd[1]: Starting Time & Date Service...
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'org.gnome.Photos'
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'org.gnome.Contacts.SearchProvider'
23:33:23 dbus-daemon[1113]: [system] Successfully activated service 'org.freedesktop.timedate1'
23:33:23 systemd[1]: Started Time & Date Service.
23:33:23 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'org.gnome.Calendar'
23:33:24 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'org.gnome.Calculator.SearchProvider'
23:33:24 systemd[1]: Starting Snap Daemon...
23:33:24 gnome-calculato[8191]: search-provider.vala:140: Failed to spawn Calculator: Child process killed by signal 9
23:33:24 snapd[8286]: overlord.go:271: Acquiring state lock file
23:33:24 snapd[8286]: overlord.go:276: Acquired state lock file
23:33:24 snapd[8286]: daemon.go:247: started snapd/2.63+22.04ubuntu0.1 (series 16; classic) zorin/17 (amd64) linux/6.8.0-45-generic.
23:33:24 kernel: [  728.070912] loop0: detected capacity change from 0 to 8
23:33:24 snapd[8286]: daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
23:33:24 snapd[8286]: backends.go:58: AppArmor status: apparmor is enabled and all features are available
23:33:24 systemd[1]: tmp-syscheck\x2dmountpoint\x2d164841083.mount: Deactivated successfully.
23:33:24 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:24 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:24 org.gnome.Nautilus[8189]: Initializing nautilus-dropbox 2020.03.04
23:33:24 nautilus[8189]: Connecting to org.freedesktop.Tracker3.Miner.Files
23:33:24 dbus-daemon[1842]: [session uid=1001 pid=1842] Activating service name='com.intel.dleyna-renderer' requested by ':1.163' (uid=1001 pid=8201 comm="/usr/bin/gnome-photos --gapplication-service " label="unconfined")
23:33:24 dleyna-renderer-service[8369]: dLeyna core version 0.6.0
23:33:24 dleyna-renderer-service[8369]: dleyna-renderer-service version 0.6.0
23:33:24 dleyna-renderer-service[8369]: Type[0] Level[0x13] Mask[0x4C] Flags[0x4F]
23:33:24 dleyna-renderer-service[8369]: Load file [/home/bulletproof/.config/dleyna-renderer-service.conf]
23:33:24 dleyna-renderer-service[8369]: [General settings]
23:33:24 dleyna-renderer-service[8369]: Never Quit: F
23:33:24 dleyna-renderer-service[8369]: Connector Name: dbus
23:33:24 dleyna-renderer-service[8369]: Port: 0
23:33:24 dleyna-renderer-service[8369]: Push host port: 0
23:33:24 dleyna-renderer-service[8369]: [Logging settings]
23:33:24 dleyna-renderer-service[8369]: Log Type : 0
23:33:24 dleyna-renderer-service[8369]: Log Level: 0x13
23:33:24 dleyna-renderer-service[8369]: [Network filtering settings]
23:33:24 dleyna-renderer-service[8369]: Enabled : F
23:33:24 dleyna-renderer-service[8369]: Entries: (null)
23:33:24 dbus-daemon[1842]: [session uid=1001 pid=1842] Successfully activated service 'com.intel.dleyna-renderer'
23:33:24 dleyna-renderer-service[8369]: Calling GetRenderers method
23:33:24 kernel: [  728.254753] audit: type=1400 audit(1727069604.390:39): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=8347 comm="apparmor_parser"
23:33:24 kernel: [  728.255250] audit: type=1400 audit(1727069604.390:40): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=8347 comm="apparmor_parser"
23:33:24 systemd[1]: Started Snap Daemon.
23:33:24 dleyna-renderer-service[8369]: Client :1.163 lost
23:33:24 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:24 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:25 zeitgeist-datah[5580]: zeitgeist-datahub.vala:210: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required
23:33:25 dleyna-renderer-service[8369]: dLeyna: Exit
23:33:25 systemd[1823]: Started Application launched by gnome-shell.
23:33:25 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:25 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
23:33:26 gnome-shell[1949]: Page flip discarded: drmModeAtomicCommit: Invalid argument
23:33:26 PackageKit: resolve transaction /1191_dcacebbe from uid 1001 finished with success after 362ms
23:33:27 PackageKit: resolve transaction /1192_ecabbbbc from uid 1001 finished with success after 344ms
23:33:29 snapd[8286]: daemon.go:519: gracefully waiting for running hooks
23:33:29 snapd[8286]: daemon.go:521: done waiting for running hooks
23:33:30 previews_daemon[2277]: gdk_monitor_get_geometry: assertion 'GDK_IS_MONITOR (monitor)' failed
23:33:30 previews_daemon[2277]: message repeated 5 times: [ gdk_monitor_get_geometry: assertion 'GDK_IS_MONITOR (monitor)' failed]
23:33:31 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
23:33:31 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
23:33:31 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
23:33:31 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
23:33:31 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
23:33:31 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
23:33:31 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
23:33:31 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
23:33:31 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
23:33:32 snapd[8286]: overlord.go:515: Released state lock file
23:33:32 snapd[8286]: daemon stop requested to wait for socket activation
23:33:32 systemd[1]: snapd.service: Deactivated successfully.
23:33:37 previews_daemon[2277]: gdk_monitor_get_geometry: assertion 'GDK_IS_MONITOR (monitor)' failed
23:33:37 previews_daemon[2277]: message repeated 5 times: [ gdk_monitor_get_geometry: assertion 'GDK_IS_MONITOR (monitor)' failed]
23:33:37 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
23:33:37 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
23:33:37 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
23:33:37 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
23:33:37 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
23:33:37 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
23:33:37 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
23:33:37 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
23:33:37 gnome-shell[1949]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).

There is a long list of Gnome Bug reports on this issue, sadly.
From what I can tell, this seems to begin with Gnome 41 and increase through Gnome 42 - and a larger number of reports with 43.

It gets interesting when Wayland and Xorg are factored in - With some users reporting it only happening on Wayland and others reporting it happens on Xorg - but only after logging in on Wayland, first then logging out and logging in on Xorg.
It does not seem to matter if AMD or Nvidia - so this leads me to suspect it is not a specific driver issue.
It is most reported as you describe it (and others) on Gnome, not XFCE or KDE (they do have similar issues that are described, but not a match).

I am sorry to bear bad news. It really does look like this needs an upstream fix in Gnome Shell. Most reports that are not directed to Gnome Shell get redirected to it.

2 Likes

Thanks for the reply!

Should I open a ticket elsewhere? Or maybe add to another one already open? If you could point me in the right direction, that would be great!

It's such a strange issue!!!

I have heard of this many times, so Have looked up reports a lot. Looking for some, now:

That is also the place to create a new bug report.

In the meantime, other members and Gnome users may post helpful suggestions so let's keep this open...

1 Like

I did come across that article (along with several others) over the course of troubleshooting this issue over the last couple weeks. Most of the stuff I found (like that article) was a couple, to several years old.

When I found reports of similar trouble from years ago, I thought: clearly these reports can't possibly still be relevant...but maybe that's not the case...

I decided to open a report here, partly because I've been using Zorin, and partly because I don't have the typical Multi-Display setup (6 Displays and 2 Graphics Cards).

Hopefully, at the very least, it might let someone else know that they are not alone!

Thanks again for your help!

This did make me wonder about your Power Supply and whether all six monitors were running at once. It is worth clarifying that for this thread, just in case.

Also - have you tested this (This may sound odd, but...) while using a different system user theme applied?
Some monitors do blink out when certain colors are quickly applied.

I have been running macOS on this HP Z6 Workstation for the last several years. I recently broke the OpenCore bootloader by updating to an incompatible BIOS and apparently can't roll back. :frowning_face:

After fighting with the BIOS, I decided to install Zorin on another Drive making it easier to troubleshoot the OpenCore boot issues. Accessing the EFI partition, creating ACPI aml files, etc, is much easier with a nix OS.

I also have a Windows 10 Drive that runs just fine, I just don't want to use Windows. I've been running macOS and various forms of nix for the last 20+ years. If I have to leave my hackintosh for something else, it's going to be some form of nix system. So far, I like the Zorin GUI the best. I've been using Zorin on one of my laptops since since 16 was first released. Before that I was using elementaryOS, and before that, Budgie. I really like all variations of Debian at the core.

:thinking: Now if there was just a great replacement for Finder. Pantheon Files is closest (Miller Columns), but it doesn't refresh quite right on Zorin, and there is no quicklook feature.

Anyway, it's definitely not an issue with the hardware. As long as I don't Maximize a Browser Window on one of those Displays, I can run for weeks without issue! I think the longest uptime I had running macOS was almost a year!

1 Like

Which system user theme would you recommend? You are just referring to one of the Zorin ones right?

Just switching themes, whichever are available - Try light and dark and test if there is a difference.

I admit; I doubt this is going to lead to it being the culprit. The symptoms are different: A color incompat blinks the monitor, it does not normally put it to sleep. But it is worth trying because the universe can be a strange place and it is an easy thing to eliminate.

1 Like

Are these Browers that you tried Flatpaks?

No, personally I try to avoid all things snap and flatpak as much as possible. I really prefer to use apt repos.

This specific trouble occurs with Microsoft Edge, Web Apps tied to Edge, Brave Browser, Thunderbird, and with the Software "App Store" (the one built-in Application I tested to also cause the trouble).

I did not test every built-in (included) App, but I do know that: Audacity, Calculator, Calendar, Contacts, Disks, Evolution, Files, GIMP, Inkscape, Libre Office Apps, Maps, Photos, Settings, Software & Updates, System Monitor, Terminal, Text Editor, VLC, & Weather do not cause this specific trouble.

1 Like

Updated Original Post with additional relevant information, updated layout structure, formatting, headings, steps, and corrected minor spelling / grammatical errors.

1 Like

Opened Issue for Gnome Shell on GitLab.

UPDATED: GitLab Issue was moved to mutter.

Just wanted to post an update. It appears that logging in with X11 instead of Wayland appears to resolve this issue. I will keep monitoring it to confirm, but for now at least, this seems to be a workaround until Development resolves the issue with Wayland.

1 Like

After hours upon hours of troubleshooting, it always seems to come down to one simple stupid little checkbox. :roll_eyes:

This is slightly bemusing to me, as many of us on the forum ask this first: Are you using X11 or Wayland... Except this time... heh...

It became a common question when Zorin OS 17 introduced a new default to Wayland instead of x11 for the first time in history.

Not sure why I didn't try it a lot sooner... but at least now there is a bug report, and maybe it will be addressed (patched) sooner than later. :sunglasses:

Thanks for all your input on this, I really appreciate it!

Update from GNOME GitLab:

Confirmed that running Meta.disable_unredirect_for_display(global.display) in looking glass (Alt-F2 -> type lg) in Wayland does also work as a workaround. Albeit, (as I'm sure you all already know) it does not stay across restarts, or logouts.