I had Discover to update my KDE Neon installaton, as usual. My current version is now 5.27.

The updater removed digiKam in order to update the system.

1. Why it needed to remove DigiKam ? i.e. Why /how come system can remove applications without actually upgrading/replacing them with a functional replacement !?
2. How can I recover my installation (with all the settings and references to the database etc.) ?

BR

1. Don't know, without more information.
Have you done any software repo customization, additions, or used any workarounds in order to install something in the recent past, such as those involving libjpeg-turbo or similar used to install wine?
This one downgrades libraries that Digikam requires, so the system will want to uninstall it

2. The settings and data are still present, those are stored in your user directories, and are not removed when an application is uninstalled.

Try and re-install Digikam, and see what happens there - report any error messages.
Though I suspect it won't, and complain about the things used to fix Wine.
You can use Discover, but you will get more thorough messaging that is easier to copy and paste if you use the command line:

Code: Select all

sudo apt update
sudo apt full-ugrade
sudo apt install digikam

Updating should present you a list of what is happening, and requires the user OK things.
If you are using the stock update settings -- applied during a reboot process -- you may need to click the 'more information' to see everything a bit easier, though it should still be indicating that things are set to be removed.

You can disable the Offline Updates feature in System Settings, which does present a full list of changes directly up front.

Someone is working on a fix for the libjpeg issue, even over the weekend it seems, but no idea when that will come down the pike.

Thank you for a prompt reply !

I have not added any repositories manually. i have already in the past discovered issues they may lead to on a system that you want to maintain as your main working tool for a a longer period of time. For the same reason, I have felt safer to use Discover (I have also flatpak and snap packages) but I am able to use CLI (apt) as well.

But I have, indeed, installed Wine. I can see from the other posts that it is potential cause of the problem. I think I have Wine and Q4Wine installed through discover.
I have also libjpeg-trubo8 (i386) installed and libjpg-turbo8 'upgradeable'. I recall that I needed to install the i386 architecture in order to install the Wine.
It appars I have the following packages with 'Wine' in the package name

Code: Select all

fonts-wine/jammy,jammy,now 6.0.3~repack-1 all [installed,automatic]
libkwineffects14/jammy,now 4:5.27.2-0xneon+22.04+jammy+release+build32 amd64 [installed]
libwine/jammy,now 6.0.3~repack-1 amd64 [installed,automatic]
libwine/jammy,now 6.0.3~repack-1 i386 [installed,automatic]
q4wine/jammy,now 1.3.12-1 amd64 [installed]
wine32/jammy,now 6.0.3~repack-1 i386 [installed,automatic]
wine64/jammy,now 6.0.3~repack-1 amd64 [installed,automatic]
wine/jammy,jammy,now 6.0.3~repack-1 all [installed]

I may not need Wine and I am ready to remove it if that makes my system more stable.

Unfortunately, I am not able to try to re-install digiKam today. Before trying, do you have recommendation if I should remove something (If yes, what) prior trying to re-install, or am I better off by first installing and then removing ? Maybe, if I have installed Wine via Discover, I should use the same tool to remove ? I just do not want to end up in trouble and messing up my system.

Thank you for your support !

Someone here used Aptitude to 'fix' things, which might be useful
I do not like or recommend Aptitude in most cases, as it is quite literally Apt on steroids, and very easily can make things even worse.
But it did work, it seems.

I do see i386 builds of the package in the pipeline, but no idea if/when they will work their way down to normal user repos.
I might suggest an option might be to use the flatpak or snap of Digikam temporarily than attempt to clean up trying to remove things. But this probably involves importing the existing libraries and settings.

A better idea for a temporary solution is to use the fully standalone appimage
https://www.digikam.org/download/ This is a no-install and self-contained version. You probably need to mark the file as executable, but runs from anywhere via a double-click. It will use your existing setup directly.

You would try uninstalling libjpeg-turbo8:i386 using apt, and then see what 32-bit things it wants re uninstall as well, and see if anything important to you is in there.

if you proceed, then you *should* just be able to reinstall digikam.

Thank you. Your reply solved my problem.

I do not need Wine, so I decided to remove the libjpeg-turbo8:i386. I only had the Wine requiring i386 packages, and only the following packages ended up to be removed:
The following packages will be REMOVED:
gstreamer1.0-plugins-good:i386 libgd3:i386 libgdk-pixbuf-2.0-0:i386 libgphoto2-6:i386 libjpeg-turbo8:i386 libjpeg8:i386 libtiff5:i386 libv4l-0:i386 libv4lconvert0:i386 libwine:i386 wine32:i386
After removing the problem package, I upgraded my system and re-installed digikam. The installation was fully recovered with all my previous settings.

The commands I executed, per your suggestion, were:

Code: Select all

sudo apt remove libjpeg-turbo8:i386
sudo apt update
sudo apt full-upgrade
sudo apt install digikam


Thanks !

there are new improved (TM) libjpeg-turbo patches coming down through the build infrastructure which should fix the libjpeg-turbo and jpeg8 dependency mess and also have shiny new i386 packages to boot. should be in user on next release

carlosdem wrote:there are new improved (TM) libjpeg-turbo patches coming down through the build infrastructure which should fix the libjpeg-turbo and jpeg8 dependency mess and also have shiny new i386 packages to boot. should be in user on next release

I am excited for this. Thank you!