[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs with history memory active
https://bugs.kde.org/show_bug.cgi?id=478818 Nate Graham changed: What|Removed |Added Summary|Typing konsole in the |Typing konsole in the |Search bar of the |Search bar of the |Application Launcher menu |Application Launcher menu |showed kkonsole the first |showed kkonsole the first |time in GNOME Boxes VMs |time in GNOME Boxes VMs ||with history memory active CC||alexander.loh...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs
https://bugs.kde.org/show_bug.cgi?id=478818 --- Comment #6 from Matt Fagnani --- In System Settings > Search > Plasma Search > Configure KRunner, History was set to Enable Suggestions by default. I changed History to Disabled on several GNOME Boxes VM boots before searching, and the problem didn't happen. The Enable Suggestions setting for History of KRunner doesn't appear in my Plasma 5.27.10 installation, so it might be new. The search suggestions based on history might be the reason for the problem. I saw the problem in Plasma 5.91.0 on bare metal, so this might not be specific to GNOME Boxes VMs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs
https://bugs.kde.org/show_bug.cgi?id=478818 --- Comment #5 from Matt Fagnani --- The problem happened for more searches than I thought. Typing ae showed aae and ag showed aag while there aren't programs started with ae or ag shown in the menu. Typing aa showed aa so the two first letters might need to be different. The problem also happened when I ran plasmawindowed org.kde.plasma.kickoff in Plasma 5.91.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs
https://bugs.kde.org/show_bug.cgi?id=478818 --- Comment #4 from Matt Fagnani --- I found that searching for the first two letters which are prefixes of multiple programs names showed the doubled first letter problem. Searching for co showed cco and Contact Theme Editor, Contact Print Theme Editor, Connection Preferences, Colors are shown in the menu with co Searching for kd showed kkd and KDE Partition Manager, KDE Connect (SMS), KDE Wallet are shown in the menu with kd Searching for fi showed ffi and Filelight, Firewall, Firefox...are shown in the menu with fi I prevented plasma-baloorunner.service from running with sudo systemctl mask --user plasma-baloorunner.service, but the problem still appeared. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs
https://bugs.kde.org/show_bug.cgi?id=478818 --- Comment #3 from Matt Fagnani --- Searching for ko showed kko the first time in GNOME Boxes, but typing k just showed k with no results. There were Konsole, Kontact, KOrganizer, and Kolourpaint in the results when I corrected it to ko. I haven't seen this problem with other search strings. There were many spice-vdagent errors in the journal when using GNOME Boxes which I reported at https://bugs.kde.org/show_bug.cgi?id=478019 I stopped spice-vdagent before searching for ko with sudo systemctl stop spice-vdagentd.service spice-vdagentd.socket, but kko was still shown. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs
https://bugs.kde.org/show_bug.cgi?id=478818 Matt Fagnani changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Matt Fagnani --- (In reply to Nate Graham from comment #1) > Sounds a bit like the system was under some load or hadn't fully finished > the VT switch, resulted in the first "K" being repeated. Does the same thing > happen if you type it into KRunner itself? Does it ever happen outside of > the context of a VT switch? The problem didn't happen when I pressed alt+f2 and typed konsole into KRunner on a few VM boots. I don't usually use KRunner that way so I might just have missed it. I've seen the problem at least 20 times in VMs in the last 2-3 weeks sometimes a few minutes after the VT switch and when the system was idle otherwise. The probem might be specific to GNOME Boxes as it didn't happen in virt-manager QEMU/KVM VMs with the same settings and images. The plasma-baloorunner.service starting at the same time as the problem with the errors looked like it might be involved somehow though. The errors like kf.runner: Error requesting matches; calling "org.kde.runners.baloo" : "org.freedesktop.DBus.Error.NotSupported" "" don't happen in Plasma 5.27.10 on bare metal for me. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478818] Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs
https://bugs.kde.org/show_bug.cgi?id=478818 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- Sounds a bit like the system was under some load or hadn't fully finished the VT switch, resulted in the first "K" being repeated. Does the same thing happen if you type it into KRunner itself? Does it ever happen outside of the context of a VT switch? -- You are receiving this mail because: You are watching all bug changes.
