https://bugs.kde.org/show_bug.cgi?id=3D221107

--- Comment #21 from Thomas L=C3=BCbking <thomas.luebking@gmail.com> ---
(In reply to comment #20)
> Could it be that it's Konsole's fault?

There's no "fault" - and certainly not the one of the subprocess.
To kwin the scenario looks like konsole was trying to steal the focus from
(foreign/unrelated) dolphin, what's therefore denied.

Unless you have access to the spawned windows id (to set some relation hint,
like altering the client leader or even make konsole a transient for dolphi=
n -
depending on what is intended) my only idea was to "fake" what the newly
instanciated process probably "accidentally" does to workaround the problem:
delay the call, ie bind the action to a slot

::deferSpawningKonsole() {
   m_konsoleSpawnTimer->start(300); // 400? 500?
}

This solves tow issues for one:
1. The user probably meanwhile released the key "for a while" when the kons=
ole
window finally appears, thus it should be granted the focus.
2. You won't run into "issues" caused by automatic key repetition (ie. keep=
ing
Shift+F4 pressed and spawn a hundred konsole windows) - if the delay is abo=
ve
the keyboards repeat rate.

--=20
You are receiving this mail because:
You are watching all bug changes.=