For KMyMoney running in Arch KDE Plasma 5.24.3 & older X11 sessions, this problem does not arise, ie, afaik all standard RMB context-menus function as expected.

For KMyMoney running in Arch KDE Plasma 5.24.3 & older Wayland sessions, this problem occurs.

It might arise more broadly throughout KMM in Wayland, but i noticed it specifically as follows. In the Category view, to be able to then jump directly to the corresponding Account view for an item of interest, the RMB context-menu is useful... but it simply does not work at all in Plasma Wayland … the context menu literally does not appear at all. That’s true in Plasma Wayland sessions with my normal launcher `kmymoney`, but sadly also true when I try to force KMM to run as a Wayland app via `QT_QPA_PLATFORM=wayland kmymoney`.

Here's a picture, taken within an X11 session, showing the menu which does not appear in Wayland.



Is this a bug, or instead simply that KMM has not yet been "Waylandised"?

"Waylandisation" should happen on the Qt Library level and should not be relevant for an application. On the other hand, it could well be, that the way KMyMoney uses Qt does not work well under Wayland but is working on X11 and Windows at the same time.

To further investigate, I suggest that you try the stable AppImage. I expect this to show similar behavior. What I would be interested is to know, if the same behavior is also visible when using the current development AppImage version.

Looking forward to your findings.

Thanks for the fast reply, & the shrewd testing suggestion.

Oh, btw, i forgot to state my KMM# in my OP ... 5.1.2-5.

Looking forward to your findings

Well, they are quite interesting, i think. As i dislike all non-repo packaging systems [AppImmage, Flatpak, Snap, whatever], i wasn't willing to install those files you suggested in my real Arch KDE, so i fired up one of my Arch KDE VMs & tested them there, with both X11 & Wayland. I found these results:

kmymoney-5.1-53-linux-centos_64-gcc.AppImage = Version 5.1.2-78fde521b
- RMB context-menu X11 = Good.
- RMB context-menu Wayland = None.

kmymoney-master-55-linux-centos_64-gcc.AppImage = Version 5.1.80-e2dc68d07
- RMB context-menu X11 = Good.
- RMB context-menu Wayland = Good.

That last result was a pleasant surprise, as was also, tbh, the several very interesting UI design changes i noticed in that version, heehee [do you have to shoot me now?].

Does this mean, essentially, that my solution will be for me to sit tight & patiently await the next KMM stable release, after which i'll be able to return to Wayland but still enjoy full KMM functionality? Otoh i suppose i could reverse my package principles & begin using that AI right now in my real system... albeit not being a stable version would make me uncomfortable to trust all my real data to it for daily use.

Thanks for the detailed report. The results are - as you say - surprising, though I hoped for them to come out as they did (stable showing the failure and master working). It definitely proofs that there is a difference between the way context menus are opened in both versions and that this affects operation under Wayland. Now, we just have to find out what this difference is.

The stable AppImage comes to help here as it is build daily and can be used OOTB. I count on you for some more testing ahead. ATM, I would not want to recommend to use master (aka. development or unstable) even if it is the only version with the working context menus under Wayland and the new features. As you mention: you're data might be at risk

BTW: do you experience the problem only in the transactions view or also in any of the other views (accounts, schedules, report, ...)?

BTW: do you experience the problem only in the transactions view or also in any of the other views (accounts, schedules, report, ...)?

I've just finished testing, with more interesting results.

kmymoney-5.1-53-linux-centos_64-gcc.AppImage = Version 5.1.2-78fde521b

- RMB context-menu Wayland per section:

Institutions, Scheduled Transactions, Ledgers, Reports = Good.
Home, Accounts, Categories, Tags, Payees = None.

NB: An amazing accidental discovery: If i invoke the RMB context-menu in the Scheduled Transactions view, then immediately change to the Accounts or Categories views, the RMB context-menu then works there, once. To make it work a second time, i need to repeat that process. This trick does not work for the Home view.
Update: No, i was partly incorrect. In fact, simply changing the active view is what allows the one-time-only appearance of the context menu, in Accounts or Categories views. This trick does not work for the Home, Tags, Payees views.
Update2: Sigh, i don't understand what's going on with Ledgers. Earlier, it seemed to work, but now it seems to entirely fail [ie, produce no context-menu]... maybe i was wrong before? So, either it does not work at all, or, it only works sometimes. It is unreliable at best, failed at worst.


kmymoney-master-55-linux-centos_64-gcc.AppImage = Version 5.1.80-e2dc68d07

- RMB context-menu Wayland per section:

Institutions, Accounts, Scheduled Transactions, Categories, Tags, Payees, Ledgers, Reports = Good.
Home = None.

Hence, overall, the future looks quite promising, once the improved code trickles down from development to stable. To ask you an unfair question, do you have any idea of the possible timing please?

The KDE Wayland Porting Notes may provide some hints on what could be the cause to your findings. In KMyMoney, the context menus all have a parent widget (both in stable and master). I know that there is a difference of using the position though when opening the menu between the two versions and that could very well explain it.

steffie wrote:Hence, overall, the future looks quite promising, once the improved code trickles down from development to stable. To ask you an unfair question, do you have any idea of the possible timing please?

I somehow knew that this question would reach the surface As all the work on KMyMoney is happening on a voluntary basis I can't really tell. I try to use master as much as possible already myself and so far things look good. We probably need some more testing to finish it up and release it as the next stable version.

I somehow knew that this question would reach the surface

Haha, as much as you anticipated my question, i easily anticipated your reply. 😜 Oh well, for now obviously i have no choice but to keep using my current Stable version, but i'll keep my fingers crossed for the next update. Thanks.