SUMMARY I booted Fedora Rawhide KDE Plasma live images in GNOME Boxes QEMU/KVM VMs in a Fedora 39 KDE Plasma installation. To work around the VM getting stuck on the Plasma 5.90.0 on Wayland splash screen as I reported at https://bugs.kde.org/show_bug.cgi?id=477643 I changed to VT2 using the keyboard menu in the top bar of GNOME Boxes and selecting Ctrl+Alt+F2. When I changed back to VT1, Plasma was shown with the Plasma Welcome program open. I opened the Application Launcher menu. I typed konsole in the Search bar of the Application Launcher menu. The Search bar showed kkonsole instead of konsole with no search results the first time I typed it. The journal at the time I typed konsole showed plasma-baloorunner.service starting and errors like plasmashell[1844]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo" : "org.freedesktop.DBus.Error.NotSupported" "" Dec 21 00:12:32 plasmashell[1844]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Dec 21 00:12:32 plasmashell[1844]: org.kde.plasma.runner.bookmarks: No default firefox profile found Dec 21 00:12:32 systemd[1412]: Starting plasma-baloorunner.service - KRunner provider for baloo file indexer... Dec 21 00:12:33 baloorunner[3000]: libEGL warning: egl: failed to create dri2 screen Dec 21 00:12:34 plasmashell[1844]: kf.kunitconversion: currency conversion table data obtained via network Dec 21 00:12:34 plasmashell[1844]: QObject::startTimer: Timers cannot be started from another thread Dec 21 00:12:34 baloorunner[3000]: MESA: error: ZINK: failed to choose pdev Dec 21 00:12:34 baloorunner[3000]: libEGL warning: egl: failed to create dri2 screen Dec 21 00:12:34 systemd[1412]: Started plasma-baloorunner.service - KRunner provider for baloo file indexer. Dec 21 00:12:34 plasmashell[1844]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo" : "org.freedesktop.DBus.Error.NotSupported" "" Dec 21 00:12:34 plasmashell[1844]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo" : "org.freedesktop.DBus.Error.NotSupported" "" Dec 21 00:12:34 plasmashell[1844]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo" : "org.freedesktop.DBus.Error.NotSupported" "" Dec 21 00:12:34 chronyd[1257]: Selected source 138.197.152.115 (2.fedora.pool.ntp.org) Dec 21 00:12:35 plasmashell[1844]: Found icon of unknown type 'unknown' in 'system/package/os/org.kde.latte-dock.desktop/*', skipping it. Dec 21 00:12:35 plasmashell[1844]: Found icon of unknown type 'unknown' in 'system/package/os/org.kde.discover.snap/*', skipping it. Dec 21 00:12:35 plasmashell[1844]: Found icon of unknown type 'unknown' in 'system/package/os/io.github.syllo.nvtop/*', skipping it. Dec 21 00:12:36 plasmashell[1844]: Found icon of unknown type 'unknown' in 'system/package/os/org.kde.kiten.desktop/*', skipping it. This problem always happened the first time I typed konsole in the Search bar in a VM's boot. I've seen this happened with 3D acceleration disabled using the llvmpipe mesa driver and 3D acceleration enabled using the virgl driver. STEPS TO REPRODUCE 1. Boot a Fedora 39 KDE Plasma installation updated to 2023-12-20 with updates-testing enabled 2. Log in to Plasma 5.27.10 on Wayland 3. Start Konsole 4. Install GNOME Boxes if it isn't already with sudo dnf install gnome-boxes 5. Download Fedora-KDE-Live-x86_64-Rawhide-20231220.n.0.iso from https://koji.fedoraproject.org/koji/buildinfo?buildID=2335875 6. Start GNOME Boxes 7. Boot Fedora-KDE-Live-x86_64-Rawhide-20231220.n.0.iso in a GNOME Boxes QEMU/KVM VM with 3 GiB RAM, UEFI enabled, and 3D acceleration disabled or enabled 8. To work around https://bugs.kde.org/show_bug.cgi?id=477643, switch to VT2 in GNOME boxes via the keyboard menu Ctrl+Alt+F2 and back to VT1 with Ctrl+Alt+F1 after the Plasma 5.90.0 splash screen is shown for several seconds 9. Open the Application Launcher menu 10. Type konsole in the Search bar of the Application Launcher menu OBSERVED RESULT Typing konsole in the Search bar of the Application Launcher menu showed kkonsole the first time in GNOME Boxes VMs EXPECTED RESULT Typing konsole in the Search bar of the Application Launcher menu should have shown konsole SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Rawhide/40 (available in About System) KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION This problem didn't happen subsequent times I typed konsole in the VMs' boots. The problem didn't happen on bare metal. Plasma 5.27.9 didn't have this problem.
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?
(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.
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.
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.
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.
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.
Is this still happening in a recent version of Plasma, like 6.2.5 or later?
I haven't seen this problem in recent versions up to Plasma 6.2.90.
Thanks for following up. Let's call it fixed.
I saw this problem again with Plasma 6.2.90 in a QEMU/KVM VM in GNOME Boxes using a Fedora Rawhide live image. I guess it just happened less often than originally.