Just backed up my system then tried the "Upgrade Zorin OS" from Z15.3 Core to Z16.2 Core.
Unfortunately it failed with this:
[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.debian.apt.TransactionFailed: error-dep-resolution-failed: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. }
[CHECKING:Calculating Upgradeable Packages] Failed
[CHECKING] Failed
[CHECKING:Restoring System] Started
[CHECKING:Restoring System] Completed
The report has been sent to devs, so I hope there may be a solution.
Related to screen resolution ?
So now, despite you got an error, did the procedure restore your usual system status or break it?
It may not be display related, but rather dependency related, especially since the rest of the error describes held packages.
3 Likes
Screen resolution is nothing special its a common laptop screen resolution setting and a default for Z15.3. I don't think failure has anything to do with that.
The upgrader returned to system as before, except Installed Software shown by Software Store was incorrect. That was fixed by a re-boot and re-enter the Software Store where Installed software was then re-populated correctly.
1 Like
I have checked for any broken installs using Synaptic PM, but find none. So I have no idea of "held packages".
Also, I made sure Software was updated before using Zorin OS Upgrader.
The command apt-mark showhold
should show any packages held back.
Can you check if you have a /var/log/dist-upgrade/apt.log
file?
cat /var/log/dist-upgrade/apt.log
Yes I have.
(@Aravisian Do you think maybe best to split this thread, from my post #69 , to a new thread in General Help for my specific issue?)
Please feel free to edit the title...
zabadabadoo:
Yes I have.
Is it populated with any packages?
Entries are old circa 2020. This is the full extent of the log file.
Log time: 2020-06-15 17:29:48.160512
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) fwupd-signed:amd64 < 1.10~ubuntu18.04.3+1.2.10-1ubuntu2~ubuntu18.04.3 @ii mK Ib >
Broken fwupd-signed:amd64 Depends on fwupd:amd64 < 1.2.10-1ubuntu2~ubuntu18.04.3 -> 1.2.10-1ubuntu2~ubuntu18.04.5 @ii umU > (= 1.2.10-1ubuntu2~ubuntu18.04.3)
Considering fwupd:amd64 5 as a solution to fwupd-signed:amd64 5
Removing fwupd-signed:amd64 rather than change fwupd:amd64
Investigating (0) fwupdate-signed:amd64 < 12-7~ubuntu18.04.3 @ii mK Ib >
Broken fwupdate-signed:amd64 Depends on fwupd-signed:amd64 < 1.10~ubuntu18.04.3+1.2.10-1ubuntu2~ubuntu18.04.3 @ii mR >
Considering fwupd-signed:amd64 5 as a solution to fwupdate-signed:amd64 1
Removing fwupdate-signed:amd64 rather than change fwupd-signed:amd64
Done
Log time: 2020-06-15 17:32:01.998629
MarkPurge mypaint-brushes:amd64 < 1.3.0-1 @ii gK > FU=1
MarkPurge libsdl1.2debian:amd64 < 1.2.15+dfsg2-0.1ubuntu0.1 @ii gK > FU=1
MarkPurge libvisio-0.1-1:amd64 < 0.1.6-1build1 @ii gK > FU=1
MarkPurge libheif1:amd64 < 1.1.0-2 @ii gK > FU=1
MarkPurge libmspub-0.1-1:amd64 < 0.1.4-1 @iLog time: 2020-06-15 17:29:48.160512
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) fwupd-signed:amd64 < 1.10~ubuntu18.04.3+1.2.10-1ubuntu2~ubuntu18.04.3 @ii mK Ib >
Broken fwupd-signed:amd64 Depends on fwupd:amd64 < 1.2.10-1ubuntu2~ubuntu18.04.3 -> 1.2.10-1ubuntu2~ubuntu18.04.5 @ii umU > (= 1.2.10-1ubuntu2~ubuntu18.04.3)
Considering fwupd:amd64 5 as a solution to fwupd-signed:amd64 5
Removing fwupd-signed:amd64 rather than change fwupd:amd64
Investigating (0) fwupdate-signed:amd64 < 12-7~ubuntu18.04.3 @ii mK Ib >
Broken fwupdate-signed:amd64 Depends on fwupd-signed:amd64 < 1.10~ubuntu18.04.3+1.2.10-1ubuntu2~ubuntu18.04.3 @ii mR >
Considering fwupd-signed:amd64 5 as a solution to fwupdate-signed:amd64 1
Removing fwupdate-signed:amd64 rather than change fwupd-signed:amd64
Done
Log time: 2020-06-15 17:32:01.998629
MarkPurge mypaint-brushes:amd64 < 1.3.0-1 @ii gK > FU=1
MarkPurge libsdl1.2debian:amd64 < 1.2.15+dfsg2-0.1ubuntu0.1 @ii gK > FU=1
MarkPurge libvisio-0.1-1:amd64 < 0.1.6-1build1 @ii gK > FU=1
MarkPurge libheif1:amd64 < 1.1.0-2 @ii gK > FU=1
MarkPurge libmspub-0.1-1:amd64 < 0.1.4-1 @ii gK > FU=1
MarkPurge libcmis-0.5-5v5:amd64 < 0.5.1+git20160603-3build2 @ii gK > FU=1
MarkPurge libllvm7:amd64 < 1:7-3~ubuntu0.18.04.1 @ii gK > FU=1
MarkPurge libe-book-0.1-1:amd64 < 0.1.3-1 @ii gK > FU=1
MarkPurge libepubgen-0.1-1:amd64 < 0.1.0-2ubuntu1 @ii gK > FU=1
MarkPurge libodfgen-0.1-1:amd64 < 0.1.6-2 @ii gK > FU=1
MarkPurge libeot0:amd64 < 0.01-5 @ii gK > FU=1
MarkPurge libcdr-0.1-1:amd64 < 0.1.4-1build1 @ii gK > FU=1
MarkPurge librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii gK > FU=1
Starting pkgProblemResolver with broken count: 6
Starting 2 pkgProblemResolver with broken count: 6
Investigating (0) libwpd-0.10-10:amd64 < 0.10.2-2 @ii gK Ib >
Broken libwpd-0.10-10:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libwpd-0.10-10:amd64 1
Removing libwpd-0.10-10:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libwpd-0.10-10:amd64 < 0.10.2-2 @ii gK Ib > FU=0
Investigating (0) libmwaw-0.3-3:amd64 < 0.3.13-1 @ii gK Ib >
Broken libmwaw-0.3-3:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libmwaw-0.3-3:amd64 0
Removing libmwaw-0.3-3:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libmwaw-0.3-3:amd64 < 0.3.13-1 @ii gK Ib > FU=0
Investigating (0) libfreehand-0.1-1:amd64 < 0.1.2-2 @ii gK Ib >
Broken libfreehand-0.1-1:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libfreehand-0.1-1:amd64 0
Removing libfreehand-0.1-1:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libfreehand-0.1-1:amd64 < 0.1.2-2 @ii gK Ib > FU=0
Investigating (0) libabw-0.1-1:amd64 < 0.1.2-1ubuntu1 @ii gK Ib >
Broken libabw-0.1-1:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libabw-0.1-1:amd64 0
Removing libabw-0.1-1:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libabw-0.1-1:amd64 < 0.1.2-1ubuntu1 @ii gK Ib > FU=0
Investigating (0) libpagemaker-0.0-0:amd64 < 0.0.4-1 @ii gK Ib >
Broken libpagemaker-0.0-0:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libpagemaker-0.0-0:amd64 0
Removing libpagemaker-0.0-0:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libpagemaker-0.0-0:amd64 < 0.0.4-1 @ii gK Ib > FU=0
Investigating (0) libwpg-0.3-3:amd64 < 0.3.1-3 @ii gK Ib >
Broken libwpg-0.3-3:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libwpg-0.3-3:amd64 0
Removing libwpg-0.3-3:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libwpg-0.3-3:amd64 < 0.3.1-3 @ii gK Ib > FU=0
Done
MarkPurge libllvm8:amd64 < 1:8-3~ubuntu18.04.2 @ii gK > FU=1
MarkPurge efibootmgr:amd64 < 15-1 @ii gK > FU=1
MarkPurge secureboot-db:amd64 < 1.4~ubuntu0.18.04.1 @ii gK > FU=1
MarkPurge libfwup1:amd64 < 12-3bionic2 @ii gK > FU=1
MarkPurge libabw-0.1-1:amd64 < 0.1.2-1ubuntu1 @ii gP > FU=1
MarkPurge libwpd-0.10-10:amd64 < 0.10.2-2 @ii gP > FU=1
MarkPurge libfreehand-0.1-1:amd64 < 0.1.2-2 @ii gP > FU=1
MarkPurge libllvm8:i386 < 1:8-3~ubuntu18.04.2 @ii gK > FU=1
MarkPurge libclamav7:amd64 < 0.100.3+dfsg-0ubuntu0.18.04.1 @ii gK > FU=1
MarkPurge libpagemaker-0.0-0:amd64 < 0.0.4-1 @ii gP > FU=1
MarkPurge libwpg-0.3-3:amd64 < 0.3.1-3 @ii gP > FU=1
MarkPurge sbsigntool:amd64 < 0.6-3.2ubuntu2 @ii gK > FU=1
MarkPurge libmwaw-0.3-3:amd64 < 0.3.13-1 @ii gP > FU=1i gK > FU=1
MarkPurge libcmis-0.5-5v5:amd64 < 0.5.1+git20160603-3build2 @ii gK > FU=1
MarkPurge libllvm7:amd64 < 1:7-3~ubuntu0.18.04.1 @ii gK > FU=1
MarkPurge libe-book-0.1-1:amd64 < 0.1.3-1 @ii gK > FU=1
MarkPurge libepubgen-0.1-1:amd64 < 0.1.0-2ubuntu1 @ii gK > FU=1
MarkPurge libodfgen-0.1-1:amd64 < 0.1.6-2 @ii gK > FU=1
MarkPurge libeot0:amd64 < 0.01-5 @ii gK > FU=1
MarkPurge libcdr-0.1-1:amd64 < 0.1.4-1build1 @ii gK > FU=1
MarkPurge librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii gK > FU=1
Starting pkgProblemResolver with broken count: 6
Starting 2 pkgProblemResolver with broken count: 6
Investigating (0) libwpd-0.10-10:amd64 < 0.10.2-2 @ii gK Ib >
Broken libwpd-0.10-10:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libwpd-0.10-10:amd64 1
Removing libwpd-0.10-10:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libwpd-0.10-10:amd64 < 0.10.2-2 @ii gK Ib > FU=0
Investigating (0) libmwaw-0.3-3:amd64 < 0.3.13-1 @ii gK Ib >
Broken libmwaw-0.3-3:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libmwaw-0.3-3:amd64 0
Removing libmwaw-0.3-3:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libmwaw-0.3-3:amd64 < 0.3.13-1 @ii gK Ib > FU=0
Investigating (0) libfreehand-0.1-1:amd64 < 0.1.2-2 @ii gK Ib >
Broken libfreehand-0.1-1:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libfreehand-0.1-1:amd64 0
Removing libfreehand-0.1-1:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libfreehand-0.1-1:amd64 < 0.1.2-2 @ii gK Ib > FU=0
Investigating (0) libabw-0.1-1:amd64 < 0.1.2-1ubuntu1 @ii gK Ib >
Broken libabw-0.1-1:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libabw-0.1-1:amd64 0
Removing libabw-0.1-1:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libabw-0.1-1:amd64 < 0.1.2-1ubuntu1 @ii gK Ib > FU=0
Investigating (0) libpagemaker-0.0-0:amd64 < 0.0.4-1 @ii gK Ib >
Broken libpagemaker-0.0-0:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libpagemaker-0.0-0:amd64 0
Removing libpagemaker-0.0-0:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libpagemaker-0.0-0:amd64 < 0.0.4-1 @ii gK Ib > FU=0
Investigating (0) libwpg-0.3-3:amd64 < 0.3.1-3 @ii gK Ib >
Broken libwpg-0.3-3:amd64 Depends on librevenge-0.0-0:amd64 < 0.0.4-6ubuntu2 @ii pgP >
Considering librevenge-0.0-0:amd64 10006 as a solution to libwpg-0.3-3:amd64 0
Removing libwpg-0.3-3:amd64 rather than change librevenge-0.0-0:amd64
MarkDelete libwpg-0.3-3:amd64 < 0.3.1-3 @ii gK Ib > FU=0
Done
MarkPurge libllvm8:amd64 < 1:8-3~ubuntu18.04.2 @ii gK > FU=1
MarkPurge efibootmgr:amd64 < 15-1 @ii gK > FU=1
MarkPurge secureboot-db:amd64 < 1.4~ubuntu0.18.04.1 @ii gK > FU=1
MarkPurge libfwup1:amd64 < 12-3bionic2 @ii gK > FU=1
MarkPurge libabw-0.1-1:amd64 < 0.1.2-1ubuntu1 @ii gP > FU=1
MarkPurge libwpd-0.10-10:amd64 < 0.10.2-2 @ii gP > FU=1
MarkPurge libfreehand-0.1-1:amd64 < 0.1.2-2 @ii gP > FU=1
MarkPurge libllvm8:i386 < 1:8-3~ubuntu18.04.2 @ii gK > FU=1
MarkPurge libclamav7:amd64 < 0.100.3+dfsg-0ubuntu0.18.04.1 @ii gK > FU=1
MarkPurge libpagemaker-0.0-0:amd64 < 0.0.4-1 @ii gP > FU=1
MarkPurge libwpg-0.3-3:amd64 < 0.3.1-3 @ii gP > FU=1
MarkPurge sbsigntool:amd64 < 0.6-3.2ubuntu2 @ii gK > FU=1
MarkPurge libmwaw-0.3-3:amd64 < 0.3.13-1 @ii gP > FU=1
It looks like librevenge is getting its vengeance.
Have these broken packages been resolved?
I have no idea what they are related to.
As I said above, Synaptic shows nothing broken. I have no Software that I use that is not working properly.
Let's try:
sudo apt remove libmwaw libfreehand libpagemaker libabw libwpd fwupdate-signed:amd64
We can be bold, since they are listed as broken, anyway.
If it shows that they remove, reboot and try testing the upgrader again.
OK. I will report back.
First I am going to check those 2020 dates in log against what I was doing on the machine at that time i.e. software or OS updates.
EDIT: The log events dated 15 June 2020 coincide with OS Update to Z15.2 Core 64bit. I don't know if that is significant.
Since then it has been updated to Z15.3 Core 64bit.
EDIT2: I have looked on Synaptic for those items.
libmaw
libfreehand
libpagemaker
libabw
libwpd
are NOT shown as Installed (i.e. just listed available for installation if wanted)
fwupdate
is a a bit more tricky. A "transitional package" is installed but signed one is not. See screenshot.
I assume this relates to GUFW, which as far as I can see is on and working.
I don't really want to break my working Z15.3 system, but equally would like to upgrade without pain of reconfiguration. I tested Z16.2 Core Live USB yesterday and after some faffing with Alsamixer I did get sound to work.
2 Likes
@zabadabadoo
What does the terminal command
sudo dpkg --remove --pending
output?
Ok, so is the Upgrade issue abandoned? (EDIT - This question was in response to a post that is now merged into a new thread).
Thread closed due to O.P. moving on to a full reinstall.
Thread contents must be reviewed for feedback of Zorin Upgrader.
Aravisian
Split this topic
25 July 2023 13:25
20