Please provide the software versions and system information as instructed by the default template (the output of "kinfo" should be good enough).

We also need you to be more specific about how exactly it is not working - does it not show up at all? Can you not type into it? Can you type but nothing happens? Does something happen, but it's the wrong thing? etc.

Can you create a new user account and see if it works there?

It shows up, but I can't type into it.

kinfo:
```
> kinfo
libEGL warning: egl: failed to create dri2 screen
Operating System: EndeavourOS
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.6-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor 1: Mesa Intel® UHD Graphics
Graphics Processor 2: zink Vulkan 1.4
```
Weirdly, it just snapped back into working for me after my browser crashed (but still works now that I've reopened it). It seems to switch between working and not working randomly. However, I *suspect* (but couldn't prove to you) it's because there's some kind of input (e.g. an authentication prompt) open somewhere that I couldn't find, and this makes it impossible to type into krunner (in which case the browser crashing might have killed the prompt).

What browser is it?

Nevermind, browser doesn't seem to be the issue—it keeps happening even without having a browser on. Seems to be "random" and I can't work out what it is causing this.

Hi - while this is happening, are you able to type into other fields in Plasma, like the search box in the Application Launcher?

Could you also please open a terminal and run `sudo journalctl --follow`, trigger the issue, then press Ctrl+C and copy/paste the resulting logs into a comment here?

Thanks!

(In reply to John Kizer from comment #5)
> Hi - while this is happening, are you able to type into other fields in
> Plasma, like the search box in the Application Launcher?
> 
> Could you also please open a terminal and run `sudo journalctl --follow`,
> trigger the issue, then press Ctrl+C and copy/paste the resulting logs into
> a comment here?
> 
> Thanks!

I'm able to type into KRunner outside the overview animation (by opening it with alt+F2). I'll try to get you that info, but I can't reproduce the issue reliably (it seems to happen at random), so no guarantees.

(In reply to John Kizer from comment #5)
> Hi - while this is happening, are you able to type into other fields in
> Plasma, like the search box in the Application Launcher?
> 
> Could you also please open a terminal and run `sudo journalctl --follow`,
> trigger the issue, then press Ctrl+C and copy/paste the resulting logs into
> a comment here?
> 
> Thanks!
```
Journal file /var/log/journal/c18d0bcf56d24a0ab74df26adb0844d3/system@0006378eb6d25acc-315dec0256c3c5bb.journal~ is truncated, ignoring file.
Jun 21 15:04:14 lime-81y6 kwin_wayland[1233]: qml: Krohnkite: Screen(output):HDMI-A-1, Desktop(name):Desktop 2, Activity: 5d493f23-0686-412f-bc88-49fa59adb8b6, layouts: 0.spirallayout ,1.btreelayout ,2.threecolumnlayout ,3.stackedlayout ,4.tilelayout ,5.floatinglayout
Jun 21 15:04:27 lime-81y6 systemd[1166]: Started dbus-:1.2-org.freedesktop.Notifications@99.service.
Jun 21 15:04:29 lime-81y6 wpa_supplicant[926]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-61 noise=9999 txrate=351000
Jun 21 15:04:44 lime-81y6 wpa_supplicant[926]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-57 noise=9999 txrate=351000
Jun 21 15:04:52 lime-81y6 systemd[1166]: Started Alacritty - Terminal.
Jun 21 15:04:52 lime-81y6 alacritty[43695]: Created log file at "/tmp/Alacritty-43695.log"
Jun 21 15:04:52 lime-81y6 alacritty[43695]: [0.000361923s] [ERROR] [alacritty_config_derive] Config error: unknown keyboard action ``
Jun 21 15:04:52 lime-81y6 alacritty[43695]:                                                  ; ignoring binding
Jun 21 15:05:00 lime-81y6 sudo[43707]:     lime : TTY=pts/6 ; PWD=/home/lime ; USER=root ; COMMAND=/usr/bin/journalctl --follow
Jun 21 15:05:00 lime-81y6 sudo[43707]: pam_unix(sudo:session): session opened for user root(uid=0) by lime(uid=1000)
Jun 21 15:05:27 lime-81y6 plasma_waitforname[43683]: org.kde.plasma.waitforname: WaitForName: Service was not registered within timeout
Jun 21 15:05:27 lime-81y6 systemd[1166]: dbus-:1.2-org.freedesktop.Notifications@99.service: Main process exited, code=exited, status=1/FAILURE
Jun 21 15:05:27 lime-81y6 systemd[1166]: dbus-:1.2-org.freedesktop.Notifications@99.service: Failed with result 'exit-code'.
Jun 21 15:05:47 lime-81y6 wpa_supplicant[926]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=351000
Jun 21 15:07:07 lime-81y6 sudo[43611]: pam_unix(sudo:session): session closed for user root
Jun 21 15:07:07 lime-81y6 alacritty[43593]: Deleted log file at "/tmp/Alacritty-43593.log"
Jun 21 15:07:07 lime-81y6 systemd[1166]: app-Alacritty@bb14eb70c7f94912896ea582234106e9.service: Consumed 670ms CPU time, 457.1M memory peak, 36.6M memory swap peak.
Jun 21 15:07:58 lime-81y6 kwin_wayland[1233]: kwin_libinput: Libinput: event6  - MSFT0001:01 06CB:7F28 Touchpad: client bug: event processing lagging behind by 60ms, your system is too slow
Jun 21 15:07:59 lime-81y6 kwin_wayland[1233]: kwin_scene_opengl: Could not delete texture because no context is current
```
Not sure this output is very useful.

you mean typing in the overview effect to see krunner results?

(In reply to Marco Martin from comment #8)
> you mean typing in the overview effect to see krunner results?

setting this as waitingforinfo

For what its worth, when I open overview and start typing, I can see the results as expected.

Operating System: Fedora Linux 42
KDE Plasma Version: 6.5.80
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: AMD Radeon RX 6600

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!