SUMMARY The usual way to customize an application is to copy its .desktop file to ~/.local/share/applications and modify it there. It seems that Plasma doesn't check for a copy of org.kde.krunner.desktop in ~/.local/share/applications and always uses the "factory" copy in /usr/share/kglobalaccel. STEPS TO REPRODUCE 1. `cp /usr/share/kglobalaccel/org.kde.krunner.desktop ~/.local/share/applications` 2. Edit the override file to set `Exec=env QT_QUICK_BACKEND=software /usr/bin/krunner` in an attempt to work around #455913 3. Log out & in OBSERVED RESULT The symptom of #455913 manifests, indicating that the ~/.local copy of the desktop file was not taken into consideration when starting krunner. (It has been already experimentally determined that killing krunner and re-running it manually with the workaround applied _does_ alleviate the symptom on this system). EXPECTED RESULT The symptom of #455913 should not manifest, because the workaround should be in effect as a result of the ~/.local/share/applications/org.kde.krunner.desktop override file being used by Plasma to launch krunner, instead of the "factory" file. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B24 System Version: 2.0
This is sort of expected. KRunner is not launched through the desktop file. To customize the launch behavior you can edit the relevant systemd unit via "systemctl --user edit plasma-krunner.service"