Zorin-OS V17.2 fails to boot after successful installation on my HP EliteBook 8470p Notebook.
I have successfully installed the same ISO image on several other HP notebooks without any issues.
If I manually set the boot device to "Boot From EFI File" using the F9 key, I can select the file system, then Ubuntu, and finally grubx64.efi. After that, Zorin-OS starts without any problems.
Unfortunately, after a restart, Zorin-OS is not automatically detected by the system and must always be started manually using F9.
It seems to me that the boot sector cannot be saved persistently.
Can someone please tell me how to configure Zorin-OS to start automatically after a restart?
Switch to Xorg (logout and at login click on your username then a cog wheal appears at the bottom right corner. There select "Zorin Desktop on Xorg").
You can launch the browsers from terminal with disabled hardware acceleration, if it helps, disable hardware acceleration in the browser settings.
brave-browser --disable-gpu
google-chrome --disable-gpu
For flatpak versions of the browsers you would need other commands, these ones are only for .deb/apt packages.
If it now works properly, you do not need to disable hardware acceleration.
Unfortunately, the problem still exists in Zorin 18. Wayland is not yet well implemented and still causes many problems. However, switching to XOrg is usually enough to fix it, especially with older hardware that does not run well under Wayland.
If you want to use Wayland, you could set the ozone platform wayland in your browser, which often also fixes the problems.
But in your case, with your somewhat older notebook, you're probably better off with XOrg.
Yes, with switching to XOrg at login Wayland is no longer used - until you change it at login and select the normal Wayland session.
Unfortunately, the Zorin group wants to use Wayland as default. It has been suggested many times to change this default setting to Xorg because it causes so much problems.
Thank you very much for your detailed explanation.
I will continue using this old racket from 2012 without Wayland. Thanks to Zorin-OS, it can continue to function for a while longer.
I have one last question before I close this topic.
During my last installation of Zorin-OS 17.3, I noticed that the remote management software RustDesk (under Wayland) exhibits the following malfunction:
If the client computer being controlled has fractional scaling set to > 100%, the Zorin start menu can no longer be accessed by the RustDesk master user.
Have you also encountered this bug, and if not, where should I report it?
I'm not familar with this problem. If my research is correct, this problem has existed for some time under Wayland and rustdesk. It looks like an update could now provide improved Wayland support. However, I don't know how quickly it will be available on Zorin 17, or if it will be available at all.
Thats one of the things that bothers me, its been suggested many times, and many times ignored. I just don't understand the whole, "we know better then you" attitude. Unfortunately, there are gaming dev's that do the same thing, won't take feedback, and think their way is best, drives me insane!
