https://bugs.kde.org/show_bug.cgi?id=443131
--- Comment #19 from alk...@protonmail.com --- Note that I am not familiar with how Qt / Singletons work, however coming from a developers perspective I can roughly tell what's happening by observing the behavior. (So take the following with a grain of salt) The current behavior from the Application Launcher is to bind the search item to the content area. For this, user input (keyboard) is being delegated to that search item and search result content is being displayed. Adding a second Application Launcher, which is a different object, now maybe restores the binding between itself and the existing search item from the first Application Launcher. Now user input from the first Application Launcher seems to be delegated to the search item, which is now bound to the second Application Launcher. This results in the observed behavior, that writing something in the first Application Launcher is not seen there, yet visible in the second Application Launcher. The search object is not bound to the first launcher anymore, that's why we see the message: "ApplicationsPage.qml:118: TypeError: Cannot read property 'forceActiveFocus' of null". It could also be, that it's some issue with the search bar in Header.qml or it could be that only one global searchView is being created. Of course, this can be all wrong, but I think it might be something related. Sorry for the wall of text. -- You are receiving this mail because: You are watching all bug changes.
