https://bugs.kde.org/show_bug.cgi?id=505876
--- Comment #6 from [email protected] --- I tried putting in some debugging effort and couldn't find the cause of the issue, but what I did find is that the AppMenuModel does appear to have the correct internal state, including when searching in response to keyboard input. Logging the m_currentSearchActions for each keystroke shows the correct results. From what I can tell, the issue seems to be somewhere between adding the actions to the searchAction menu and displaying the menu on the screen, or signaling that the state has changed. -- You are receiving this mail because: You are watching all bug changes.
