Gnome Stability issues/GDM Disconnecting behaviour on my Asus ROG Strix

Hey there guys I have been recently dealing with this issue where after a while if my Asus ROG Strix laptop. I have noticed that if it is sitting there idle for a while even with applications opened the whole GDM desktop will stop working and currently open applications will stop opening,working or responding, I have looked at my journalctl logs and I see a whole bunch of these similar logs of when it happens and I even did a fresh install just in case and it still is happening

Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): EDID vendor "CMN", prod id 5409
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Using hsync ranges from config file
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Using vrefresh ranges from config file
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Printing DDC gathered Modelines:
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Modeline "1920x1080"x0.0  342.06  1920 1968 2000 2080  1080 1090 1095 1142 -hsync -vsync (164.5 kHz eP)
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Modeline "1920x1080"x0.0  142.53  1920 1968 2000 2080  1080 1090 1095 1142 -hsync -vsync (68.5 kHz e)
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): EDID vendor "CMN", prod id 5409
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Using hsync ranges from config file
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Using vrefresh ranges from config file
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Printing DDC gathered Modelines:
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Modeline "1920x1080"x0.0  342.06  1920 1968 2000 2080  1080 1090 1095 1142 -hsync -vsync (164.5 kHz eP)
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (II) modeset(0): Modeline "1920x1080"x0.0  142.53  1920 1968 2000 2080  1080 1090 1095 1142 -hsync -vsync (68.5 kHz e)
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-0: disconnected
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-0: 2660.0 MHz maximum pixel clock
Jan 08 23:46:51 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0):
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-1: disconnected
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0):
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-2: disconnected
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
Jan 08 23:46:52 corey-rogstrixg512lug512lu /usr/lib/gdm-x-session[1420]: (--) NVIDIA(GPU-0):
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5641eb8d34e0] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5641ec3ebc00] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5641eb8d34e0] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5641ec3ebc00] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5641e7d0bcd0] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5641ea2edad0] is on because it needs an allocation.
Jan 08 23:46:53 corey-rogstrixg512lug512lu gnome-shell[1524]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e0000a
Jan 08 23:46:53 corey-rogstrixg512lug512lu rtkit-daemon[1129]: Successfully made thread 160249 of process 160226 owned by '1000' high priority at nice level -15.
Jan 08 23:46:53 corey-rogstrixg512lug512lu rtkit-daemon[1129]: Supervising 7 threads of 4 processes of 1 users.
Jan 08 23:47:00 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5641e7d0bcd0] is on because it needs an allocation.
Jan 08 23:47:00 corey-rogstrixg512lug512lu gnome-shell[1524]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5641ea2edad0] is on because it needs an allocation.
Jan 08 23:47:04 corey-rogstrixg512lug512lu gnome-shell[1524]: invalid (NULL) pointer instance

There is a lot more in the log to see, would you guys like to see a full log of the last boot?

Not sure if it is kernel related but I went back to kernel 6.5.13-7-MANJARO and haven’t had the issue pop up again for a while so far.

Scratch that, still happening…

Has anyone else run into this issue? it’s really annoying and I don’t know whats causing it :joy:

I made a post on Nvidia’s forum about it if anyone is interested as I am investigating the issue