GNOME Bugzilla – Bug 758333
unable to add Google account as lost keyboard focus when Google Apps requests Kerberos credentials
Last modified: 2017-01-06 18:00:14 UTC
Created attachment 315880 [details] Screenshot of the window that does not have keyboard focus When using the "Sign in with your Google Account" form, after clicking "Sign in" button the pop-up window activates "The site google.company.xyz:443 requests a username and password" Server message: XYZ Google Apps Username: Password: [ ] Remember password Cancel / OK Basically this is GSSAPI (Kerberos) thing, and I have the valid Kerberos login set and active. The problem is that whatever I am trying to type in the active Username field -> gets retyped in the parent window "Sign in with your Google Account". And even though the pup-up window looks active, no elements are clickable. So it looks like it completely lost the keyboard focus. I've tried 'xprop', 'xdotool', etc.. to regain the focus, with no success... arno@lenovo:~$ wmctrl -lx |grep gnome-control 0x01c00011 0 gnome-control-center.Gnome-control-center lenovo Online Accounts 0x01c01463 0 gnome-control-center.Gnome-control-center lenovo Google account 0x01c024ec 0 gnome-control-center.Gnome-control-center lenovo arno@lenovo:~$ for i in $(wmctrl -lx |grep gnome-control|awk '{print $1}'); do xprop -id $i _NET_WM_STATE; done _NET_WM_STATE(ATOM) = _NET_WM_STATE_FOCUSED _NET_WM_STATE(ATOM) = _NET_WM_STATE_MODAL, _NET_WM_STATE_SKIP_TASKBAR _NET_WM_STATE(ATOM) = _NET_WM_STATE_SKIP_TASKBAR I've tried to "override" the setting by sending the: xprop -id 0x01c024ec -f _NET_WM_STATE 32a -set _NET_WM_STATE "_NET_WM_STATE_FOCUSED" However, no success. Any idea what can I try? what signal to send or alternative ways to work this problem around (e.g. CLI commands to setup the gnome online account) ? Thanks a lot in advance.
The problem here was that libsoup didn't support GSS-Negotiate, which meant that webkitgtk+ couldn't authenticate with your Kerberos token to the website. That support is now in place and sites like these should now work. *** This bug has been marked as a duplicate of bug 587145 ***