Stuck on infinite logo screen

General Help
1

I tried going to recovery mode, but nothing worked my pc is stuck on infinite logo screen.

Any way to fix this.

photo_2026-08-08_21-44-49
photo_2026-08-08_21-44-49960×1280 182 KB

2

Try hit Escape button and take a picture of it if it tells you where it's stuck.

3

photo_2026-08-08_21-44-49
photo_2026-08-08_21-44-49960×1280 182 KB

4

Did this happen after you first installed Zorin or is it a new situation after things worked OK for a while?

Do you have a dual boot or single?

Is your BIOS UEFI or Legacy?

What graphics?

Is secure boot and fast boot off?

1 Like
5

I wasn’t using the desktop that often I installed the Zorin month ago and had no problem; I got update notifications yesterday after the update I was playing game and during the game screen turned off then I forced shut it down and it’s stuck since then.

Single boot.
Legacy
RTX3090
Both fast boot and secure are OFF

6

My first move would be to try picking an older kernel from the advanced options grub menu. You must have used that to get into recovery mode.

7

Tried but no luck.

photo_2026-08-09_18-38-49
photo_2026-08-09_18-38-49960×1280 57.9 KB

How could I reinstall it? I tried with the usb and after clicking on try Zorin and restarting it got stuck on the logo again.

8

This is what brave ai said about failed rsyslog. Some of it may be useful but the issue you are having is not one I've experienced personally so obviously cannot vouch for any of it. Use at your own risk, I'm thinking the last paragraph about reinstalling a corrupted package might be low risk and worth trying.

Also see what others may suggest.

The failed to start rsyslog.service error typically stems from configuration conflicts, excessive log file handles, or service dependency issues. Common causes include logrotate triggering rapid restarts , too many open journal files , or missing systemd dependencies .

Resolution Steps

  1. Check Logrotate Conflicts : If logrotate scripts restart rsyslog too frequently, systemd may timeout. Add sharedscripts to the relevant files in /etc/logrotate.d/ to prevent multiple restarts per rotation cycle.
  2. Increase File Handles : If the system has too many journal files, rsyslog may fail to open them. Edit /etc/rsyslog.conf to add $MaxOpenFiles 4096 under Global Directives, then run systemctl daemon-reload and systemctl restart rsyslog . Alternatively, vacuum old journals using journalctl --vacuum-time='3 weeks' .
  3. Resolve PID Conflicts : On Debian/Ubuntu, ensure no duplicate processes exist. Stop both units with systemctl stop syslog.socket rsyslog.service , remove stale PID files in /var/run/ if necessary, and restart. You may also need to add the -iNONE flag to the rsyslogd ExecStart directive to prevent PID file writing issues.
  4. Verify Configuration Integrity : Check for syntax errors in /etc/rsyslog.conf using rsyslogd -N1 . If compatibility mode is used, ensure SYSLOGD_OPTIONS is set correctly, as older modes can cause failures in RHEL 8+.
  5. Reinstall Package : If the service file is missing or corrupted, reinstall the package using yum reinstall rsyslog (RHEL/CentOS) or apt-get install --reinstall rsyslog (Debian/Ubuntu).

If the issue persists, check specific logs with journalctl -xe or systemctl status rsyslog.service for detailed error codes