I have a problem, which I thought was related to Nobara OS. But from what I see I am wrong. I just switched to Zorin, and the system has already crashed 2 times.
Compared to NobaraOS, which the PC was totally blocked, forcing me to shut it down by force from the button, let's say that half the system works.
The mouse works, but I can't click anything, the keyboard is unusable.
I can see the minutes pass on the clock.
If I am on steam, messages from friends who connect regularly appear.
Via phone with SSH I created a log, then at 01:13 I rebooted with the command.
Can you help me understand why this is happening to me. On Nobara, no one has been able to understand exactly what causes these crashes. Many hypotheses, the most voted the NVIDIA Drivers. I specify that I have been using Linux for 2 months, and with windows I have never had problems. Since I switched to this operating system, it regularly crashes, randomly.
Your link goes to a page which is inaccessible and with inappropriate language. Use pastebin instead. I am guessing you are using Core. Which version? Zorin defaults to a Wayland desktop, when you get to login screen, select your username then a cog appears, lower right. Click on the cog and choose Zorin on xorg. I would also advise you uninstall snap and flatpak completely from your system and only install Zorin APT packages from Software. Elswhere on this forum the general advice is to stick with nvidia 555 drivers, assuming your card supports it. Any driver numbers higher than this are still in Beta and therefore unstable. Better alternatives to Software are Apper and Synaptic Package Manager, both of which can be used to update your system and applications.
I am using the latest version of Zorin version 17.2. The default environment is x11.
Please note that I have not made any changes. Everything is installed by default.
If what you say about snap and flatpak is true why integrate it into the system?
Anyway I have not touched or changed anything about the system.
The drivers installed are the 550. Those installed by default during the installation of Zorin.
I created another log with the command journalctl -b -p err. I don't know if it can help.
dic 10 10:27:53 andrea-desktop kernel: x86/cpu: SGX disabled by BIOS.
dic 10 10:27:54 andrea-desktop kernel: hid-generic 0003:0B05:1815.0001: No inputs registered, leaving
dic 10 10:27:54 andrea-desktop kernel:
dic 10 10:27:55 andrea-desktop kernel: /dev/sr0: Can't open blockdev
dic 10 10:27:55 andrea-desktop systemd[1]: Failed to mount /mnt/ata-TSSTcorp_CDDVDW_SH-222AB_R8BZ6GDBA35514.
dic 10 10:27:58 andrea-desktop colord-sane[930]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
dic 10 10:27:59 andrea-desktop pipewire[1038]: spa.v4l2: '/dev/video0' VIDIOC_QUERYCTRL: ioctl non appropriata per il device
dic 10 10:28:00 andrea-desktop systemd[1029]: Failed to start Application launched by gnome-session-binary.
dic 10 10:28:00 andrea-desktop systemd[1029]: Failed to start Application launched by gnome-session-binary.
dic 10 10:28:01 andrea-desktop systemd[1029]: Failed to start Application launched by gnome-session-binary.
dic 10 10:28:25 andrea-desktop pulseaudio[1040]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
dic 10 10:42:38 andrea-desktop kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
The timestamps for these logs go from 00:44:26 - 01:11:41. Is this when the crash happened? It might be a good idea to include something from the next boot in case there's some trace of the system attempting to recover from an exception or something. Although, if the system did crash entirely is also possible that no logs have been kept about it.
Do you get any errors if you start with graphics disabled (should appear as an option on the boot menu)?
This is a whole other topic for another day. There's another discussion in this thread that you can read through to get a general idea:
Perfect, I will read that discussion with great pleasure.
So, Regarding Storm, yes I am a gamer. For this reason I initially used Nobara. Precisely because I was focused on Gaming.
BUT having this problem, I thought it was due to him, and I switched to Zorin.
Regarding the time of the block, yes it is correct. Around that time. And at 01:13 I rebooted with the terminal command from a cell phone connected with SSH.
No, as specified, the system is not completely blocked, but partially. In fact on Nobara, the block prevented me from accessing even via SSH. On Zorin instead I connect and can use the terminal. From there I executed the command and the log and told it to save in .txt format. I uploaded everything online and shared the generated logs with you.
I think I'll go back to Windows. Zorin crashed again. I rebooted, and now the OS won't boot. Zorin is even worse than NobaraOS. It seems my PC doesn't like Linux.
I don't even know what to do... the BIOS is set to ultra fast. and that in this mode the keyboard is not immediately detected when turned on. I don't even know how to access the BIOS....
EDIT:
I managed to install Zorin. I have to say that as an experience after only 2 days it has already crashed 5 times. Worse than NobaraOS which had an average of two crashes per week.
So let's start over. For the next block, what do you need besides journalctl logs?
Let's start at the beginning (#a very good place to start# - Sound of Music). Did you check the hash sum of the downloaded .iso before creating bootable media? Did you use a Download Accelerator Manager (DAM) or Toreent to get the .iso? DAM's have been advised against being used with respect to earlier versions of Zorin leading to a corrupt .iso. You came from Windows. What is the make and model of the machine? Normally to get to the BIOS you have to press a function key (F2 or F10 being the usual culprits), or the DEL(ete) key whilst powering on. On a rare occasion I came across a BIOS that needed F8 to boot into the BIOS. If you can get into the BIOS I would disabke fast boot and secure boot, then try to install Zorin. But before we get that far, can you boot into 'Try Zorin' and run GParted to view the layout of your hard drive and the type of hard drive in use.
So, no I didn't check hash of .iso file and I don't know how to do it. No Download Accelerator Manager .
For BIOS fixed, Fast Boot disabled and now I can access it with F11.
The disk is an SSD from the XPG brand Model: (ADATA SX8200PNP (42AZS6AC) Serial number: 2K0320082983
I am new to using Linux, and I have to say what a terrible experience... And I am still convinced that I want to use it, but if there are such serious problems, well at least on my machine, it is not stable, whatever distribution I try. Windows is more stable and usable...
EDIT:
I saw a site page about Zorin. It specifies that it does this file check at the beginning before starting the installation. No errors reported.
I also followed the QuickHash guide and Set SHA256 and verified the .iso file.
This is what it showed at the end of the check.
E68D49172964E4D0AA39AC1D77674D724B0B835658836A56FC1B318680DEAED6
Everything seems ok.
System crashed even now that I reinstalled Zorin OS.
The crash occurred at 15:53.
I had started a game on steam. Seeing that the audio was not playing from the speakers, I minimized the game, clicked on the audio properties to change the output from headphones to speakers.
I could not do it, because the system crashed.
So I access the terminal via SSH, create the logs and at 15:58 I restart the PC via terminal.
SGX (Software Guard Extensions) is a set of security-related instructions introduced by Intel. It allows applications to create secure enclaves, isolated regions of memory, where sensitive computations or data can be protected from other parts of the system, including the operating system and other applications. It’s used in scenarios like:
Secure data processing.
Digital Rights Management (DRM).
Cryptographic key management.
Why is SGX Disabled?
Disabled in BIOS by Default: Most BIOS/UEFI configurations disable SGX by default for security or compatibility reasons.
Lack of Use Case: SGX is not widely used by most consumer applications, so many users don't need it.
Security Concerns: There have been vulnerabilities in SGX in the past, so some manufacturers or users may choose to disable it proactively.
Should You Enable SGX?
This depends on your use case:
You don't need it: If you're a general user without specific applications requiring SGX, you can safely ignore this message.
You need it: If you're running software that explicitly requires SGX (e.g., certain cryptographic applications or Intel-specific security software), you can enable it in your BIOS/UEFI settings.
Unfortunately it's not that simple... is not like we're going to find a line in the logs that says "You got me!".
Just so you know, Nvidia is famous for it being notoriously difficult to work alongisde Linux. For context:
This error does popup a few times:
[drm:nv_drm_master_set [nvidia_drm]] ERROR [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
I found a few threads similar to this one, where there are several proposed solutions with different degrees of success. Have a look and try some of them and see if that helps:
I have followed some of the advice in that thread. Let's see if it improves.
Anyway, here are the specs.
Since the problem is related to the graphical environment, since it crashes but it is still possible to access the PC via SSH, I used this command, journalctl -u gdm this is the log reported. I do not know if it is related to the crash.
dic 10 14:22:33 andrea-desktop systemd[1]: Starting GNOME Display Manager...
dic 10 14:22:33 andrea-desktop systemd[1]: Started GNOME Display Manager.
dic 10 14:22:36 andrea-desktop gdm-autologin][952]: gkr-pam: no password is available for user
dic 10 14:22:36 andrea-desktop gdm-autologin][952]: pam_unix(gdm-autologin:session): session opened for user andrea(uid=1000) by (ui>
dic 10 14:22:36 andrea-desktop gdm-autologin][952]: gkr-pam: gnome-keyring-daemon started properly
dic 10 15:58:14 andrea-desktop systemd[1]: Stopping GNOME Display Manager...
dic 10 15:58:14 andrea-desktop gdm3[892]: Gdm: Failed to contact accountsservice: Errore nel chiamare StartServiceByName per org.fre>
dic 10 15:58:14 andrea-desktop systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
dic 10 15:58:14 andrea-desktop systemd[1]: gdm.service: Failed with result 'exit-code'.
dic 10 15:58:14 andrea-desktop systemd[1]: Stopped GNOME Display Manager.
dic 10 15:58:14 andrea-desktop systemd[1]: gdm.service: Triggering OnFailure= dependencies.
dic 10 15:58:14 andrea-desktop systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.se>
-- Boot f58f332edb2f4596bb716916200cbe5b --
dic 10 15:58:41 andrea-desktop systemd[1]: Starting GNOME Display Manager...
dic 10 15:58:41 andrea-desktop systemd[1]: Started GNOME Display Manager.
dic 10 15:58:44 andrea-desktop gdm-autologin][1050]: gkr-pam: no password is available for user
dic 10 15:58:44 andrea-desktop gdm-autologin][1050]: pam_unix(gdm-autologin:session): session opened for user andrea(uid=1000) by (u>
dic 10 15:58:44 andrea-desktop gdm-autologin][1050]: gkr-pam: gnome-keyring-daemon started properly
dic 10 16:32:22 andrea-desktop systemd[1]: Stopping GNOME Display Manager...
dic 10 16:32:22 andrea-desktop gdm3[1005]: Gdm: Failed to contact accountsservice: Errore nel chiamare StartServiceByName per org.fr>
dic 10 16:32:22 andrea-desktop systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
dic 10 16:32:22 andrea-desktop systemd[1]: gdm.service: Failed with result 'exit-code'.
dic 10 16:32:22 andrea-desktop systemd[1]: Stopped GNOME Display Manager.
The gdm bits you posted appear to be related to the fact you have autologin enabled, or no password on your account, or if you are using SSH without credentials. I was wondering if you might be better replacing gdm with lightdm to see if that makes any difference. Open a terminal and enter:
Absolutely not. Name and password is set. And auto login is enabled. I read the article, however I don't think it is related to solving my problem. Changing display manager for credentials, I don't think it will solve the blocking problem.
