Bug 210006 - focus doesn't return to app after alt+f2 run command
Summary: focus doesn't return to app after alt+f2 run command
Status: RESOLVED WORKSFORME
Alias: None
Product: krunner
Classification: Plasma
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Unspecified
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-10-09 19:00 UTC by David Rankin
Modified: 2018-10-21 04:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Rankin 2009-10-09 19:00:49 UTC
Version:            (using KDE 4.3.1)
Installed from:    SuSE RPMs

When you use alt+f2 to reach the run command and execute a command that runs in the background (like a script that mounts CIFS shares), focus does not return to application you were using when you pressed alt+f2.

This is unexpected behavior. If you are using an application (kwrite in this instance) and you use alt+f2 to run a script, then focus should return to kwrite once the command has completed -- but it does not.

The window title bar appears to have focus, but attempting to use any keyboard shortcuts (like ctrl+o to open a new file in kwrite) does nothing until you manually click the kwrite window again with the mouse. It is like kde4 is simply confused as to where focus should go. In this case, kwrite was the only application open in kde4 when the run command was executed. After executing the run command, the desktop appeared normal:

http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/runcmd-no-return-focus.jpg

But, as stated above, there was no focus for the keyboard in kwrite, so when I attempted to open a new file with ctrl+o, nothing happened. The keyboard was dead until I manually clicked the kwrite window with a mouse to give it focus again.
Comment 1 Jacopo De Simoi 2009-12-27 00:10:52 UTC
I can't reproduce here; is it still the case?
Comment 2 Jacopo De Simoi 2010-01-09 13:22:04 UTC
Please reopen if you can provide some more infos as I can't reproduce here and got no answer for >1 week
Comment 3 Andrew Crouthamel 2018-09-20 03:03:00 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-21 04:32:04 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

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