Using KRDC to connect to a remote host, I frequently run into a problem with
keyboard focus (or the program just ignores the keyboard - same effect).
What happens is that I fire up KRDC and select (or enter) a site to connect
to. Generally, I get a popup wanting a password to open the wallet or the
password for the selected site. The failure is that the popup will not
accept keyboard input - the keyboard is ignored completely. The problem
exists only within KRDC environment only. Once I do get the password/login
popup to accept keyboard input, that session of KRDC has no further problems
with the keyboard for days on end.
Does this sound familiar to anyone? I can’t see any repeatable pattern
leading to this situation but it can be a real PITA getting keyboard access
restored to KRDC when it does happen.
Will Honea wrote:
> Using KRDC to connect to a remote host …]
> …] Generally, I get a popup wanting a password to open the wallet…]
> The failure is that the popup will not accept keyboard input …]
on a first looks this does not look like a bug in KRDC to me:
the kwallets password dialog is fired and controlled by the wallet manager,
KRDC just asks the manager via D-Bus for an entries content.
Typically I see problems like this with unnoticed additional popups
(somewhere in the background), popups like warnings or errors that act in a
modal way, want to be accepted first and thus grabbing the keyboard focus.
> Hello,
>
> Will Honea wrote:
>> Using KRDC to connect to a remote host …]
>> …] Generally, I get a popup wanting a password to open the wallet…]
>> The failure is that the popup will not accept keyboard input …]
>
> on a first looks this does not look like a bug in KRDC to me:
> the kwallets password dialog is fired and controlled by the wallet
> manager, KRDC just asks the manager via D-Bus for an entries content.
>
> Typically I see problems like this with unnoticed additional popups
> (somewhere in the background), popups like warnings or errors that act in
> a modal way, want to be accepted first and thus grabbing the keyboard
> focus.
That was my first thought as well but I couldn’t find any pending popups. I
did finally hit on a usable way to break the deadlock - whatever it is - by
simply switching to a command line session (alt-ctl-F1) and back.
Strange problem: nothing obviously consistent about when or if it occurs
that I can see other than being on the first call with kwallet not open yet.