5.1.3 is better than 5.2.1

[Jack]

Bill,

First, thanks for the update.  I was really hoping theere wasn't  
something wrong with the Fedora build. :-)  More comments below.

On 2025.11.05 17:45, Bill Gee via KMyMoney wrote:
> Dang it, something changed!  I started up KMyMoney again to run  
> verify the problems, and now it is working!  Argh ....  I hate  
> problems that go away for no apparent reason.  The very first  
> requirement for troubleshooting is to reliably replicate the problem.
> 
> Hypothesis:  When I ran KyMyMoney this morning, it migrated my data  
> file.  I wonder if the migration process required an exit and  
> restart?? It did not say anything about that.
There is no "migration" of data, in the usual sense.  There have been  
no changes to the basic data structure of a .kmy file.  (It is just a  
gzipped xml file.)  However, there ARE occasional changes to some of  
the details of how data is stored, as well as added checks for invalid  
or questionable data.  There is a "version" number of the data format  
stored in the file, but any time an older version is read in, relevant  
data gets an extra check and is then stored in the new way, and the new  
version number is stored the next time the data file is saved.  I don't  
think your problems were due to this, becuase the newly saved file  
would have the same problems.

> Hypothesis:  This machine has been running Fedora for years.  I  
> upgrade every time a new version comes out.  No reinstalls - That  
> would take days.  I wonder if the KMyMoney configuration file had  
> some accumulated cruft?
while I won't rule that out, it just doesn't strike me as very likely.

> Resizing a column is still fairly slow, but everything else works at  
> good speed.
What I find odd here is that most column resizing for me is almost  
instantaneous, but I can't resize the Detail column, except by changing  
the width of the window.

> I started KMyMoney from a command shell.  It issued about 40 or 50  
> lines similar to these:
> 
> kf.coreaddons: The plugin  
> "/usr/lib64/qt6/plugins/kmymoney_plugins/ofximporter.so" explicitly  
> states an 'Id' in the embedded metadata. This value should be  
> removed, the resulting pluginId will not be affected by it
> kf.coreaddons: The plugin  
> "/usr/lib64/qt6/plugins/kmymoney_plugins/konlinetasks_sepa.so"  
> explicitly states an Id in the embedded metadata, which is different  
> from the one derived from the filename The Id field from the KPlugin  
> object in the metadata should be removed
> 
> Each line named a different .so file.  There was nothing else that  
> looked like any kind of error.
That is actually not a new issue, and has recently been fixed, but the  
fix will only be in 5.2.2 or a version built from the 5.2 or master  
branches of the git repository.  The are not related to any of the  
problems you had.

> I am running KDE Plasma desktop under Wayland.  The display adapter  
> is an old Intel.  I got tired of fighting with both AMD and nVidia  
> drivers, so reverted to something that Just Works.
:-)  We do sometimes find issues related to Wayland vs. xorg, but this  
didn't sound like it.  I am also using full KDE Plasma with Wayland,  
although I do have AMD graphics on my main PC.

> Flatpaks/snaps/et.al.   I have four problems with them.  1) They  
> strike me as a solution looking for a problem.  If you need to  
> virtualize, why not do the whole machine?  2) They do not save files  
> where I can see them from other applications.  3) The last one I  
> tried wanted to download nearly 4 gigabytes of stuff!  For an  
> application where the native RPM file is less than 50 megabytes!  4)  
> They do not interact with other applications on the machine.
> 
> As an example, I tried the flatpak for LabPlot a few years ago.  I  
> used it to generate a plot, then exported the plot to a jpg file in  
> ~/Documents.  When I went to find that file in Dolphin, it was not  
> there!  WTF???  Back to LabPlot - save the file again - It said it  
> was going to overwrite.  How could it do that to a file that did not  
> exist??  I also tried to view the file from within LabPlot, but it  
> said there were no suitable viewers on the machine.  WTF???  I have a  
> dozen different apps that can view jpg files.  That experience left a  
> VERY bad taste, and I have not been back.  The geeks can have fun - I  
> want it to Just Work.
First, note that (as far as I can tell) one of the purposes of those  
standalone packages (flatpak, snap, and appimage) is not virtualiztion,  
but isolation (which I think is more true of the first two than the  
last one.)  In particular, the main concept of an Appimage is that it  
contains all the dependency libraries rather than instisting they  
already be installed or (as apparently with the Flatpak) installed as  
more Flatpaks.  While an Appimage may be larger than the native package  
file for KMyMoney, the difference is not huge.  The advantage of  
Appimages, is, for example, that you can run a newer version than is  
available as a disto package, which is particularly true for LTS  
distros, which trade stability for being up-to-date.

As far as the "isolation" of the Flatpacks, it is intentional, but can  
be overridden, and I believe there are even modern GUI applications to  
contraol that.  I have not used Flatpaks or snaps myself, but this  
issue has been discussed recently on discuss.kde.org.  Note that this  
isolation mechanism is not used by Appimages.

Jack

> On 11/5/25 15:42, Jack via KMyMoney wrote:
>> On 2025.11.05 09:44, Bill Gee via KMyMoney wrote:
>>> Now that I have 5.2.1 courtesy of Fedora 42 to 43 upgrade, I have  
>>> to say ...  FAIL!!!
>>> 
>>> Gimme back 5.1!!
>> The first thing I'll point out is that almost everything you are  
>> complaining about works perfectly well for most users.  What we need  
>> to do is figure out why things are not working correctly for you.   
>> It seems unlikely the problems are inherent in the KMyMoney code, so  
>> we need to dig deeper.
>> 
>>> 1) When I click on the Accounts icon on the left side, it gives me  
>>> a list of Liability, Asset and Favorite.  Single-clicking the arrow  
>>> beside any of these does nothing (behavior change - it used to open  
>>> the sublist).
>> For me (Gentoo Linux) clicking the arrow does expand the list of  
>> that type of account, as it has always done.
>> 
>>> Double-clicking on any of the three entries opens Liability and  
>>> shows me the one credit card account.  Click or double-clicking on  
>>> that account closes the sublist (behavior change - it used to take  
>>> me to the ledger for that account).
>> For me, double clicking opens that list, same as clicking the arrow.
>> Do you have more Liability accounts than just that Credit Card, or  
>> is that the only one?
>> For me, single clicking any account simply selects it (and enables  
>> the right click context menu.)  Double clicking takes me to the  
>> ledger for that account
>> 
>>> 2) So how do I get to the account ledgers now?  The only way I have  
>>> found is to go to the Institutions icon, open the institution and  
>>> double-click the account.
>> While I agree you should not need to do this, you can go to the  
>> Ledgers View (click the Ledgers icon on the left.)  Then click the   
>> "+" near the top.  This will open a drop-down where you can select  
>> any account.
>> 
>>> 3) Click on the Categories icon on the left.  It gives me Expenses  
>>> and Income.  Clicking or double-clicking on either does nothing.   
>>> (behavior change - It used to open a sublist.)
>> This continues to behave for me the same as the accounts and  
>> institutions views.
>> 
>>> Update - I waited several minutes.  Now double-clicking on either  
>>> Expense or Income will open a sublist under Expense.  Clicking or  
>>> double-clicking any item on the sublist closes the sublist.
>> Still seems odd - single clicking should just select the clicked  
>> item.  Double clicking a grouping entry should expand or contract  
>> its sublist.  Double clicking an item (Account or Category or ...)  
>> should open that item in the Ledger.
>> 
>>> 4) Account ledgers now have a column for Details.  I don't want  
>>> that column.  It just clutters things up.  I can shrink the column  
>>> (which takes 15 to 20 seconds) but cannot turn it off.
>> Apparently not (you could file a wishlist bug to allow deselecting  
>> it.)  Oddly, I can adjust the width of other columns, but not the  
>> Detail column.  It seems to me that the Detail column just gets the  
>> leftover width after all the other columns are displayed.  That is  
>> definitely an odd behavior.
>> 
>>> I have not looked any further.  This is unusable, a complete fail.   
>>> I cannot go back because Fedora does not offer a 5.1 package for  
>>> F43. Flatpacks are not acceptable.  I have had far too many  
>>> problems with them.  Same with snaps.  An appimage might be OK if  
>>> one were offered.
>> 
>> Why are flatpaks not acceptable?  At least try one for testing to  
>> see if the problems appear there also.  You can also try (if only  
>> for testing) an Appimage or Snap version.
>> 
>> These fails are not (or at least not entirely) in the code for  
>> KMyMoney, as many other users are not having the same problems.  I'm  
>> still not sure where or why they show up for you.  One thing you can  
>> to is check your System Settings application to see if there are any  
>> setting which might confuse single vs. double clicking the mouse.   
>> (No, I do not expect anything here, but it's worth checking.)  I  
>> might als post on a Fedora forum or list, to see if any other Fedora  
>> users are seeing the same issues.  One additional question - are you  
>> using a full KDE Plasma desktop, or only those pulled in as  
>> dependencies?  If the latter, I wonder if teh Fedora build might be  
>> missing one or more Qt or KDE dependencies.  Also not likely, as I  
>> would expect a crash or error message.  Finally, please try  
>> launching KMyMoney from command line, and see if there is any useful  
>> information output to the console.
>> 
>> The behaviour you complain about is indeed not normal, but it may  
>> take some effort to identify the cause.
>> 
>> Jack
>