Constant crashes/reboot since a couple of months

Hello there,

Anyone else experiencing constant reboots/crashes on Zorin OS16 since a couple of months?

I thought it was going to get solved as it could have been a single update issue, but no :frowning: ... Depending on the daily updates, it gets worse or more stable

Pity as everything was working super nicely, and stable... Without any crash/reboot until a couple of months I think with an update a couple of months ago, my system started suddenly and randomly crashing. Since then depending on the daily updates, it happens once a day or like today,with today's update, it is every 5 minutes...
I basically cannot use it... Trying to figure out what could have caused it. I remember once installing Google Chrome, as it was crashing a lot while using it. But now, even when writing emails on Mailspring (and only that app opened), it crashes:(

Very frustrating experience as I paid for the Plus version, that I LOVED but I'm seriously considering changing as I can't trust its stability anymore.

If anybody has any recommendations or has experienced such crashes/reboots, I'd appreciate a feedback/resolution.

Alternatively, if it can't be trusted, and recommended OS to migrate to

Thanks
Lester

Can you check your system journal to see if there is anything wrong there ?

sudo journalctl -r

What gpu do you have ? and what kernel are you using ?

2 Likes

5.15.0-52-generic
Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280] (prog-if 00 [VGA controller])

Not sure if the journal log is readable the way I copied it

-- Logs begin at Sat 2022-05-07 08:58:58 CEST, end at Tue 2022-11-29 12:49:26 CET. --
Nov 29 12:49:26 lester-zorin sudo[8391]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 29 12:49:26 lester-zorin sudo[8391]: lester : TTY=pts/0 ; PWD=/home/lester ; USER=root ; COMMAND=/usr/bin/journalctl -r
Nov 29 12:49:25 lester-zorin systemd[1]: fprintd.service: Succeeded.
Nov 29 12:49:20 lester-zorin gnome-shell[4691]: ../clutter/clutter/clutter-actor.c:9589: Actor 'StBin' tried to allocate a size of -2147483648.00 x -2147483648.00
Nov 29 12:49:20 lester-zorin gnome-shell[4691]: ../clutter/clutter/clutter-actor.c:9589: Actor 'StDrawingArea' tried to allocate a size of -2147483648.00 x -2147483648.00
Nov 29 12:49:20 lester-zorin gnome-shell[4691]: clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) && !isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed
Nov 29 12:49:20 lester-zorin systemd[1]: blueman-mechanism.service: Succeeded.
Nov 29 12:49:20 lester-zorin systemd-timesyncd[1424]: Initial synchronization to time server 91.189.91.157:123 (ntp.ubuntu.com).
Nov 29 12:49:19 lester-zorin systemd[1]: systemd-fsckd.service: Succeeded.
Nov 29 12:49:19 lester-zorin PackageKit[4102]: get-details transaction /2212_bbdcdbbe from uid 1000 finished with success after 281ms
Nov 29 12:49:19 lester-zorin blueman.desktop[4917]: blueman-applet 12.49.19 WARNING DiscvManager:109 update_menuitems: warning: Adapter is None
Nov 29 12:49:19 lester-zorin pulseaudio[4421]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Nov 29 12:49:19 lester-zorin PackageKit[4102]: search-file transaction /2211_dbeebdec from uid 1000 finished with success after 366ms
Nov 29 12:49:19 lester-zorin dbus-daemon[1497]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Nov 29 12:49:18 lester-zorin PackageKit[4102]: search-file transaction /2210_ebbdcbad from uid 1000 finished with success after 877ms
Nov 29 12:49:17 lester-zorin PackageKit[4102]: resolve transaction /2209_bbedbbbb from uid 1000 finished with success after 302ms
Nov 29 12:49:17 lester-zorin gnome-software[5606]: automatically prevented from changing kind on system/snap//runtime/io.snapcraft.core18-CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6/latest/stable from runtime to unknown!
Nov 29 12:49:16 lester-zorin gnome-software[5606]: automatically prevented from changing kind on system/snap/
/runtime/io.snapcraft.bare-EISPgh06mRh1vordZY9OZ34QHdd7OrdR/latest/stable from runtime to unknown!
Nov 29 12:49:16 lester-zorin gnome-software[5606]: automatically prevented from changing kind on system/snap//desktop/io.snapcraft.snapd-PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4/latest/stable from desktop to unknown!
Nov 29 12:49:16 lester-zorin gnome-shell[4691]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Nov 29 12:49:16 lester-zorin gnome-shell[4691]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Nov 29 12:49:16 lester-zorin gnome-shell[4691]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Nov 29 12:49:16 lester-zorin gnome-shell[4691]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Nov 29 12:49:16 lester-zorin gnome-shell[4691]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Nov 29 12:49:16 lester-zorin gnome-shell[4691]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Nov 29 12:49:16 lester-zorin gnome-shell[4691]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Nov 29 12:49:16 lester-zorin gnome-shell[4691]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Nov 29 12:49:16 lester-zorin gnome-shell[4691]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Nov 29 12:49:15 lester-zorin gnome-software[5606]: automatically prevented from changing kind on system/snap/
/runtime/io.snapcraft.core20-DLqre5XGLbDqg9jPtiAhRRjDuPVa5X1q/latest/stable from runtime to unknown!
Nov 29 12:49:15 lester-zorin snapd[1521]: storehelpers.go:748: cannot refresh: snap has no updates available: "bare", "brave", "core", "core18", "core20", "core22", "gimp", "gnome-3-28-1804", "gnome-3-34-1804", "gnome-3-38-2004", "gnome-42-2204", "gtk-common-themes", "gtk2-common-themes", "mailspring", "signal-desktop", "snapd", "thunderbird", "whatsapp-for-linux", "youtube-musi>
Nov 29 12:49:15 lester-zorin gnome-software[5606]: automatically prevented from changing kind on system/snap//runtime/io.snapcraft.core22-amcUKQILKXHHTlmSa7NMdnXSx02dNeeT/latest/stable from runtime to unknown!
Nov 29 12:49:15 lester-zorin gnome-software[5606]: automatically prevented from changing kind on system/package/
/generic/org.a11y.brltty/* from generic to unknown!
Nov 29 12:49:15 lester-zorin PackageKit[4102]: resolve transaction /2208_cebaaada from uid 1000 finished with success after 1441ms
Nov 29 12:49:14 lester-zorin systemd[1]: Removed slice User Slice of UID 124.
Nov 29 12:49:14 lester-zorin systemd[1]: Stopped User Runtime Directory /run/user/124.
Nov 29 12:49:14 lester-zorin systemd[1]: user-runtime-dir@124.service: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[1]: run-user-124.mount: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[4412]: run-user-124.mount: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[1]: Stopping User Runtime Directory /run/user/124...
Nov 29 12:49:14 lester-zorin systemd[1]: Stopped User Manager for UID 124.
Nov 29 12:49:14 lester-zorin systemd[1]: user@124.service: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Reached target Exit the Session.
Nov 29 12:49:14 lester-zorin systemd[3869]: Finished Exit the Session.
Nov 29 12:49:14 lester-zorin systemd[3869]: systemd-exit.service: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Reached target Shutdown.
Nov 29 12:49:14 lester-zorin systemd[3869]: Closed REST API socket for snapd user session agent.
Nov 29 12:49:14 lester-zorin systemd[3869]: snapd.session-agent.socket: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Closed Sound System.
Nov 29 12:49:14 lester-zorin systemd[3869]: pulseaudio.socket: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Closed debconf communication socket.
Nov 29 12:49:14 lester-zorin systemd[3869]: pk-debconf-helper.socket: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Closed Multimedia System.
Nov 29 12:49:14 lester-zorin systemd[3869]: pipewire.socket: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Closed GnuPG cryptographic agent and passphrase cache.
Nov 29 12:49:14 lester-zorin systemd[3869]: gpg-agent.socket: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Nov 29 12:49:14 lester-zorin systemd[3869]: gpg-agent-ssh.socket: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Nov 29 12:49:14 lester-zorin systemd[3869]: gpg-agent-extra.socket: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Nov 29 12:49:14 lester-zorin systemd[3869]: gpg-agent-browser.socket: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Closed GnuPG network certificate management daemon.
Nov 29 12:49:14 lester-zorin systemd[3869]: dirmngr.socket: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Closed D-Bus User Message Bus Socket.
Nov 29 12:49:14 lester-zorin systemd[3869]: dbus.socket: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped target Timers.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped target Sockets.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped target Paths.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped target Basic System.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Nov 29 12:49:14 lester-zorin systemd[3869]: gvfs-afc-volume-monitor.service: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped Virtual filesystem service - disk device monitor.
Nov 29 12:49:14 lester-zorin systemd[3869]: gvfs-udisks2-volume-monitor.service: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped Tracker file system data miner.
Nov 29 12:49:14 lester-zorin systemd[3869]: tracker-miner-fs.service: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Removed slice session.slice.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped Multimedia Service.
Nov 29 12:49:14 lester-zorin systemd[3869]: pipewire.service: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopping Multimedia Service...
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped Multimedia Service Session Manager.
Nov 29 12:49:14 lester-zorin systemd[3869]: pipewire-media-session.service: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped D-Bus User Message Bus.
Nov 29 12:49:14 lester-zorin systemd[3869]: dbus.service: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[1]: run-user-124-gvfs.mount: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped Tracker metadata database store and lookup manager.
Nov 29 12:49:14 lester-zorin systemd[3869]: tracker-store.service: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped Virtual filesystem service.
Nov 29 12:49:14 lester-zorin systemd[3869]: gvfs-daemon.service: Succeeded.
Nov 29 12:49:14 lester-zorin systemd[3869]: Stopped Virtual filesystem metadata service.

1 Like

I see two things in the log you posted that may account for consistent crashing or freezing.

If the system is searching for Bluetooth devices with non available, it creates a memory loop that can result in a Crash.
Do you have or use Bluetooth devices? If you do not, then this can be readily solved by disabling Bluetooth entirely.

sudo apt remove --purge bluez

This is a gnome-shell-extension bug and gnome-shell is the major function in a crash.
The solution s to avoid, remove or not use a Dash To Dock style extension.

Other than the above:
Have you tried testing on an earlier kernel like 5.15.0-35?

You also might test if it is a RAM issue that is causing it.
You can test this by freeing up RAM regularly while working

And seeing if it crashes, still. If it does not, then we know that RAM error may be the culprit.

2 Likes

Thank you for your response. A few questions if you don't mind.

  • I have a keyboard and mouse connected via a Bluetooth dongle (plugged on a USB). Will they work if I remove the Bluetooth with your suggested command line?
  • I'm using the Zorin Dash as I find it esthetic than a menu bar. Are you advising to switch to that?
  • Where could I select a different Kernel? On advanced option on booting, I only have Kernel ending with 50 (not loading) or 52 (current). Where could I find/use your recommended one?
  • I have 24gb of ram and I only have Chrome and email software (Mailspring) opened when rebooting. Not sure the ram is that much of an issue

Last but not least, what changed in the OS updates that have caused all these issues which were not present for the first months of the OS16 release?

Thanks in advance

The removal was framed as:

You do have Bluetooth devices in use, so please do not remove Bluez.
The removal is a simple fix since it is unneeded.
If it is needed, then we need a complex fix.

I agree; but it may be the cause of the crashing.

Gnome Extensions are great when they work. When they do not... the desktop crashes. As Gnome does not support nor endorse the use of extensions, gnome-dev will provide no help in this.

Upon reboot, tap esc key or tab key (sometimes like you are the drummer for Metallica) to pull up the Grub Menu at startup.
From the Grub menu, select Advanced Options for Zorin.
From there, you will see the kernels you have listed and can select one to boot from.

I truly wish I knew.
But if you are willing to test Not Running Dash to see if that changes anything, it may help to narrow down what is going on.

1 Like

Again thank you for your response and help!

I now have changed it to the taskbar, and hopefully it will stopped the rebooting.
Edit: rebooted twice since the change to the taskbar (third choice on the available options in the Zorin layout tab in Zorin Appearance)
Edit 2: Changed it to the first choice (first one on Zorin layout options) now, and it seems more stable... hasn't reboot in the past 5 minutes

As per the choice of kernels I have once I go Advanced Option at booting is:
Zorin
Zorin, with Linux 5.15.0-50
Zorin with Linux 5.15.0-52 (doesn't work as it says that the kernel must be loaded first)

Let see how it goes... the "Windows" taskbar layout is my least favourite, but let's see if it provides stability. If so, I might test the others taskbar option (fourth one seemed to be unstable from one try)

So, not really changing much or the reboot I'm afraid...

I think I might need to reinstall Zorin OS and give it a fresh start :frowning:

Or maybe I just switch to another distro. Thinking of Manjaro

1 Like

I wonder if an earlier kernel may be what you need, too.

sudo apt install linux-headers-5.15.0-46-generic linux-image-5.15.0-46-generic linux-modules-5.15.0-46-generic linux-modules-extra-5.15.0-46-generic

1 Like

Trying to think of anything specific I might have done before the issues started... And the only thing I can really remember is that I installed Google Chrome. I am/was using Brave and Firefox as well.

Seems like the issues stared after. I have uninstalled Chrome a couple of days ago, but nothing changed. Removing the Dash on Dock seemed to have reduce the frequency (a bit) of the reboots but not eliminated them.

It doesn't seem to be software related. I could be only using Firefox or Mailspring when it happens... I don't program nor use specific RAM intensive softwares.

My usage is really only web, LibreOffice and emails. Sometimes photo editing but not since the issues started

Thanks for the suggestion, I shall try it

I am using some transparency theme, so I might try to go to "pure/basic" Zorin layout aside the taskbar. And see if that helps. If not, then try your suggestion

1 Like

Update:
Good news as my system seems to be stable since yesterday evening. No reboot since then.

  • I have changed my appearance settings to Day/Night Zorin theme, and set the interface to the first choice of Taskbar.
  • I have also uninstall Google.

I will keep it so for a couple of days to check the stability, then try to reinstall Google to verify if that was creating any issues.

Again, thanks everybody for your support and suggestions on this matter.

1 Like