I'm sharing my experience in case it helps other Zorin users facing a frozen desktop or a system that won't boot.
The problem
My Zorin OS 18 Pro laptop stopped booting normally. The Zorin logo appeared, but the login screen would not load.
Using Ctrl + Alt + F3 to access a Linux terminal, I discovered that my 457 GB filesystem was 100% full.
Further investigation revealed:
/var/log/syslog.1— 208 GB/var/log/syslog— 38 GB/var/log/journal— approximately 4 GB
The system was repeatedly logging this GNOME Shell error:
Object .Gjs_ui_messageTray_Notification ... has been already disposed - impossible to emit any signal on it.
How I recovered the computer
With step-by-step assistance from ChatGPT, I completed the following:
1. Located the oversized logs
From a text terminal, I used:
df -h /
sudo du -xhd1 /var
sudo du -ahx /var/log | sort -h | tail -n 15
2. Stopped logging and recovered disk space
After identifying and preserving a sample of the errors, I temporarily stopped logging:
sudo systemctl stop syslog.socket rsyslog.service
I then emptied the two confirmed oversized files:
sudo truncate -s 0 /var/log/syslog.1
sudo truncate -s 0 /var/log/syslog
These commands destroy the contents of the named logs, so don't use them without verifying the files first.
Disk usage eventually fell from 100% to 44%.
3. Repaired the desktop
I temporarily disabled GNOME extensions, restarted the graphical desktop, and installed the available Zorin software updates.
I then restored these extensions individually:
gnome-extensions enable zorin-desktop-icons@zorinos.com
gnome-extensions enable zorin-menu@zorinos.com
gnome-extensions enable zorin-taskbar@zorinos.com
This restored my desktop icons, application menu, and taskbar. Other nonessential extensions remain disabled.
4. Added safeguards
I restarted system logging and verified that the error was no longer appearing.
I also:
- Configured
maxsize 100Mfor syslog rotation. - Changed the logrotate timer to check hourly.
- Reduced the system journal to approximately 500 MB and configured
SystemMaxUse=500M.
These measures reduce the risk of runaway log growth but are not absolute disk-space limits.
The results
My Zorin computer now boots normally. Disk usage is approximately 44%, the system log is around 1 MB, and the recurring GNOME notification error has not appeared in subsequent checks.
Possible cause
I cannot establish the precise software defect, but the repeated GNOME notification errors strongly suggest a GNOME Shell or extension-related problem.
I also discovered that Zorin developers discussed a possible GNOME Shell package conflict and released an updated package on November 6, 2026:
My recommendation: If your Zorin system suddenly freezes or refuses to boot, check disk usage and /var/log before reinstalling the operating system. Recovering disk space, updating the software, and carefully restoring desktop extensions may save your installation and personal files.
Hopefully, this experience will help someone else avoid a complete reinstall.