Could you let us know exactly when the freeze usually happens?
For example:
- While watching a video?
- During high system activity (like gaming or rendering)?
- When opening a PDF or document?
- When launching an application or opening a new window?
It happens at very different times, usually when I'm on the internet with the firefox browser or brave browser. But also just when I look at a photo or play a song or want to read an email. There is no apparent reason actually. When I look at the logs I can't make anything of it because it is full of English reasons that I don't understand. Remarkable perhaps is that the music continues to play but I can't click on anything. The mouse pointer keeps moving, for example I can go to the taskbar but can't click on anything. The keyboard also continues to work and then I can for example press the keys AltGr + SysRq + B and restart the computer. So it is only visual that everything freezes. This computer has a dual boot system with Zorin OS 17.3 Core and Windows 10 iot enterprise. The computer also freezes in Windows. I need Windows 10 to make music and videos that I cannot make in Linux because of the program Video deluxe 2025 and Music Maker 2024 from Magix. It is very annoying because then I have to reboot without the possibility to save the piece of music or film. Maybe it is a hardware error, I bought the motherboard, CPU and memory as a set from AliExpress (which is a Chinese brand) and maybe it is refurbished, I don't know.
I have contacted a computer technician and I am going to buy a new motherboard, 64 RAM memory and a new processor. To build a good workstation with water cooling. I already have the video card and the power supply of 1000 Watts.
Trust me friend, don't go for water cooling as it can lead to disaster. You would be much better purchasing a Noctua CPU cooler which is what I have.
It is also what Chris Titus recommends over water cooling.
OK friend, it will be an aircooler. thanks my friend!
1 Like
If you want save some Money, I can recommed the combination of Thermalright Cooler Heatsink+Noctua Fan.
2 Likes
send your log to chatgpt for quick analysis
1 Like
In view of hackers increasingly attacking flaws in ChatGPT I would avoid ChatGPT like the plague.
1 Like
I have shown the logs to Gemini and we have addressed an important problem, namely Apparmor profile in Firefox
Which I previously posted!
1 Like
We have removed the old Apparmor profile from the computer.
Then we restarted and the Backup Apparmor profile also deleted.
This is what Gemini now explains to me:
So far it is still good. Do we now have a new Apparmor profile?
That's great to hear! I am happy that the system remains stable.
Regarding your question whether we have a new Apparmor profile: No, we have not made a new profile.
What we have done is the following:
We have removed the defective, locally created or changed Apparmor profile called /etc/apparmor.d/firefox local (and the backup thereof,. Bak). This profile caused the error messages about 'ABI/4.0' and prevented Apparmor from starting correctly.
By removing this problematic profile, we have cleared the road for the standard Apparmor profiles to load correctly. For browsers such as Firefox, especially if they are installed via Snap (or another comparable container technology), the Apparmor profiles are often automatically managed by the system or the Snap package itself.
So, in essence we have removed an obstacle that blocked the correct effect of Apparmor. The system can now load and enforce its built-in, correct Apparmor profiles for Firefox and other applications, without the errors we saw earlier.
The result is the same as a "new" profile in the sense that Firefox now falls under a correctly enforced Apparmor policy, but we have not written any configuration files ourselves. We only cleaned up the damaged.
The Firefox browser that I use is not Snap or Flatpack but the Zorin OS APT package
Ah, thanks for this important clarification!
The fact that you use the Firefox browser as a Zorin OS APT package (and therefore not as a Snap or Flatuit) makes the behavior of the Firefox-Local Apparmor profile more logical.
Here is why that is important:
APT packages and Apparmor: If you install Firefox via APT, the system usually manages the Apparmor profiles via the standard Apparmor packages and their updates. A Firefox-local profile in /etc/apparmor.d/ would then typically be a manually created or adapted profile, or the result of a specific configuration that deviates from the standard. This explains why it could introduce a mistake. Snap and flat pack packages have their own, often more insulated and stricter managed Apparmor rules, which would cause conflicts with locally placed files less quickly.
So, the analysis remains the same: the defective Firefox locomotive file was the source of the Apparmor error. By removing it, we have enabled Apparmor to do its work correctly with the built -in or by APT profiles for Firefox and other applications, without this, now disappeared, who disappeared, conflicting file.
It is nice to know that you can now work stably with your familiar APT version of Firefox!
If freezing the system no longer happens, we have found the solution.
I will let you know if the computer is freezed.
I now have the following applications open:
Brave browser, Firefox browser, calculator, terminal, libreoffice writer, audacious, file manager Nautilus, Gedit, Software Shop and Terminal.
This is Gemini's answer:
That is a considerable list of applications that are open at the same time, and that is very good news that your system is still running stably!
You now have the following apps active:
Brave browser
Firefox browser
Calculator
Terminal (probably this session, and possibly an extra)
LibreOffice Writer
Audacious (for music)
Nautilus (file manager)
Gedit (text editor)
Software store (Zorin's software center)
This is a sturdy test of your system, with multiple browsers, an Office suite, a media player and system tools. The fact that you still do not experience freezes confirms almost certain that the Apparmor fix was the cause of your problems.
Your system now seems stable and ready for everyday use. Keep monitoring, but it looks very positive!
1 Like
The problem solving: Stable Zorin Os after Hard Freezes
My Zorin OS system repeatedly experienced hard freezes, where the mouse was still moving, but clicking or input via the keyboard was no longer possible. This always required a forced restart. After an in -depth analysis of the system logs (Journalctl), we have identified and resolved a specific cause.
The problem found: Apparmor errors
The key to the problem was in the Systemd logs and specifically with the Apparmor.service. Apparmor is a security module that places applications in a sandbox, so that they are limited in what they can do and to which system sources they have access.
The following log rules were consistent:
Systemd: Failed to Start Load Apparmor Profiles.
Apparmor parser error for /etc/apparmor.d in profile /etc/apparmor.d/firefox-local at Line 3: Could Not Open 'ABI/4.0': File or folder does not exist
Error: At Least One Profile Failed to Load
These errors indicated that Apparmor could not start correctly because a specific profile for Firefox (Firefox local) contained a reference to a non-existent file or folder ('ABI/4.0'). This defective profile ensured that the entire Apparmor service could not load, which led to underlying system instability and ultimately the Freezes. Even after an earlier attempt to remove the profile, it turned out that a backup made (firefox local) contained the same mistake.
The solution: Delete the defective Apparmor Profile
The solution consisted of identifying and removing this problematic Apparmor profile. Because the Firefox-Browser used is a regular Zorin OS APT package (and not Snap or Flatpak), this relies on the standard Apparmor profiles that are supplied by the system or Firefox APT package itself. The Firefox-local profile was probably a manual adjustment or a remnant of an earlier configuration that was no longer correct.
By removing the defective local profile, the standard, correct Apparmor profiles of the system could load undisturbed again.
Step-by-step terminal assignments
Here are the commands used in the terminal:
Check Apparmor's status to confirm the error:
Bash
SUDO Systemctl Status Apparmor
This showed the Failed Status and the Parser Error for Firefox-Local or Firefox-Local.bak.
Make a backup of the problematic profile (in case, although we removed it later):
(This command was performed when the error was still in Firefox local. If this file is already gone, this command will give a mistake, which is not a problem.)
Bash
SUDO CP /ETC/Apparmor.d/firefox-local /etc/apparmor.d/firefox-local.bak
Remove the (first) problematic Apparmor profile:
(This command could give a mistake the first time if the file had already disappeared, but later the backup turned out to be the culprit.)
Bash
SUDO RM /ETC/Apparmor.d/firefox-local
Remove the backup from the problematic Apparmor profile:
(This was the crucial step, because the backup contained the same mistake and the Apparmor service was still blocking.)
Bash
SUDO RM /ETC/Apparmor.d/firefox-local.bak
Restart the Apparmor service:
(Because the service is in a failed, it had to be restarted, not only recharged.)
Bash
SUDO Systemctl Start Apparmor
Check Apparmor's status to confirm the solution:
Bash
SUDO Systemctl Status Apparmor
After this step, the output indicated: Active: Active (Exited) and there were no more errors.
Restart the system to fully apply all changes:
Bash
Sudo reboot
The result
After successful execution of these steps, the Apparmor service was started correctly. The system has since remained stable, even with several applications at the same time active on four screens (including two browsers, a word processor, media player, file manager and more). The hard freezes have no longer occurred.
This solution suggests that a defect or outdated local Apparmor profile was the cause of system instability and the freezes. By removing this profile, Apparmor can do its work with the correct, standard profiles, which has significantly improved the stability of Zorin OS.
I am going to leave the topic open for a while in case the PC still freezed.
But I have the idea and the feeling that it is solved.
1 Like