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.
The main reason is that developers are constantly getting into these themes and breaking things!!
On top of that, these Zorin updates are breaking the system and can't be turned off.
Why, when I have only "security patches" enabled = I get these Zorin themes now? That's what broke my system!
Can't developers just stop at security patches? Let's figure out why people switched from Windows for these reasons, and this is exactly what's happening with Zorin, a system that's up to 2029 and has already been broken 2-3 times in 5 months of use.
NO MORE UPDATES - no need for themes, icons or anything else that breaks gnome and the system, I highly doubt anyone is testing this, given the problems.
all updates were with such tricks, these are themes and icons!!
with the new core my RTX4060Ti just read like everything was okay although in the logs it was noticeable without any unnecessary issues, launching any game - the game just froze and that's it.
Zorin Desktop Theme - NEVER UPDATE UNDER ANY CONDITIONS!!
anything related to Zorin icons - also avoid!
in addition it breaks your existing and working gnome extensions!
if the kernel can be changed - when the system starts, other updates to the system itself break everything to the root!
Zorin OS desktop theme - breaks gnome shell extension - Vitals in logs: invalid pointer
that's not all, also another extension - Desktop Widgets (Desktop Clock), began to lead the system to white screens of death, as in the photo above.
of the suspects other extensions that could have been affected:
Blur my shell and Rounded Window Corners Reborn.
finally I declare that if you disable the system extension in Zorin: Light Style you will stop messing with shortcuts on the desktop every time you log in to the system!
I don't know how to test all this to even break some of the system extensions.
maybe the logic is that a person installs their Zorin system and uses it without changing anything at all, without installing any programs or extensions?!
if this is so, then there are others that give more options, system customization, while not breaking anything with updates.
In principle, I found the culprit, rolled back the system, and I don't plan to update anything more than security patches until 2029.
Themes do not break things. The Zorin Themes and icons in the update did not break anything. You are jumping to a conclusion because Zorin Themes were included in the updates, even as you ignore the other system packages that were included in the updates.
They can... and not only can you turn off automatic updates, you can disable update notifications.
You could try to disable the third-party gnome extensions and test then. The more third-party extensions you add, the less stable the system becomes. Some extensions make conflicts with the Zorin extensions.
yes thank you, I understand that when a person installs only security patches in updates, he does not need any themes that break half of the extensions, an already configured system.
now the new kernel works normally with the video card and no problems, for example I can install their themes and everything will happen again, I am more than sure of this!!
you are talking about the extension side, so why did the developers add gnome to the system so that then everything would break with their updates and say that it is stable until 2029.
Other themes usually don't cause system crashes, unless they're incompatible with the GNOME desktop or too outdated. GNOME extensions, on the other hand, are much more critical.
For "rounded window corners reborn" are reported many crashes. It makes conflicts together with "blur my shell". Do you have also installed "just perfection"? It is not suitable for Zorin and leads to many problems.
I also noticed an error there as you could see they accelerated the new kernel, that is, the processor tries to start the video card even before the system starts.
so in the logs there was this error from nvidia, yes there is an error but the video card restarted although with problems.
the fact that everything is okay now proves that I will not update and I have no desire to do it at all!
so important security patches suit me it is my security on the Internet and the rest, other new drivers and errors do not suit me at all!
Why do they touch those themes/icons at all? This is not stability. I want to see someone who won't break anything and will live on this system without copies until 2029.
so I see it's better to turn off the update altogether or even better through the terminal and forget about it and work in a stable system - 1 copy is mine, another will be made automatically every day 2 copies + 1 mine don't take much and you can roll back if something happens!
these updates are simply not justified to be honest..
I came to Linux as a stable system, just for work, fun and relaxation, my Windows broke twice in six months and I see the same thing with Zorin and honestly I don't like it!
I just thought I would install a stable LTS system and forget about it until 2029, but no, everything was already working for me, even the unfamiliarity with the system as a whole went away within a month when I started using it on a regular basis every day.
if developers want to experiment there are other distributions without LTS.
with stable LTS systems there is no need for experiments and these updates at all!!!!
