It is important if you want to build from source, it will install a whole bunch of packages. It is what is called a Meta package nothing but a package to force the install of other packages. In it case to save a person time and effort installing the essential packages needed to compile working software. And in your case you show here the libc6-dev is preventing the libc6 from being upgraded to the new required version for the newer software. This package is essential as the libc6 is the underlying basis of any Linux system, all of the software installed is compiled against the libraries it provides. You cannot upgrade without it being upgraded, remove the -dev.
hallo again.
I went through the list of packages required by this libc6 package, what is left have circular requirements:
sudo dpkg -r libc6-dev
dpkg: dependency problems prevent removal of libc6-dev:amd64:
zlib1g-dev:amd64 depends on libc6-dev | libc-dev; however:
Package libc6-dev:amd64 is to be removed.
Package libc-dev is not installed.
Package libc6-dev:amd64 which provides libc-dev is to be removed.
libtiff-dev:amd64 depends on libc6-dev | libc-dev; however:
Package libc6-dev:amd64 is to be removed.
Package libc-dev is not installed.
Package libc6-dev:amd64 which provides libc-dev is to be removed.
zlib1g-dev:amd64 depends on libc6-dev | libc-dev; however:
Package libc6-dev:amd64 is to be removed.
Package libc-dev is not installed.
Package libc6-dev:amd64 which provides libc-dev is to be removed.
libtiff-dev:amd64 depends on libc6-dev | libc-dev; however:
Package libc6-dev:amd64 is to be removed.
Package libc-dev is not installed.
Package libc6-dev:amd64 which provides libc-dev is to be removed.
libjpeg-turbo8-dev:amd64 depends on libc-dev; however:
Package libc-dev is not installed.
Package libc6-dev:amd64 which provides libc-dev is to be removed.
dpkg: error processing package libc6-dev:amd64 (--remove):
dependency problems - not removing
Errors were encountered while processing:
libc6-dev:amd64
example: libjpeg-turbo8-dev:
sudo dpkg -r libjpeg-turbo8-dev
dpkg: dependency problems prevent removal of libjpeg-turbo8-dev:amd64:
libtiff-dev:amd64 depends on libjpeg-dev; however:
Package libjpeg-dev is not installed.
Package libjpeg-turbo8-dev:amd64 which provides libjpeg-dev is to be removed.
libcupsimage2-dev:amd64 depends on libjpeg-dev; however:
Package libjpeg-dev is not installed.
Package libjpeg-turbo8-dev:amd64 which provides libjpeg-dev is to be removed.
dpkg: error processing package libjpeg-turbo8-dev:amd64 (--remove):
dependency problems - not removing
Errors were encountered while processing:
libjpeg-turbo8-dev:amd64
then:
sudo dpkg -r libtiff-dev
dpkg: dependency problems prevent removal of libtiff-dev:amd64:
libcupsimage2-dev:amd64 depends on libtiff-dev.
dpkg: error processing package libtiff-dev:amd64 (--remove):
dependency problems - not removing
Errors were encountered while processing:
libtiff-dev:amd64
then:
sudo dpkg -r libcupsimage2-dev
dpkg: dependency problems prevent removal of libcupsimage2-dev:amd64:
libcups2-dev:amd64 depends on libcupsimage2-dev (= 2.4.1op1-1ubuntu4.11).
dpkg: error processing package libcupsimage2-dev:amd64 (--remove):
dependency problems - not removing
Errors were encountered while processing:
libcupsimage2-dev:amd64
finally:
sudo dpkg -r libcups2-dev
dpkg: dependency problems prevent removal of libcups2-dev:amd64:
libcupsimage2-dev:amd64 depends on libcups2-dev (= 2.4.1op1-1ubuntu4.11).
dpkg: error processing package libcups2-dev:amd64 (--remove):
dependency problems - not removing
Errors were encountered while processing:
libcups2-dev:amd64
so libcups2-dev requires libcupsimage2-dev, which in turn requires libcups2-dev . is there a way to resolve this? cups is not a required package on this system at this stage.
thanks!
Christ what a mess. Try putting them all one the one line with the dpkg -r to see if that helps. By all I mean the packages you try to remove and the ones it complains about being dependent on them. All of them -dev packages have no use for anything on a system for just desktop use. How did they get on there, were they installed by default?
sometimes I would build packages out of tree with cmake so I required some dev packages.
ok I have made some progress, having the packages in the same line helped with removing some of the packages however I have reached another circular package cycle with plasma-workspace.
sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
libasound2-dev : Depends: libasound2 (= 1.2.6.1-1ubuntu1)
libc6-dev : Depends: libc6 (= 2.35-0ubuntu3.8) but 2.39-0ubuntu8.3 is installed
Depends: libc-dev-bin (= 2.35-0ubuntu3.8)
libgegl-0.4-0t64 : Depends: libpng16-16t64 (>= 1.6.2) but it is not installed
libglib2.0-bin : Depends: libglib2.0-0 (= 2.72.4-0ubuntu2.4)
libglib2.0-dev-bin : Depends: libglib2.0-0 (= 2.72.4-0ubuntu2.4)
libssl-dev : Depends: libssl3 (= 3.0.2-0ubuntu1.18)
libva-drm2 : Depends: libva2 (>= 2.20.0) but 2.14.0-1 is installed
libva-x11-2 : Depends: libva2 (>= 2.20.0) but 2.14.0-1 is installed
network-manager : Depends: libnm0 (= 1.36.6-0ubuntu2) but 1.46.0-1ubuntu2.2 is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
then attempt to remove libva-x11-2
sudo dpkg -r libva-x11-2
dpkg: dependency problems prevent removal of libva-x11-2:amd64:
libavutil56:amd64 depends on libva-x11-2 (>= 1.3).
dpkg: error processing package libva-x11-2:amd64 (--remove):
dependency problems - not removing
Errors were encountered while processing:
libva-x11-2:amd64
then:
sudo dpkg -r libswscale5 libavfilter7 libkpipewirerecord6 qml6-module-org-kde-pipewire qml-module-org-kde-pipewire plasma-workspace
dpkg: dependency problems prevent removal of plasma-workspace:
libweather-ion7 depends on plasma-workspace.
libtaskmanager6 depends on plasma-workspace.
libplasma-geolocation-interface5 depends on plasma-workspace.
libnotificationmanager1 depends on plasma-workspace.
libkworkspace6-6 depends on plasma-workspace.
libkfontinstui5 depends on plasma-workspace.
libkfontinst5 depends on plasma-workspace.
libcolorcorrect5 depends on plasma-workspace.
dpkg: error processing package plasma-workspace (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of qml-module-org-kde-pipewire:
plasma-workspace depends on qml-module-org-kde-pipewire.
dpkg: error processing package qml-module-org-kde-pipewire (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of qml6-module-org-kde-pipewire:
qml-module-org-kde-pipewire depends on qml6-module-org-kde-pipewire.
dpkg: error processing package qml6-module-org-kde-pipewire (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of libkpipewirerecord6:
qml6-module-org-kde-pipewire depends on libkpipewirerecord6 (= 6.2.0-0zneon+22.04+jammy+release+build9).
dpkg: error processing package libkpipewirerecord6 (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of libavfilter7:amd64:
libkpipewirerecord6 depends on libavfilter7 (>= 7:4.4).
dpkg: error processing package libavfilter7:amd64 (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of libswscale5:amd64:
libavfilter7:amd64 depends on libswscale5 (= 7:4.4.2-0ubuntu0.22.04.1).
dpkg: error processing package libswscale5:amd64 (--remove):
dependency problems - not removing
Errors were encountered while processing:
plasma-workspace
qml-module-org-kde-pipewire
qml6-module-org-kde-pipewire
libkpipewirerecord6
libavfilter7:amd64
libswscale5:amd64
then with plasma-workspace:
sudo dpkg -r plasma-workspace
dpkg: dependency problems prevent removal of plasma-workspace:
libweather-ion7 depends on plasma-workspace.
libtaskmanager6 depends on plasma-workspace.
libplasma-geolocation-interface5 depends on plasma-workspace.
libnotificationmanager1 depends on plasma-workspace.
libkworkspace6-6 depends on plasma-workspace.
libkfontinstui5 depends on plasma-workspace.
libkfontinst5 depends on plasma-workspace.
libcolorcorrect5 depends on plasma-workspace.
dpkg: error processing package plasma-workspace (--remove):
dependency problems - not removing
Errors were encountered while processing:
plasma-workspace
then:
sudo dpkg -r plasma-workspace libweather-ion7 libtaskmanager6 libplasma-geolocation-interface5 libnotificationmanager1 libkworkspace6-6 libkfontinstui5 libkfontinst5 libcolorcorrect5
dpkg: dependency problems prevent removal of libkworkspace6-6:
libkworkspace5-5 depends on libkworkspace6-6.
dpkg: error processing package libkworkspace6-6 (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of plasma-workspace:
libkworkspace6-6 depends on plasma-workspace.
dpkg: error processing package plasma-workspace (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of libweather-ion7:
plasma-workspace depends on libweather-ion7.
dpkg: error processing package libweather-ion7 (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of libtaskmanager6:
plasma-workspace depends on libtaskmanager6.
dpkg: error processing package libtaskmanager6 (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of libplasma-geolocation-interface5:
plasma-workspace depends on libplasma-geolocation-interface5.
dpkg: error processing package libplasma-geolocation-interface5 (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of libnotificationmanager1:
plasma-workspace depends on libnotificationmanager1.
dpkg: error processing package libnotificationmanager1 (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of libkfontinstui5:
plasma-workspace depends on libkfontinstui5.
dpkg: error processing package libkfontinstui5 (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of libkfontinst5:
plasma-workspace depends on libkfontinst5.
dpkg: error processing package libkfontinst5 (--remove):
dependency problems - not removing
dpkg: dependency problems prevent removal of libcolorcorrect5:
plasma-workspace depends on libcolorcorrect5.
dpkg: error processing package libcolorcorrect5 (--remove):
dependency problems - not removing
Errors were encountered while processing:
libkworkspace6-6
plasma-workspace
libweather-ion7
libtaskmanager6
libplasma-geolocation-interface5
libnotificationmanager1
libkfontinstui5
libkfontinst5
libcolorcorrect5
thanks for your help with this so far!
The plasma-workspace is a base package for kde try not to remove it if possible. Hopefully you keep list of these packages removed. Try not to get too focused on the one task I do it myself at times and miss the obvious. I see the apt is back to at least attempting to work. You missed opportunity there you can still take with the sudo apt --fix-broken install it suggested you use. Give it a go and see what happens. Your best bet right now after that is attempted is seeing if you can download and install with dpkg the libc6-dev as it will not let you remove it, upgrade it to the version matching the libc6 that is installed. This I think might break the impasse and allow the other packages to start upgrading.
hallo again.
after all this messing around with dpkg apt started to work again.
so I am now running pkcon update, installing a lot of packages (from noble repositories I guess)
maybe this upgrade will complete without trouble, I will let you know when it completes.
thanks for your support with this issue, you have helped a lot!
You are welcome. Like I first said the solution to these thing when they happen can be convoluted but you just have to keep at it until you find the magic package(s) that was/were causing all the problems. Once that gets installed it breaks the log jam and everything starts to flow or go as it is, as it is supposed to. It should hopefully complete as with all of this we should have tracked down all the problem packages.
hi! so the apt full-upgrade command completed last night.
I also ran pkcon update and apparently this system is upgraded.
before I restart is there any way to verify the system will reboot without issues?
thanks again for your help with this.
No I have never found one. But if everything got upgraded like the kernel, the libc6 those type of basic system packages then it really should just boot. A Debian based system is really good at these type of distribution version upgrades. Oh now I mention kernel that should have been updated this means extra junk laying around never to be used again in the old version for the third kernel installed. Use sudo apt autoremove to have apt clean out the orphaned packages from all of these upgrades in addition to the third kernel it does automatically when using that command. When it boots and you confirm it worked can you mark the thread as solved.
hallo!
did not reboot again!
now boot will return to the “busybox” shell with an error about UUID not found.
this could be to do with my hard drive being encrypted?
decryption works fine (currently typing this from a live disk), and the hard drives mount ok however the drive is not being mounted at boot.
the uuid given by the error is different to the uuid for the root drive in /etc/fstab (also in crypttab, which I do not know a lot about)
any help appreciated.
No clue on the encrypted hard drive never used that. The uuid error if using efi with the grub bootloader then there are three places where it must match up for it to boot.
The first /boot/efi/EFI/debian/grub.cfg in my case each OS vendor/provider use their own name for the directory in there. My file.
root@9600k:~# cat /boot/efi/EFI/debian/grub.cfg
search.fs_uuid a4410a13-b1ea-4007-b22f-6eb9e0a2ead4 root
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
There you see the uuid of the / partition on my NVMe drive I us to boot on. The second is another grub.cfg file the /boot/grub/grub.cfg.
root@9600k:~# grep -i a4410a13-b1ea-4007-b22f-6eb9e0a2ead4 /boot/grub/grub.cfg
linux /boot/vmlinuz-6.12.5-amd64 root=UUID=a4410a13-b1ea-4007-b22f-6eb9e0a2ead4 ro
That shows the kernel entry it is to boot using my uuid as the place to find it. There are numerous entries in that file where it appears. The third is the /etc/fstab.
root@9600k:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / is on /dev/nvme1n1p2 9600k machine SP NVMe
UUID=a4410a13-b1ea-4007-b22f-6eb9e0a2ead4 / ext4 errors=remount-ro 0 1
There you tell the system to mount the UUID where your / partition is. All three of these being correct will eliminate any UUID errors when booting with grub on an efi system. Since you can decrypt the drive from live system you can mount the partitions for the /boot/efi and / on the internal drive to check and if necessary edit the files to make them math up with what is needed. To find the uuid if you do not know it use use the blkid command.
root@9600k:~# blkid | grep nvme1 |sort -n
/dev/nvme1n1p1: SEC_TYPE="msdos" LABEL_FATBOOT="SPNVMEEFI" LABEL="SPNVMEEFI" UUID="FEC4-39C0" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="254da66f-ea2b-43db-ab14-480480308d14"
/dev/nvme1n1p2: LABEL="SPNVMERoot" UUID="a4410a13-b1ea-4007-b22f-6eb9e0a2ead4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="f979d6b1-0c46-4357-88b3-6afd8e25dfe5"
/dev/nvme1n1p3: LABEL="SPNVMEHome" UUID="1ba697ed-bde7-4bd3-b9f3-b47045b44585" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="8854aa17-12b1-464f-9abf-a686e7d64b6b"
thank you for your reply.
the uuid in fstab for root / swap are correct for their system detected uuids (/media/ubuntu/[UUID] however during boot from hard drive the uuid the system claims cannot be mounted is different from those in fstab and from mount?
the drive is a dos partition boot sector, not efi.
the entry in fstab is correct for the uuid of /dev/sda1.
thanks again for your support!
Well we have reached the limit here for me. I have absolutely no idea how it works with a BIOS booting doing this. Only the EFI which I have played around with many many times. Though with the prompt you get is it a grub prompt? If so a google on booting from grub prompt should get you some instructions on how to figure out that. Which can be done to get into the system then once there run the sudo update-grub to get it to reinstall. Basically I think the idea is you set the root file system on the command line of it, then telling it to boot. Not sure I never use that method as all my errors like that are from when I manually clone a hard drive and forget to change a UUID. Then is is just a matter of mounting the drive again and correcting the mistake to boot again.
ok well I will start a new topic for this issue, then if that is resolved and boot completes I will return to mark this fixed.
thank you for your help with the apt upgrade issue!