You are not logged in.
Searching for something in krunner produces the following output:
Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
Error contacting the daemon!
org.kde.kurifilter-ikws: ":q"
org.kde.kurifilter-ikws: Keywords Engine: Loading config...
org.kde.kurifilter-ikws: Web Shortcuts Enabled: true
org.kde.kurifilter-ikws: Default Shortcut: ""
org.kde.kurifilter-ikws: Keyword Delimiter: :
session switching to "kickstart my heart"
Xapian::Query((NAkickstart:(pos=1) OR NAmy:(pos=2) OR NAheart:(pos=3) OR kickstart:(pos=1) OR my:(pos=2) OR heart:(pos=3)))
PIMContactsRunner(0x3b06220, name = "PIMContactsRunner") MATCH: queryAutocompleter = true
session switching to "kru"
KCrash: Attempting to start /usr/bin/krunner from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: Application 'krunner' crashing...
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
Unable to start Dr. Konqi
This results in the program crashing and restarting itself.
A similar issue happens when searching for anything in the Plasma Application Launcher.
Offline
You should generate a backtrace and eventually post it to bugs.kde.org
Do you know how to use gdb?
Offline
Not really. How could I go about doing this?
Offline
Given that you'll probably need to install/build some packages, you could try starting with runnin plasmashell with gdb and see what happens when you cause the error:
kquitapp5 plasmashell
gdb plasmashell
then, from the gdb prompt, tun
run
One you got the crash you could run (from the gdb prompt):
bt
to get the backtrace
Offline