Reply to topic

KMyMoney not installable after updates on 19-Feb-2021

User avatar Paul
Registered Member
Posts
29
Karma
0
OS
The update I installed via Discover on 19 Feb removed KMyMoney and now I can't re-install it. Also can't install it on a fresh installation of neon user edition. There seems to be a dependency problem:

[email protected]:~$ sudo apt install kmymoney
Reading package lists... Done
Building dependency tree
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) kmymoney:amd64 < none -> 5.1.1-0xneon+20.04+focal+build7 @un puN Ib >
Broken kmymoney:amd64 Depends on kmymoney-common:amd64 < none | 5.1.1-0xneon+20.04+focal+build7 @un uH > (= 5.1.1-0xneon+20.04+focal+build7)
Considering kmymoney-common:amd64 0 as a solution to kmymoney:amd64 9999
Re-Instated kmymoney-common:amd64
Broken kmymoney:amd64 Depends on libalkimia5-8:amd64 < none | 8.0.4-0xneon+20.04+focal+build6 @un uH >
Considering libalkimia5-8:amd64 1 as a solution to kmymoney:amd64 9999
Re-Instated alkimia-data:amd64
Re-Instated libalkimia5-8:amd64
Broken kmymoney:amd64 Depends on libaqbanking44:amd64 < none | 6.2.6-0xneon+20.04+focal+build5 @un uH >
Considering libaqbanking44:amd64 1 as a solution to kmymoney:amd64 9999
Re-Instated libaqbanking-data:amd64
Reinst Failed early because of libgwenhywfar79:amd64
Considering libaqbanking44:amd64 1 as a solution to kmymoney:amd64 9999
Considering libaqbanking44:amd64 1 as a solution to kmymoney:amd64 9999
Considering libaqbanking44:amd64 1 as a solution to kmymoney:amd64 9999
Considering libaqbanking44:amd64 1 as a solution to kmymoney:amd64 9999
Broken kmymoney:amd64 Depends on libgwengui-qt5-79:amd64 < none | 5.5.1-0xneon+20.04+focal+build3 @un uH >
Considering libgwengui-qt5-79:amd64 1 as a solution to kmymoney:amd64 9999
Reinst Failed early because of libgwenhywfar79:amd64
Considering libgwengui-qt5-79:amd64 1 as a solution to kmymoney:amd64 9999
Broken kmymoney:amd64 Depends on libgwenhywfar79:amd64 < none | 5.1.3-1build1 @un uH > (>= 5.5.1)
Considering libgwenhywfar79:amd64 0 as a solution to kmymoney:amd64 9999
Re-Instated libgwenhywfar-data:amd64
Re-Instated libgwenhywfar79:amd64
Broken kmymoney:amd64 Depends on libofx7:amd64 < none | 1:0.9.15-3build1 @un uH > (>= 0.9.14)
Considering libofx7:amd64 0 as a solution to kmymoney:amd64 9999
Re-Instated libosp5:amd64
Re-Instated libofx7:amd64
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.
kmymoney : Depends: libaqbanking44 but it is not going to be installed
Depends: libgwengui-qt5-79 but it is not going to be installed
Depends: libgwenhywfar79 (>= 5.5.1) but 5.1.3-1build1 is to be installed
Recommends: kleopatra but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


Running KDE neon User Edition
User avatar theabarnes
Registered Member
Posts
8
Karma
0
OS
I ran into this myself when I updated a couple days ago. The solution is to comment out the lines about
Code: Select all
libgwenhywfar
in
Code: Select all
/etc/apt/preferences.d/99-focal-overrides
. That overrides file is provided by the neon-settings-2 package, and I think it was the last update of that package that broke things.
jmacleod
Registered Member
Posts
40
Karma
0
I found the same problem also on a test install. However I now always use the KMM appimage which can be downloaded via the KMM homepage. This is constantly updated and so does not run into problems like this.

Make the downloaded app executable and you're good to go.
(I use appimages for digiKam, KMM, LibreOffice, Strawberry and others - all in an appimage folder).
User avatar Paul
Registered Member
Posts
29
Karma
0
OS
Thanks for the advice guys, I also found that aptitude was able to resolve the dependency problem. But just now (20 Feb 18:01) I received an update to the neon-settings-2 package which has resolved the problem. 😁


Running KDE neon User Edition
manttila
Registered Member
Posts
18
Karma
0
Hi,

This happened to me also. KMyMoney was removed by the KDE Neon update (Discover) on 21st. KMyMoney is also not available for re-install in Discover.
I have today updated all packages (with Discover) and my neon-settings-2 is Version: 0.4+p20.04+git20210220.1700. KMyMoney is still uninstallable via Discover.
If someone has this resolved through package updates I would be interested in knowing package versions required.

I am using KDE Neon 5.21 User Edition.

This is kind of annoying issue for an average user. Applications should not just disappear.

BR
User avatar Snowhog
Registered Member
Posts
198
Karma
1
OS
I'm running KDE neon 5.21 User Edition as my main OS.

I just had kmymoney removed during this afternoons update to my system. I don't use Discover (POS in my opinion). In fact, I don't use a package manager for system maintenance at all. I do all my package management from the CLI. After kmymoney was removed, I installed it (again) from the CLI:

sudo apt install kmymoney

It installed without any issue, which of course begs the question: Why did it have to be removed at all during the update?


Administrator
Kubuntu Forums . Net - https://kubuntuforums.net
User avatar claydoh
Registered Member
Posts
741
Karma
6
OS
Snowhog wrote:
It installed without any issue, which of course begs the question: Why did it have to be removed at all during the update?


  • The previous update to the neon-settings-2 package contained a mis-configured/outdated/incorrect apt preference file.
  • This new config is not read until the next time the system is checked for updates.
  • The next time updates are checked, the new config is read
  • Then, the incorrect info causes the dependency problem, prompting for the removal of KMyMoney.

Then, in the more recent update:
  • A new version of neon-settings-2 is released
  • This gets installed the next time the system is updated
  • However, the corrected preference file included in it does not get read until the next time the system is checked for updates. i.e; you cannot change apt's settings while apt is running.
  • KMyMoney is still prompted for removal, as the new preference setting is not in effect yet.

So, KMM is removed, and can be reinstalled after the update as the broken config and the dependency it created is fixed. Sucks, but afaik the only way to do it, if the user does not know about the bad config ahead of time.

Just, ahem, normal apt and dpkg stuff.
Discover has zero to do with anything here as it is still using apt/dpkg on Debian-like systems.


claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
pwrcul
Registered Member
Posts
75
Karma
0
OS
Thanks for the discussion and tips.
I found the same issue after a recent update.
KMyMoney is working again.


Neon Plasma 5.20 User on 1 desktop and on Asus Transformer 3 Pro laptop. Win10 in VirtualBox for JMP stat package. Still 5.19 on older desktop.

 
Reply to topic

Bookmarks



Who is online

Registered users: andrewm, Baidu [Spider], Bing [Bot], Google [Bot], Merlimau, ssanderson, Yahoo [Bot]