Version: SVN HEAD (using KDE 4.3.5) OS: Linux Installed from: openSUSE RPMs After https://bugs.kde.org/show_bug.cgi?id=234113 has been fixed, we face a new problem: the main 'Settings' menu and the context menu for transactions in the ledger view are gone. I have no idea why that is. Guess it's time to find someone with some more knowledge about KXMLGuiClient.
Addon: these items are gone after a change of the toolbar as described in the referenced bug.
I would close this as a KXMLGuiClient bug since although the behaviour described by you is correct it is only observable until the application is restarted after that everything is OK.
But why does all this work within other applications? We seem to trigger something here and I like to know what it is.
(In reply to comment #3) > But why does all this work within other applications? We seem to trigger > something here and I like to know what it is. kmymoney(3754) KXMLGUI::ActionList::plug: Index 66 is not within range (0 - 29) I see all kinds of warnings like this but it seems to me that are internal to KXMLGUI code. The whole toolbar configuration dialog is KXMLGUI code. See https://projects.kde.org/projects/kde/kdelibs/repository/revisions/master/entry/kdeui/xmlgui/kxmlguifactory_p.cpp#L39 it seems to me that data that is saved by KXMLGUI is not consistent when read back again.
We have this problem with KXMLGUI in KMyMoney: if the user configures the toolbar in a certain way the menubar mixes up the menus until the application is restarted. Steps to reproduce: 1. Open KMyMoney (you can use a testfile at kmymoney2.sourceforge.net/SampleKMyMoneyDataFile.kmy) 2. Configure the toolbar and add the 'Edit Splits' action to it 3. Close the toolbar editor and observer that the 'Settings' menu was moved as the third menu 4. Warnings like 'kmymoney(3754) KXMLGUI::ActionList::plug: Index 66 is not within range (0 - 29)' are printed during this process We would like to know if we don't use the API in the 'right way'. feel free to ask for any other info. This bug is in kdeui component but I can't edit the component of the report.
*** This bug has been marked as a duplicate of bug 64754 ***