Has something been changed in Zorin 18 r1 iso so that Wayland can't be enabled in live session? In the first version of Zorin 18 and Zorin 18 beta it was possible to use Wayland in live session. When I tried today to switch to Wayland by editing /etc/gdm3/custom.conf and uncommeting WaylandEnable=false or setting it to true, it didn't work.
It stayed at XOrg after logout and login again.
And when I enter echo XDG_SESSION_TYPE in terminal then the output is XDG_SESSION_TYPE - not as before and usual Wayland or X11.
What can be done to use Wayland in live session? I sometimes want to check something for other users or want to reproduce errors and therefore it would be practical.
Have you tried the same with Z18 Core r2 which is now available to download?
I don't know what the devs changed from r1 to r2.
There seems to be no announcement of r2 on forum by @AZorin or @zorink
Not yet, I would have to download r2.iso first and put it on my stick. But I read that there is a new .iso but I don't know what has been changed from r1 to r2.
Ah, I just noticed that I forgot to enter the command
sudo systemctl restart gdm3
I hadn't needed to switch to Wayland for some time and had therefore forgotten that it is neccessary to execute this command and that simply logging out doesn't work.
Now Wayland works.
I downloaded the r2 .iso and experienced two system crashes in the live session yesterday: One with showing 'Something has gone wrong' without the option to log out, and I had to shut down the laptop hard. The other time was after a time where I had left the laptop behind, when endless white text appeared on a black background, indicating that the page could not be displayed. I had to pull the plug too.
I don't know if my boot stick is broken now, but as far as I can tell, r2 is not a real improvement. This has never happened to me before with other versions of Zorin 18 live session.
Today again a crash with wayland and r2 .iso in Zorin 18 live session after suspend. I wanted to shutdown my computer and clicked in startmenu on the button for shutdown. A message appears similar to "Failed to start show plymouth poweroff screen" and then an endless white written list with always the same errors appeared on black background and I had to press the power off button long time to hard shut down.
Is the .iso or stick broken? Yesterday it was the same. Would it help to remove splash at boot or not to make the plymouth update?
Your post #5 is marked as Solution.
Maybe that is deflecting further attention to this thread, so suggest you consider removing that flag if your Z18 Live USB issues continue.
I wanted to switch to lightdm in Zorin 18 live session for testing purposes with customizing login screen.
I installed lightdm, lightdm-gtk-greeter and lightdm-gtk-greeter-settings and reconfigured lightdm, but with the default zorin live session user with automatic login I was not able to login and got stuck in a login loop.
After I created a new user account with password login the login worked.
Why does this happen? Can something be changed that it also works without creating a new account? It seems not to work with automatic login and this can't be changed for live session user account.
I would also be interested in how to go back to gdm3. It was not possible, I always got a black screen after I reconfigured lightdm to gdm3 ('sudo dpkg-reconfigure lightdm' and selected gdm3 there) and ran 'sudo systemctl restart gdm3'.
Does this mean the commands were right? I thought it always worked this way when I did the same on my Zorin 17 virtual machine. But now I'm not sure if I made something wrong.
Won't the stick break down faster with persistence? It's a pretty big stick with over 60 GiB, and I'm currently using it every day to answer questions about Zorin 18. It would be a shame if it broke down because of that. But the frequent crashes lately, which required me to turn off the power and shut down hard, aren't so good in the long run either...
The Zorin OS 18 r2 revised isos were released shortly after the r1 isos, primarily to include a more robust fix for the E:Sub-process /usr/bin/dpkg returned an error code (1) error while installing Zorin OS 18 when the "modern NVIDIA drivers" option was enabled and newer Linux kernel versions are available.
When we release revised sets of isos we usually include a suffix (like -r2) to the file names of the free editions of Zorin OS. We do this in case there are any issues with deleting/overwriting the old iso files on some of the free mirror servers, which are run by third-parties like universities and organisations around the world.
As they can't store multiple files with the same name in the same directory, we need to differentiate them on the mirror servers by changing the names of the new isos, which we do by appending the "-rX" suffix.
However, as the Pro edition iso files are hosted on servers administrated by us, we can safely overwrite the older iso files with the newer revised isos there. As a result, we typically don't change the file name for the Pro edition iso files in order to maintain continuity and to avoid hosting multiple old & redundant files.
I can see the point of that for keeping a minimum of server files, but for users that download an .iso for backup purposes, they will not know if they have the initial or r1 or r2 version of Pro. They could also be upset when a recent downloaded .iso fails to compare against the SHA256 they initially saved for Z18 Pro. They may then think they have a corrupt download file again and again for the wrong reason.
I am personally unhappy with version control of Pro in this respect. I have witnessed total software chaos caused by software version mis-labelling in the past, i.e. different versions with same label, hence I flagged my concern.
I'm still having problems in the live session of r2 .iso where the Gnome session crashes, even under Xorg. Today, after resuming the session from hibernation, I got an ibus (or dbus? I'm not relly sure) error in the terminal when I tried to install an app. When I then tried to log out, everything crashed, black screen with endless terminal output.
Oh, I meant suspend, not hibernation, that was wrong translated by the translator tool. Since I didn't have any such session interruptions for two months before, but now it happens almost daily since I started using the r2 .iso, I will probably go back to using an older Zorin 18 .iso.
3 days without gnome-session crashing on my Zorin-18-Live-boot-stick !!!
That hasn't happened the last weeks.
After boot I uninstalled folder-color and disabled almost all pre-installed Gnome extensions except for Zorin menu and Zorin taskbar.
I will continue to monitor whether this completely fixes the crashes.
Perhaps the culprit can be identified more precisely.
Solution.