I found another issue like this but not the same as in this instance krunner is managed by a systems user service. I haven't found the way to reproduce it yet but krunner will not open with Alt Space shortcut. Checking the systemd service log when I try it, I get one entry which is krunner[157007]: QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
Just to add, restarting the systemd user service fixes the issue for a while.
>Checking the systemd service log when I try it, I get one entry which is Do you get that only once? Also, please check if calling the DBus method manually works (when you currently experience the bug): ` qdbus org.kde.krunner /App org.kde.krunner.App.display`
(In reply to Alexander Lohnau from comment #2) > >Checking the systemd service log when I try it, I get one entry which is > > Do you get that only once? > > Also, please check if calling the DBus method manually works (when you > currently experience the bug): > ` qdbus org.kde.krunner /App org.kde.krunner.App.display` I get it each time I press the shortcut key. I'll wait for it to happen again and try the qdbus invocation.
OK I got it again and `qdbus org.kde.krunner /App org.kde.krunner.App.display` does nothing, a blank line is just printed in konsole
That is really weird, honestly it is out of scope for my knowledge. Maybe David Edmundson has any idea?
I experience this issue as well. If I do `strace -p $krunner_pid` I gues a **lot** of messages like: poll([{fd=5, events=POLLIN}, {fd=13, events=POLLIN}, {fd=54, events=POLLIN}, {fd=55, events=POLLPRI}, {fd=57, events=POLLIN}, {fd=99, events=POLLIN}, {fd=114, events=POLLIN}, {fd=128, events=POLLIN}, {fd=151, events=POLLIN}], 9, 499) = 0 (Timeout) And whenever I press the alt+space combination I guet: sendmsg(26, {msg_name={sa_family=AF_UNIX, sun_path="/run/systemd/journal/socket"}, msg_namelen=30, msg_iov=[{iov_base="MESSAGE=QCommandLineParser: argu"..., iov_len=105}, {iov_base="\n", iov_len=1}, {iov_base="PRIORITY=4", iov_len=10}, {iov_base="\n", iov_len=1}, {iov_base="CODE_FUNC=unknown", iov_len=17}, {iov_base="\n", iov_len=1}, {iov_base="CODE_LINE=0", iov_len=11}, {iov_base="\n", iov_len=1}, {iov_base="CODE_FILE=unknown", iov_len=17}, {iov_base="\n", iov_len=1}, {iov_base="QT_CATEGORY=default", iov_len=19}, {iov_base="\n", iov_len=1}, {iov_base="SYSLOG_IDENTIFIER=", iov_len=18}, {iov_base="krunner", iov_len=7}, {iov_base="\n", iov_len=1}], msg_iovlen=15, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 211 write(4, "\1\0\0\0\0\0\0\0", 8) = 8 sendmsg(3, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="J\0\0\0\2\0\24\0\1\0\0\0\0\0\0\0O\0\0\0", iov_len=20}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 20 So it seems like krunner does get the keystroke but it doesn't show up...