alt-f2 stops working and doesn't bring up krunner

[lexual]

Binary package hint: kdebase-runtime

alt-f2 stopped working (didn't pop up run dialog)
alt-f1, alt-f3 continued to work.

This is with 4.4 kde packages from lucid.

running krunner manually from command line corrected the problem.

Maybe krunner crashed without restarting itself?

[Daniel K (sinani201)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Jonathan Thomas (echidnaman)]

Yeah, krunner probably crashed. Is this issue reproducible? It'd help to get a backtrace of the krunner crash.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!

[Joseph S Tate (jtate)]

This is happening to me as well; after some period of time, krunner no longer responds to Alt-F2. It has happened twice since I upgraded yesterday afternoon, so I'm sure it will happen again.

There is no crash report because krunner is still running according to ps. If I killall krunner, and then run it from the kicker menu, it works again for a while.

There's nothing that I can see in .xsession-errors to indicate a problem.

Anything else I can provide to help debug this?

[Jonathan Thomas (echidnaman)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

[Joseph S Tate (jtate)]

Following this bug at https://bugs.kde.org/show_bug.cgi?id=213907