I understand that. My point, and what I was reporting to the developers, was that the driver thing didn't apply to when I got the "Oops. Something went wrong" message, so there is not just one problem.
1 Like
And now, on Startup, I've one of (1) Oops and frozen screen, (2) BIOS, or (3) Zorin with the right background, wrong display and no items on the desktop.
Edit. When in option 3, I've discovered that, if I click on the horizontal grey bar in the Taskbar that moves the window, I can get back to my chosen layout and apps on desktop. Bizarre!
Edit 2. Each time on boot, it puts up the wrong layout (No. 2) with the correct background, then changes to the correct layout no. 3. Bizarre again
I just tried to update a newly created (updated) VM that has full disk encryption and it wouldn't even try to perform the update. It did the pre-checks, and gave me this report:
[CHECKING] Started
[CHECKING:Validating Upgrade Attempt] Started
[CHECKING:Validating Upgrade Attempt] Completed
[CHECKING:Checking Filesystem] Started
[CHECKING:Checking Filesystem] Completed
[CHECKING:Restarting Apt] Started
[CHECKING:Restarting Apt] Completed
[CHECKING:Simulating Flatpak Transaction] Started
[CHECKING:Simulating Flatpak Transaction] Completed
[CHECKING:Processing Apt Repos] Started
[CHECKING:Processing Apt Repos] Completed
[CHECKING:Updating Apt Repos] Started
[CHECKING:Updating Apt Repos] Completed
[CHECKING:Calculating Upgradeable Packages] Started
[CHECKING:Calculating Upgradeable Packages] Fatal Error: { GDBus.Error:org.aptkit.TransactionFailed: error-dep-resolution-failed: E:Internal Error, pkgProblemResolver::ResolveByKeep is looping on package libsane1:amd64. }
[CHECKING:Calculating Upgradeable Packages] Failed
[CHECKING] Failed
[CHECKING:Restoring System] Started
[CHECKING:Restoring System] Completed
Of course, i sent the report via the dialogue box.
It seems to have a Problem with the Package libsane1:amd64
I have also tried the update on a system (another VM) where the /home/user directory is encrypted with ecryptfs.
It seems to get stuck on "installing the upgrades". It's been sitting there for over 45 minutes. I had to leave (and shut down the host), so i don't know if it would have completed had i left it there much longer.
EDIT: It did eventually finish. I can't say how long it took, but it was a long time. But...
"Oh no! something has gone wrong".
Man, this upgrade process has failed on me 4 of 4 attempts, on different VMs with different setups (2 setups just vanilla in the early days of the upgrade availability).
I'll be blunt - all this goes to support my and others' assertion that Zorin OS should just dump Ubuntu and move to Debian as the base. Period. Ubuntu is NOT the same as it was before. Period again. Just move to Debian for Zorin OS 19, and slap on the same GNOME environment (with bugfixes and whatnot). Call it a day then.
I don't mind the failed updates in 'testing'. Though i must say that 4 out of 4 is not so fun. It would be nice to see more visible solution communication. That error is not at all helpful. Perhaps it should say "press alt-F2 and enter this command: sudo help!.sh or something 
.. especially as Timeshift is a thing - include a script in the update that allows the user to hit alt-F2 and enter save-me.sh.
To your point about Debian, Mint hasn't moved yet, but they do produce a Debian-based version. I wonder how much of Ubuntu they have to unwind, and how that would compare to how much they have to add to Debian. I suspect a problem they would face is the small development team. They'd have to spend a long time on a Debian version, and possibly support a 'Debian edition' at the same time as the Ubuntu-based version at least for a while. I doubt they have the capacity, especially as they're working on Grid, which is due for release around the same time as Star Citizen (i'm joking guys, just enjoy it 
).
1 Like
Do we know if it's worth doing some more testing? I don't want to spend time setting up and breaking something if the improvements haven't yet been inbuilt.