again new update breaks the system and how much can it be??!
they say it works don't touch it!!
why don't the developers just limit themselves to security patches?
vkedaxvip@vkedaxvip-MS-7B51:~$ uname -r
6.17.0-19-generic
vkedaxvip@vkedaxvip-MS-7B51:~$ dpkg --list | grep linux-image
ii linux-image-6.14.0-37-generic 6.14.0-37.37~24.04.1 amd64 Signed kernel image generic
ii linux-image-6.17.0-14-generic 6.17.0-14.14~24.04.1 amd64 Signed kernel image generic
ii linux-image-6.17.0-19-generic 6.17.0-19.19~24.04.2 amd64 Signed kernel image generic
ii linux-image-generic-hwe-24.04 6.17.0-19.19~24.04.2 amd64 Generic Linux kernel image
vkedaxvip@vkedaxvip-MS-7B51:~$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.
vkedaxvip@vkedaxvip-MS-7B51:~$ journalctl -p 3 -xb
бер 26 13:30:08 vkedaxvip-MS-7B51 kernel: x86/cpu: SGX disabled or unsupported by BIOS.
бер 26 13:30:10 vkedaxvip-MS-7B51 kernel:
бер 26 13:30:10 vkedaxvip-MS-7B51 bluetoothd[1029]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
бер 26 13:30:10 vkedaxvip-MS-7B51 bluetoothd[1029]: sap-server: Operation not permitted (1)
бер 26 13:30:10 vkedaxvip-MS-7B51 bluetoothd[1029]: Failed to set mode: Failed (0x03)
бер 26 13:30:30 vkedaxvip-MS-7B51 gdm-password][2082]: gkr-pam: unable to locate daemon control file
бер 26 13:30:31 vkedaxvip-MS-7B51 gdm3[1556]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
бер 26 13:30:33 vkedaxvip-MS-7B51 systemd[2097]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2340.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 253 and the job result is failed.
бер 26 13:30:33 vkedaxvip-MS-7B51 systemd[2097]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2337.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 249 and the job result is failed.
бер 26 13:30:33 vkedaxvip-MS-7B51 systemd[2097]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-2334.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 245 and the job result is failed.
бер 26 13:30:34 vkedaxvip-MS-7B51 systemd[2097]: Failed to start app-gnome-spice\x2dvdagent-2503.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 306 and the job result is failed.
бер 26 13:30:34 vkedaxvip-MS-7B51 systemd[2097]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2606.scope - Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 323 and the job result is failed.
бер 26 13:30:36 vkedaxvip-MS-7B51 gdm3[1556]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
you said break the system your system is crashed or it work ? because your journal have just some noises like 95% of linux install
here is my journal and my system never crash
mars 26 05:47:47 zorin-tof kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000009d800000-0x000000009fffffff], contact BIOS vendor for fixes
mars 26 05:51:53 zorin-tof gdm-password][1928]: gkr-pam: unable to locate daemon control file
mars 26 05:51:54 zorin-tof gdm3[1371]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
mars 26 05:52:05 zorin-tof gdm3[1371]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
mars 26 07:42:54 zorin-tof bluetoothd[1140]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
I caught this window, rebooted, and after 5-10 minutes this window appeared again, and it happened after an update, kernel or themes that recently appeared there - if you looked at the update logs there was just a theme and most likely that's it!
And the 6.14 Kernel worked for You, yes? Then I would suggest to stay on it or as an Alternative install an even newer Kernel with the Mainline Tool or using the Liquorix Repo:
the same errors this update was recently and it is related to themes, I don't know what was there but they broke something for sure I'll go to the Bazzite something these updates in Zorin flatter me, no install a stable system and use it but let's update and break everything, that's why I left Windows here the same perspective is enough for me!
I don't advise the system as a whole a lot of nuances!
I also try disabling the Desktop Widgets (Desktop Clock) extension, if it's not it then the system is broken and all thanks to the developers!
this is not the first time by the way I've already spoken about updates that broke the icons in the tray and so on.
It seems like a stable build until 2029, but no, there are also updates that break the system.
One of these updates broke something on me.
The errors started at 14:24:20, everything was fine before that, now the errors are specifically on the nvidia video card!!
here I think you can track what is breaking gnome shell
vkedaxvip@vkedaxvip-MS-7B51:~$ journalctl -p 3..4 -xb | grep -i "gnome-shell" | tail -n 50
бер 26 16:42:26 vkedaxvip-MS-7B51 /usr/libexec/gdm-x-session[1691]: dbus-daemon[1691]: Activating service name='org.a11y.atspi.Registry' requested by ':1.1' (uid=121 pid=1711 comm="/usr/bin/gnome-shell" label="unconfined")
бер 26 16:42:27 vkedaxvip-MS-7B51 /usr/libexec/gdm-x-session[1659]: dbus-daemon[1659]: [session uid=121 pid=1659] Activating service name='org.gnome.Shell.Screencast' requested by ':1.5' (uid=121 pid=1711 comm="/usr/bin/gnome-shell" label="unconfined")
бер 26 16:42:27 vkedaxvip-MS-7B51 /usr/libexec/gdm-x-session[1659]: dbus-daemon[1659]: [session uid=121 pid=1659] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.5' (uid=121 pid=1711 comm="/usr/bin/gnome-shell" label="unconfined")
бер 26 16:42:27 vkedaxvip-MS-7B51 /usr/libexec/gdm-x-session[1659]: dbus-daemon[1659]: [session uid=121 pid=1659] Activating service name='org.gnome.Shell.Notifications' requested by ':1.5' (uid=121 pid=1711 comm="/usr/bin/gnome-shell" label="unconfined")
бер 26 16:42:27 vkedaxvip-MS-7B51 gnome-shell[1711]: Trying to set label on QuickToggle. Use title instead.
бер 26 16:42:27 vkedaxvip-MS-7B51 /usr/libexec/gdm-x-session[1659]: dbus-daemon[1659]: [session uid=121 pid=1659] Activating service name='ca.desrt.dconf' requested by ':1.5' (uid=121 pid=1711 comm="/usr/bin/gnome-shell" label="unconfined")
бер 26 16:42:27 vkedaxvip-MS-7B51 gnome-shell[1711]: Ignoring length property that isn't a number at line 3229, col 24
бер 26 16:42:27 vkedaxvip-MS-7B51 gnome-shell[1711]: Ignoring length property that isn't a number at line 3229, col 24
бер 26 16:42:28 vkedaxvip-MS-7B51 gnome-shell[1711]: Ignoring length property that isn't a number at line 3229, col 24
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUnix.InputStream instead.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: Trying to set label on QuickToggle. Use title instead.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a979cc5f60 StBoxLayout ("…")] which is not in the stage.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a979cc8760 StLabel.vitals-panel-label:insensitive ("…")] which is not in the stage.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: invalid (NULL) pointer instance
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a979cc5f60 StBoxLayout ("…")] which is not in the stage.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a979cccde0 StLabel.vitals-panel-label:insensitive ("…")] which is not in the stage.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: invalid (NULL) pointer instance
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a979cc5f60 StBoxLayout ("…")] which is not in the stage.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a979cd0a80 StLabel.vitals-panel-label:insensitive ("…")] which is not in the stage.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: invalid (NULL) pointer instance
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a979cc5f60 StBoxLayout ("…")] which is not in the stage.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a979cd4770 StLabel.vitals-panel-label:insensitive ("…")] which is not in the stage.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: invalid (NULL) pointer instance
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a979cc5f60 StBoxLayout ("…")] which is not in the stage.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a979cd8460 StLabel.vitals-panel-label:insensitive ("…")] which is not in the stage.
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: invalid (NULL) pointer instance
бер 26 16:42:44 vkedaxvip-MS-7B51 gnome-shell[2371]: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
бер 26 16:42:46 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a977da9300 StWidget.panel-menu] which is not in the stage.
бер 26 16:42:46 vkedaxvip-MS-7B51 gnome-shell[2371]: st_widget_get_theme_node called on the widget [0x57a977dc4430 Gjs_ui_boxpointer_BoxPointer.popup-menu-boxpointer popup-menu:first-child] which is not in the stage.
бер 26 16:42:46 vkedaxvip-MS-7B51 gnome-shell[2371]: invalid (NULL) pointer instance
бер 26 16:42:46 vkedaxvip-MS-7B51 gnome-shell[2371]: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
бер 26 16:42:47 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [ShellTrayIcon] is on because it needs an allocation.
бер 26 16:42:47 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
бер 26 16:42:47 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
бер 26 16:42:54 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [ShellTrayIcon] is on because it needs an allocation.
бер 26 16:42:54 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
бер 26 16:42:54 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
бер 26 16:43:56 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
бер 26 16:43:56 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
бер 26 16:44:17 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
бер 26 16:44:17 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
бер 26 16:50:00 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
бер 26 16:50:00 vkedaxvip-MS-7B51 gnome-shell[2371]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
vkedaxvip@vkedaxvip-MS-7B51:~$
You could always try reinstalling Zorin OS to see if that corrects the issue. I installed the updates and my system is not having these issues and it looks like your the only one having this issue.
Same thing happens with POP OS on old computers. POP OS likes to install the latest and greatest, suddenly you get 20-kernels installed, and only 1 of them is able to boot the system.
Zorin OS tends to be more update stable, however, Zorin OS 18 suffers issues. I'm still on Zorin OS 16, and I don't have any of these issues. I know the frustration of unnecessary updates breaking a system.
But this is no Zorin Extension. And Gnome Extensions in Common can be a bit tricky.
Does Your System runs in Wayland or X11? You can check that with the Terminal Command echo $XDG_SESSION_TYPE and what Nvidia Driver do You use?
Because of the Logs: @Nourpon already mentioned that only because You have Log entries these doesn't automatically mean that they affect the System in an Amount like You have it with this Screen:
I would repeat my Comment from above and suggest to switch to the 6.14 Kernel if this one works well for You or think about to try a newer Kernel.
The logs are incomplete but I see several errors relating to Nvidia, GDM and Gnome - I think I saw one with Intel earlier...
GPU Stack errors can definitely lead to a GDM - Gnome Shell crash.
