Summary: | Search does not work at times | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Filip Fila <filipfila.kde> |
Component: | Application Launcher (Kickoff) | Assignee: | David Edmundson <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | plasma-bugs |
Priority: | NOR | ||
Version: | 5.14.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Filip Fila
2018-12-21 12:46:26 UTC
I don't suppose there's any relevant command line output? I can't reproduce, which makes this quite difficult without any other info. If possible (and I know this is a big ask) can you attach gammaray, and introspect the relevant model to see if it's updating? Yeah, I wish I could figure out what causes it. If I keep mashing Meta and then start typing something, that doesn't seem to be triggering it at all. For the time being I've reproduced it with plasmashell running in the terminal. There was no output, just the ordinary: "org.kde.plasmaquick: Applet "Application Launcher" loaded after 0 msec "org.kde.plasmaquick: Increasing score for "Application Launcher" to 100" I'll try to set up gammaray and get the info, I haven't used it before. I've realized this is still of importance for LTS releases even if it may have been somehow inadvertently fixed in 5.15 so I'll focus on gammaray instead of testing with git Kickoff. *** This bug has been marked as a duplicate of bug 401861 *** |