https://bugs.kde.org/show_bug.cgi?id=429435
--- Comment #16 from David Redondo <k...@david-redondo.de> --- So when krunner is started the first time after logging in via shortcut it shows the broken behavior? If I read this thread correctly, killing krunner and starting it from a terminal fixes it? What happens if after logging in krunner is started from terminal? What happens if after killing krunner, it is started via shortcut again? -- You are receiving this mail because: You are watching all bug changes.
