Bug 217318

Summary:	Alt+F2 brings up a deaden 'Run Program' dialog
Product:	[Plasma] krunner	Reporter:	Parameshwara Bhat <peebhat>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	aseigo
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Alt+F2 run Program Dialog

Description Parameshwara Bhat 2009-12-04 11:34:21 UTC

Version:           1.0 (using 4.3.1 (KDE 4.3.1) "release 6", openSUSE 11.2)
Compiler:          gcc
OS:                Linux (i686) release 2.6.31.5-0.1-desktop

When Alt+f2 is pressed,instead of the usual Run Command Dialog,I get a UI which accepts no key inputs.

I get the usual krunner if I go through klauncher-Run command menu.

If I press Alt+shift+F2 I get krunner with clipboard inputs.I tried getting rid of this new dialog by switching shortcuts,but that does not work.Whatever shortcut is assigned,Alt+F2 brings up this.

Comment 1 Parameshwara Bhat 2009-12-04 11:36:33 UTC

Created attachment 38825 [details]
Alt+F2 run Program Dialog

This happened only on this machine.Other machine where I installed opensuse,it did not happen.May be something to do with scim?

Comment 2 Ben Cooksley 2009-12-04 12:05:02 UTC

That isn't Plasma. Does it occur with a new user?
Also, did you ever compile KDE 4 whilst it was being ported to Qt4? Or install packages to this effect?

Comment 3 Parameshwara Bhat 2009-12-04 16:50:17 UTC

This is a brand new installation of opensuse 11.2,only a session old.

This occurs with a new user as well.

I never compiled KDE 4.

Comment 4 Parameshwara Bhat 2009-12-04 17:19:42 UTC

The problem disappeared as strangely as it appeared.

My first session after installation it appeared.I logged out and logged in for some other thing.I find this disappeared.

Let the bug report be there,I will return to it after a few more sessions and update

Comment 5 Parameshwara Bhat 2009-12-20 17:18:57 UTC

This comes back several times for apparently no reason.I have been unable to isolate any particular action or event causing it.

Comment 6 Aaron J. Seigo 2011-05-28 01:00:29 UTC

too old relative to the current code to be triagable.