pckon is driving me mad by telling me over and over again about unmet dependencies, but when I try to install those packages I am told they are installed already.
Below you’ll find an example. (I used “LC_ALL=C” to make the system speak English temporally.)
I can take whatever package I want from the list of recommendations, but the result will always be same: those packages are installed already, ‘dpkg’ will list their contents and ‘ls’ will show those files as existent. My plasma desktop is up and running, until now I have not experienced any crash due to missing files.
How do I solve this misery?
Thanks in advance for any help!
root@pc:~# LC_ALL=C pkcon update
Getting updates [=========================]
Finished [=========================]
Loading cache [=========================]
Testing changes [=========================]
Finished [=========================]
Fatal error: The following packages have unmet dependencies:
neon-desktop: Depends: kde-cli-tools but it is not going to be installed
Depends: kinfocenter but it is not going to be installed
Depends: kio but it is not going to be installed
Depends: kwin-wayland but it is not going to be installed
Depends: kwin-x11 but it is not going to be installed
Depends: sddm-theme-breeze but it is not going to be installed
Recommends: dolphin but it is not going to be installed
Recommends: dolphin-plugins but it is not going to be installed
Recommends: frameworkintegration but it is not going to be installed
Recommends: hplip but it is not going to be installed
Recommends: kde-config-plymouth but it is not going to be installed
Recommends: kdeconnect but it is not going to be installed
Recommends: kio-gdrive but it is not going to be installed
Recommends: konsole but it is not going to be installed
Recommends: kscreen but it is not going to be installed
Recommends: ksshaskpass but it is not going to be installed
Recommends: kwin-addons but it is not going to be installed
Recommends: kwrite but it is not going to be installed
Recommends: linux-generic-hwe-22.04 but it is not going to be installed
Recommends: neon-adwaita but it is not going to be installed
Recommends: okular but it is not going to be installed
Recommends: plasma-discover but it is not going to be installed
Recommends: plasma-firewall but it is not going to be installed
Recommends: plasma-nm but it is not going to be installed
Recommends: plasma-systemmonitor but it is not going to be installed
Recommends: plasma-welcome but it is not going to be installed
Recommends: plasma-widgets-addons but it is not going to be installed
Recommends: plasma-workspace-wayland but it is not going to be installed
Recommends: plymouth-theme-breeze but it is not going to be installed
Recommends: snapd but it is not going to be installed
kwalletmanager: Depends: libkf5wallet5 but it is not going to be installed
plasma-desktop: Depends: kde-cli-tools (>= 4:5.14) but it is not going to be installed
Depends: kio but it is not going to be installed
Depends: plasma-workspace (>= 4:5.14) but it is not going to be installed
Depends: libkf5newstuffcore5 but it is not going to be installed
Recommends: khelpcenter but it is not going to be installed
Recommends: kinfocenter (>= 4:5.14) but it is not going to be installed
Recommends: kscreen (>= 4:5.14) but it is not going to be installed
Recommends: ksshaskpass (>= 4:5.14) but it is not going to be installed
Recommends: kwin-x11 (>= 4:5.14) but it is not going to be installed or
kwin
Recommends: plasma-discover (>= 5.14) but it is not going to be installed
root@pc:~# LC_ALL=C pkcon install kde-cli-tools
Resolving [=========================] Package not found: kde-cli-tools
[=========================] Command failed: The selected packages may already be installed.
root@pc:~# LC_ALL=C apt install kde-cli-tools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
kde-cli-tools is already the newest version (4:5.27.7-0xneon+22.04+jammy+release+build30).
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
root@pc:~# LC_ALL=c dpkg -L kde-cli-tools
/.
/usr
/usr/bin
/usr/bin/kbroadcastnotification
/usr/bin/kcmshell5
/usr/bin/kde-inhibit
/usr/bin/kde-open
/usr/bin/kdecp
/usr/bin/kdemv
/usr/bin/keditfiletype
/usr/bin/kinfo
/usr/bin/kioclient
/usr/bin/kmimetypefinder
/usr/bin/kstart
/usr/bin/ksvgtopng
/usr/bin/ktraderclient5
/usr/bin/plasma-open-settings
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libexec
/usr/lib/x86_64-linux-gnu/libexec/kf5
/usr/lib/x86_64-linux-gnu/libexec/kf5/kdeeject
/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu
/usr/lib/x86_64-linux-gnu/qt5
/usr/lib/x86_64-linux-gnu/qt5/plugins
/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma
/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms
/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings_qwidgets
/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings_qwidgets/kcm_filetypes.so
/usr/share
/usr/share/applications
/usr/share/applications/kcm_filetypes.desktop
/usr/share/applications/org.kde.keditfiletype.desktop
/usr/share/applications/org.kde.plasma.settings.open.desktop
/usr/share/doc
/usr/share/doc/kde-cli-tools
/usr/share/doc/kde-cli-tools/changelog.Debian.gz
/usr/share/doc/kde-cli-tools/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/kde-cli-tools
/usr/bin/kde-open5
/usr/bin/kdecp5
/usr/bin/kdemv5
/usr/bin/keditfiletype5
/usr/bin/kioclient5
/usr/bin/kmimetypefinder5
/usr/bin/kstart5
/usr/bin/ksvgtopng5
root@pc:~# ls -alF /usr/bin/kbroadcastnotification
-rwxr-xr-x 1 root root 26848 Aug 2 12:14 /usr/bin/kbroadcastnotification*
Well, here’s what apt has to say about this issue. It’s basically the same errors that pkcon emits. I can not make sense of all those “fixing”, “adding” and “repairing” messages, because they appear each time I run this command. How many times do these packages need to be added, fixed and repaired??
Furthermore, I never set any packages to be held back, and I never switched the machine off just using the main switch and thus killing a possible maintenance of apt’s database. (Last time I had to use the power switch was over 20 years ago! )
And finally, smartmond says nothing about hard drive failures.
So, my guess is that the repository of KDE Neon contains some wrong packages dependencies. But I am open to suggestions how to fix my system.
> apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 2
Starting 2 pkgProblemResolver with broken count: 2
Investigating (0) libkf5wallet5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 @ii mK Ib >
Broken libkf5wallet5:amd64 Depends on libkf5wallet-data:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 -> 5.109.0-0xneon+22.04+jammy+release+build34 @ii umU > (= 5.108.0-0xneon+22.04+jammy+release+build32)
Considering libkf5wallet-data:amd64 15 as a solution to libkf5wallet5:amd64 52
Added libkf5wallet-data:amd64 to the remove list
Fixing libkf5wallet5:amd64 via keep of libkf5wallet-data:amd64
Investigating (0) libkwalletbackend5-5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 @ii mK Ib >
Broken libkwalletbackend5-5:amd64 Depends on libgpgmepp6:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 -> 1.16.0-1.2ubuntu4.1 @ii mD > (>= 1.20.0)
Considering libgpgmepp6:amd64 1 as a solution to libkwalletbackend5-5:amd64 16
Added libgpgmepp6:amd64 to the remove list
Fixing libkwalletbackend5-5:amd64 via keep of libgpgmepp6:amd64
Try to Re-Instate (0) libkf5wallet-data:amd64
Try to Re-Instate (0) libgpgmepp6:amd64
Re-Instated libgpgmepp6:amd64 (1 vs 1)
Investigating (1) libkwalletbackend5-5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 @ii mK Ib >
Broken libkwalletbackend5-5:amd64 Depends on libgpgmepp6:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 -> 1.16.0-1.2ubuntu4.1 @ii mD > (>= 1.20.0)
Considering libgpgmepp6:amd64 1 as a solution to libkwalletbackend5-5:amd64 16
Added libgpgmepp6:amd64 to the remove list
Fixing libkwalletbackend5-5:amd64 via keep of libgpgmepp6:amd64
Investigating (1) libgpgmepp6:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 | 1.16.0-1.2ubuntu4.1 @ii mH Ib >
Broken libgpgmepp6:amd64 Depends on libgpgme11:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 -> 1.16.0-1.2ubuntu4.1 @ii mD > (>= 1.20.0)
Considering libgpgme11:amd64 17 as a solution to libgpgmepp6:amd64 1
Removing libgpgmepp6:amd64 rather than change libgpgme11:amd64
Investigating (2) libkwalletbackend5-5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 @ii mK Ib >
Broken libkwalletbackend5-5:amd64 Depends on libgpgmepp6:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 | 1.16.0-1.2ubuntu4.1 @ii mR > (>= 1.20.0)
Considering libgpgmepp6:amd64 1 as a solution to libkwalletbackend5-5:amd64 16
Added libgpgmepp6:amd64 to the remove list
Fixing libkwalletbackend5-5:amd64 via keep of libgpgmepp6:amd64
Investigating (2) libgpgmepp6:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 | 1.16.0-1.2ubuntu4.1 @ii mH Ib >
Broken libgpgmepp6:amd64 Depends on libgpgme11:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 -> 1.16.0-1.2ubuntu4.1 @ii mD > (>= 1.20.0)
Considering libgpgme11:amd64 17 as a solution to libgpgmepp6:amd64 16
Removing libgpgmepp6:amd64 rather than change libgpgme11:amd64
Investigating (3) libkwalletbackend5-5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 @ii mK Ib >
Broken libkwalletbackend5-5:amd64 Depends on libgpgmepp6:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 | 1.16.0-1.2ubuntu4.1 @ii mR > (>= 1.20.0)
Considering libgpgmepp6:amd64 17 as a solution to libkwalletbackend5-5:amd64 16
Removing libkwalletbackend5-5:amd64 rather than change libgpgmepp6:amd64
Investigating (4) libkf5wallet5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 @ii mK Ib >
Broken libkf5wallet5:amd64 Depends on libkwalletbackend5-5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 @ii mR > (= 5.108.0-0xneon+22.04+jammy+release+build32)
Considering libkwalletbackend5-5:amd64 17 as a solution to libkf5wallet5:amd64 52
Added libkwalletbackend5-5:amd64 to the remove list
Fixing libkf5wallet5:amd64 via keep of libkwalletbackend5-5:amd64
Investigating (4) libkwalletbackend5-5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 @ii mK Ib >
Broken libkwalletbackend5-5:amd64 Depends on libgpgmepp6:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 | 1.16.0-1.2ubuntu4.1 @ii mR > (>= 1.20.0)
Considering libgpgmepp6:amd64 17 as a solution to libkwalletbackend5-5:amd64 52
Added libgpgmepp6:amd64 to the remove list
Fixing libkwalletbackend5-5:amd64 via keep of libgpgmepp6:amd64
Investigating (4) libgpgmepp6:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 | 1.16.0-1.2ubuntu4.1 @ii mH Ib >
Broken libgpgmepp6:amd64 Depends on libgpgme11:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 -> 1.16.0-1.2ubuntu4.1 @ii mD > (>= 1.20.0)
Considering libgpgme11:amd64 17 as a solution to libgpgmepp6:amd64 52
Added libgpgme11:amd64 to the remove list
Fixing libgpgmepp6:amd64 via keep of libgpgme11:amd64
Try to Re-Instate (5) libgpgme11:amd64
Done
Entering ResolveByKeep
Calculating upgrade... Done
The following packages have been kept back:
appstream gnubiff kwalletmanager libappstream-compose0 libappstream4 libkf5wallet-data libkf5wallet5
libkwalletbackend5-5 libnss-mymachines libnss-systemd libpam-systemd libsystemd-dev libsystemd0
libsystemd0:i386 libudev-dev libudev1 libudev1:i386 systemd systemd-container systemd-sysv
systemd-timesyncd udev
0 upgraded, 0 newly installed, 0 to remove and 22 not upgraded.
If so, then everyone would be seeing this problem, or at least many would.
The first half DOES provide more specific info on the specific packages that are being complained about.
Broken libkf5wallet5:amd64 Depends on libkf5wallet-data:amd64
And libgpgmepp6 seems relevant as well
I have not deciphered it yet, though.
As to many of the ‘held’ packages, those are being ‘phased’ by Ubuntu. All of the ones you have except for the kwallet related ones are being phased, or have dependencies that are. They are not related to kwallet, as far as I can tell, and I have a similar list of held stuff on one of my neon systems.
Broken libkf5wallet5:amd64 Depends on libkf5wallet-data:amd64
…
And libgpgmepp6 seems relevant as well
If I try to install those packages, apt goes haywire. I can not paste the complete output of the install command, because the forum system tells me it’s twice as much bytes than I am allowed to enter.
apt install libgpgmepp6
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libkf5wallet5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 -> 5.109.0-0xneon+22.04+jammy+release+build34 @ii uU Ib >
Broken libkf5wallet5:amd64 Hängt ab von on libkf5wallet-data:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 | 5.109.0-0xneon+22.04+jammy+release+build34 @ii uH > (= 5.109.0-0xneon+22.04+jammy+release+build34)
Considering libkf5wallet-data:amd64 15 as a solution to libkf5wallet5:amd64 53
Re-Instated libkf5wallet-data:amd64
Reinst Failed because of protected libkwalletbackend5-5:amd64
Removing libkf5wallet5:amd64 rather than change libkf5wallet-data:amd64
Investigating (0) libkf5khtml5:amd64 < 5.109.0-0xneon+22.04+jammy+release+build37 @ii K Ib >
Broken libkf5khtml5:amd64 Hängt ab von on libkf5wallet5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 | 5.109.0-0xneon+22.04+jammy+release+build34 @ii uR >
Considering libkf5wallet5:amd64 53 as a solution to libkf5khtml5:amd64 9
Removing libkf5khtml5:amd64 rather than change libkf5wallet5:amd64
Investigating (0) drkonqi:amd64 < 5.27.7-0xneon+22.04+jammy+release+build27 @ii K Ib >
Broken drkonqi:amd64 Hängt ab von on libkf5wallet5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 | 5.109.0-0xneon+22.04+jammy+release+build34 @ii uR >
Considering libkf5wallet5:amd64 53 as a solution to drkonqi:amd64 9
Removing drkonqi:amd64 rather than change libkf5wallet5:amd64
Investigating (0) kaccounts-integration:amd64 < 4:23.08.0-0xneon+22.04+jammy+release+build24 @ii K Ib >
Broken kaccounts-integration:amd64 Hängt ab von on libkf5wallet5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 | 5.109.0-0xneon+22.04+jammy+release+build34 @ii uR >
Considering libkf5wallet5:amd64 53 as a solution to kaccounts-integration:amd64 9
Removing kaccounts-integration:amd64 rather than change libkf5wallet5:amd64
Investigating (0) libokular5core11:amd64 < 4:23.08.0-0xneon+22.04+jammy+release+build30 @ii K Ib >
Broken libokular5core11:amd64 Hängt ab von on libkf5wallet5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 | 5.109.0-0xneon+22.04+jammy+release+build34 @ii uR >
Considering libkf5wallet5:amd64 53 as a solution to libokular5core11:amd64 7
Removing libokular5core11:amd64 rather than change libkf5wallet5:amd64
Investigating (0) kwalletmanager:amd64 < 4:22.12.3-0xneon+22.04+jammy+release+build14 | 4:23.08.0-0xneon+22.04+jammy+release+build19 @ii uH Ib >
Broken kwalletmanager:amd64 Hängt ab von on libkf5wallet5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 | 5.109.0-0xneon+22.04+jammy+release+build34 @ii uR >
Considering libkf5wallet5:amd64 53 as a solution to kwalletmanager:amd64 5
Reinst Failed because of protected libgpgmepp6:amd64
Reinst Failed because of libkf5wallet-bin:amd64
Removing kwalletmanager:amd64 rather than change libkf5wallet5:amd64
Investigating (0) libkpimgapicore5:amd64 < 23.08.0-0xneon+22.04+jammy+release+build21 @ii K Ib >
Broken libkpimgapicore5:amd64 Hängt ab von on libkf5wallet5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 | 5.109.0-0xneon+22.04+jammy+release+build34 @ii uR >
Considering libkf5wallet5:amd64 53 as a solution to libkpimgapicore5:amd64 4
Removing libkpimgapicore5:amd64 rather than change libkf5wallet5:amd64
Investigating (0) okular-backends:amd64 < 4:23.08.0-0xneon+22.04+jammy+release+build30 @ii K Ib >
Broken okular-backends:amd64 Hängt ab von on libokular5core11:amd64 < 4:23.08.0-0xneon+22.04+jammy+release+build30 @ii R > (= 4:23.08.0-0xneon+22.04+jammy+release+build30)
Considering libokular5core11:amd64 7 as a solution to okular-backends:amd64 4
Removing okular-backends:amd64 rather than change libokular5core11:amd64
Investigating (0) libkf5khtml-bin:amd64 < 5.109.0-0xneon+22.04+jammy+release+build37 @ii K Ib >
Broken libkf5khtml-bin:amd64 Hängt ab von on libkf5khtml5:amd64 < 5.109.0-0xneon+22.04+jammy+release+build37 @ii R >
Considering libkf5khtml5:amd64 9 as a solution to libkf5khtml-bin:amd64 4
Removing libkf5khtml-bin:amd64 rather than change libkf5khtml5:amd64
Investigating (0) konqueror:amd64 < 4:23.08.0-0xneon+22.04+jammy+release+build21 @ii K Ib >
Broken konqueror:amd64 Hängt ab von on libkf5wallet5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 | 5.109.0-0xneon+22.04+jammy+release+build34 @ii uR >
Considering libkf5wallet5:amd64 53 as a solution to konqueror:amd64 3
Removing konqueror:amd64 rather than change libkf5wallet5:amd64
Investigating (0) libkpimgapidrive5:amd64 < 23.08.0-0xneon+22.04+jammy+release+build21 @ii K Ib >
Broken libkpimgapidrive5:amd64 Hängt ab von on libkpimgapicore5:amd64 < 23.08.0-0xneon+22.04+jammy+release+build21 @ii R >
Considering libkpimgapicore5:amd64 4 as a solution to libkpimgapidrive5:amd64 2
Removing libkpimgapidrive5:amd64 rather than change libkpimgapicore5:amd64
Investigating (0) libkf5sane5:amd64 < 23.08.0-0xneon+22.04+jammy+release+build23 @ii K Ib >
Broken libkf5sane5:amd64 Hängt ab von on libkf5wallet5:amd64 < 5.108.0-0xneon+22.04+jammy+release+build32 | 5.109.0-0xneon+22.04+jammy+release+build34 @ii uR >
Considering libkf5wallet5:amd64 53 as a solution to libkf5sane5:amd64 2
Removing libkf5sane5:amd64 rather than change libkf5wallet5:amd64
Investigating (0) signon-kwallet-extension:amd64 < 4:23.08.0-0xneon+22.04+jammy+release+build20 @ii K Ib >
...
Sadly, that does not work either, because the package libxmlb2 seems to be too old and apt does not find a newer version:
sudo LC_ALL=C apt install appstream gnubiff libappstream-compose0 libappstream4 libnss-mymachines libnss-systemd libpam-systemd libsystemd-dev libsystemd0 libsystemd0:i386 libudev-dev libudev1 libudev1:i386 systemd systemd-container systemd-sysv systemd-timesyncd udev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 2
Starting 2 pkgProblemResolver with broken count: 2
Investigating (0) libappstream4:amd64 < 0.16.2-0xneon+22.04+jammy+release+build10 -> 0.16.2-0xneon+22.04+jammy+release+build18 @ii puU Ib >
Broken libappstream4:amd64 Depends on libxmlb2:amd64 < 0.3.6-2build1 @ii K > (>= 0.3.13)
Considering libxmlb2:amd64 11 as a solution to libappstream4:amd64 10013
Considering libxmlb2:amd64 11 as a solution to libappstream4:amd64 10013
Considering libxmlb2:amd64 11 as a solution to libappstream4:amd64 10013
Investigating (0) libappstream5:amd64 < none -> 1.0.0+p22.04+vrelease+git20230904.0432-0 @un puN Ib >
Broken libappstream5:amd64 Depends on libxmlb2:amd64 < 0.3.6-2build1 @ii K > (>= 0.3.14)
Considering libxmlb2:amd64 11 as a solution to libappstream5:amd64 4
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libappstream4 : Depends: libxmlb2 (>= 0.3.13) but 0.3.6-2build1 is to be installed
libappstream5 : Depends: libxmlb2 (>= 0.3.14) but 0.3.6-2build1 is to be installed
E: Unable to correct problems, you have held broken packages.
Hmmmm… I just had a closer look at the suggested command. There is no libappstream5 to be installed. And even when I leave libappstream4, I get the message about libappstream5, which I find a bit strange:
apt install appstream gnubiff libappstream-compose0 libnss-mymachines libnss-systemd libpam-systemd libsystemd-dev libsystemd0 libsystemd0:i386 libudev-dev libudev1 libudev1:i386 systemd systemd-container systemd-sysv systemd-timesyncd udev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libappstream5:amd64 < none -> 1.0.0+p22.04+vrelease+git20230904.0432-0 @un puN Ib >
Broken libappstream5:amd64 Depends on libxmlb2:amd64 < 0.3.6-2build1 @ii K > (>= 0.3.14)
Considering libxmlb2:amd64 11 as a solution to libappstream5:amd64 4
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libappstream5 : Depends: libxmlb2 (>= 0.3.14) but 0.3.6-2build1 is to be installed
E: Unable to correct problems, you have held broken packages.
Is anyone able to provide good news to this topic? I really would like to solve this mess. When I try to completely remove those packages, apt wants to remove my whole KDE Neon installation. That does not sound any good!
Could these missing and unmet dependencies be resolved by an empty fake package, that does not really install any files but makes the package management relax?
No, I did not change anything in apt’s settings or in the repositories, except for one thing: I added launchpad repository for Firefox, because I don’t like the snap version.
As far as I understand it now, it’s because of Ubuntu’s “phasing” of updates, as Claydoh mentioned above. I read the page that he linked in his comment: Ubuntu say, that there’s nothing to worry and that these messages about packages being held back will disappear sooner or later. I just don’t like to wait till “later”.
You can manually install the phased packages being held.
But, phased packages being held are not the same as held broken packages or dependencies.
There is something about your set of packages or repos that is off for some reason.
The following packages have unmet dependencies:
libappstream5 : Depends: libxmlb2 (>= 0.3.14) but 0.3.6-2build1 is to be installed
libxmlb2 0.3.6 is the version from ubuntu, while the version that libappstream5 wants (0.3.14) is provided by neon - and is the one I have on my system.
But also noting that libappstream5 isn’t available in neon’s repos for some reason.
I have this package installed, but it does not seem to be in the repos. I am seeking guidance from the powers that be on this. Something is not right here, for sure.
According to dpkg the version on my system is: “libxmlb2:amd64 0.3.6-2build1 amd64”
I downloaded and installed the package libxmlb2_0.3.10_2, and now, “apt full-upgrade” tells me, it wants to downgrade that package again:
The following packages have been kept back:
libappstream4 libkf5wallet-data libkf5wallet5 libkwalletbackend5-5 libpoppler-qt5-1
libpoppler131
The following packages will be DOWNGRADED:
libxmlb2
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 7 not upgraded.
Need to get 67.8 kB of archives.
After this operation, 7168 B of additional disk space will be used.
Do you want to continue? [Y/n]
Hi, I am looking into this. There is definately something amiss as we are on kf5 110 and there looks to be a mix of 108 and 109 there. The appstream issue is another matter entirely. One step at a time.
I just re-noticed this. That step was unnecessary, since Neon added the mozilla-team PPA for us. Neon never came with a Snap Firefox. What specifically did you add here, and how?
I’d suggest adding a listing of the contents of the directory /etc/apt/sources.list.d as well as /etc/apt/preferences.d/, as well as the full apt output requested.
Of course! Below you will find two outputs of “apt update”: the first is done with the Firefox ppa activated, the second one without.
claydoh: As you can see, without the ppa, apt wants to install the snap version of FF.
The package “gnubiff” is the only one I manually put on hold, because I built it myself from sources. The pre-compiled version shows some silly behaviour with its pop up window on KDE. But that package doesn’t make any difference, one of the first things I did was testing that: even if I completely remove it, apt’s output does not change.
Let me know if you need more information!
apt update | tee /tmp/aptupdate1.txt
Hit:1 http://de.archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://archive.neon.kde.org/user jammy InRelease [178 kB]
Hit:3 http://de.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:4 http://de.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:5 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
Hit:6 http://security.ubuntu.com/ubuntu jammy-security InRelease
Fetched 178 kB in 13s (14.1 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
11 packages can be upgraded. Run 'apt list --upgradable' to see them.
apt list --upgradable | tee -a /tmp/aptupdate1.txt
Listing...
gnubiff/jammy 2.2.17-3ubuntu1 amd64 [upgradable from: 2.2.17-1]
libappstream4/jammy 0.16.2-0xneon+22.04+jammy+release+build40 amd64 [upgradable from: 0.16.2-0xneon+22.04+jammy+release+build10]
libkf5wallet-data/jammy,jammy,jammy 5.110.0-0xneon+22.04+jammy+release+build36 all [upgradable from: 5.108.0-0xneon+22.04+jammy+release+build32]
libkf5wallet5/jammy 5.110.0-0xneon+22.04+jammy+release+build36 amd64 [upgradable from: 5.108.0-0xneon+22.04+jammy+release+build32]
libkwalletbackend5-5/jammy 5.110.0-0xneon+22.04+jammy+release+build36 amd64 [upgradable from: 5.108.0-0xneon+22.04+jammy+release+build32]
libnetplan0/jammy-updates 0.106.1-7ubuntu0.22.04.2 amd64 [upgradable from: 0.105-0ubuntu2~22.04.3]
libpoppler-qt5-1/jammy 23.10.0-0xneon+22.04+jammy+release+build24 amd64 [upgradable from: 23.09.0-0xneon+22.04+jammy+release+build19]
libpoppler131/jammy 23.09.0-0xneon+22.04+jammy+release+build22 amd64 [upgradable from: 23.09.0-0xneon+22.04+jammy+release+build19]
libsgutils2-2/jammy-updates 1.46-1ubuntu0.22.04.1 amd64 [upgradable from: 1.46-1build1]
netplan.io/jammy-updates 0.106.1-7ubuntu0.22.04.2 amd64 [upgradable from: 0.105-0ubuntu2~22.04.3]
sg3-utils/jammy-updates 1.46-1ubuntu0.22.04.1 amd64 [upgradable from: 1.46-1build1]
Just to let you know: some updated packages have been installed today, and now Okular, the PDF reader is gone, and I can’t reinstall it again, because:
apt install okular
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libpoppler132:amd64 < none -> 23.10.0-0xneon+22.04+jammy+release+build24 @un puN Ib >
Broken libpoppler132:amd64 Depends on libgpgmepp6:amd64 < 1.20.0-0xneon+22.04+jammy+release+build3 | 1.16.0-1.2ubuntu4.1 @ii H > (>= 1.22.0)
Considering libgpgmepp6:amd64 2 as a solution to libpoppler132:amd64 2
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libpoppler132 : Depends: libgpgmepp6 (>= 1.22.0) but 1.20.0-0xneon+22.04+jammy+release+build3 is to be installed
E: Unable to correct problems, you have held broken packages.
That file shouldn’t be there, it should have been removed some time ago, replaced by 99-jammy-overrides, but looks like yours didn’t for some reason.
These probably don’t belong, either. I don’t have them on any of my neon systems, but I vaguely remember these, possibly from the 20.04 days? I don’t have any 20.04-22.04 upgraded systems any longer to verify.
The contents of these apt pin files may be mucking around with package dependencies on your system. This probably explains why the pins to keep the Firefox Snap thing from installing (in org-kde-neon-net-launchpad-ppa-mozillateam-pin) aren’t working.
You could try moving those 4 files I have quoted out of that directory, and then do an apt update and full-upgrade, and see it that helps. If this has been happening for a very long time, it may take some extra work to get through, possibly.
Apt now does its work without mumbling about unmet dependencies, and synaptic did finally allow my to remove the packages that were marked “held back”, after I let it reload the repositories. I don’t know where these files came from. As far as I remember, this system has been set up as a clean new installation of Neon/Jammny, it has not been upgraded from any previous version.
About the Firefox ppa I am not so sure, because when I deactivate this ppa, apt wants to use the snap version, if I understand its output correctly:
``
apt update
Hit:1 Index of /ubuntu jammy InRelease
Get:2 Index of /user jammy InRelease [178 kB]
Hit:3 Index of /ubuntu jammy-updates InRelease
Hit:4 Index of /ubuntu jammy-backports InRelease
Hit:5 Index of /ubuntu jammy-security InRelease
Fetched 178 kB in 1s (189 kB/s)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
3 packages can be upgraded. Run ‘apt list --upgradable’ to see them.
)
