Authentication Required window frozen Ubuntu 20.04
I use 1password extension with Firefox (v92.0). It has been working great. Whenever I require it I'd just press the keyboard shortcut and a window pops out (in the centre of screen) prompting to enter my password of my Ubuntu login -- lets call this authentication box. If it does this, everything should be fine. I'd put my PC (not laptop) into suspend mode and return to it normally.
However, there have been a few occasions now when I have to unlock 1password extension, the 1password app launched and prompted me for my 1password password. This is not the same authentication box. The main application opens.
From this point on, if I put my machine to suspend and logs back in, the above-mentioned authentication box appears frozen at the top-left of my screen. I cannot click it off -- hovering the mouse of the Cancel button highlights the button but clicking it does nothing. I can, however, click any where within the popup window and interactive with any objects or links below it even though the popup is opaque. See screenshot..
Notice the cancel button? If the Visual Code Studio icon below it is on the same row as the password field, clicking it will launch the VSCode application.
The point here is that this popup window cannot be moved, removed, resized, etc. As the popup sits above all layers, it is obstructing everything else below it. The only thing I can do to is to log off Ubuntu and back in.
Any tips?
1Password Version: 8.2.0
Extension Version: 2.1.2
OS Version: Ubuntu 20.04
Comments
-
Hi @yallneedpswd_mgr, that does sound like a strange issue, and your description here gives us a great start on troubleshooting what might be at the root of it.
I'd love to investigate this further for you. If you can send a quick email to support+linux@1Password.com, we'll get started looking at some of the potentially relevant system specifics. Be sure to include a link to this discussion so that we know it's you - and I'll look forward to helping you out over there!
0 -
Hi @PeterG_1P
Sent that email.While I still have you here, do you (or anyone reading this) know what might be the process ID for the authentication required box is in the terminal?
$ ps -faux | grep -i 1password$ ps -faux | grep -i 1password foobar 275534 0.0 0.0 1293776 10504 ? Sl 10:55 0:00 | \_ /opt/1Password/1Password-BrowserSupport /home/dantvli/.mozilla/native-messaging-hosts/com.1password.1password.json {d634138d-c276-4fc8-924b-40a0ea21d284} foobar 275552 0.0 0.9 38328912 152232 ? Sl 10:55 0:03 | | \_ /opt/1Password/1password --silent foobar 275555 0.0 0.2 213116 46048 ? S 10:55 0:00 | | | \_ /opt/1Password/1password --type=zygote --no-zygote-sandbox foobar 275591 0.0 0.6 514044 104976 ? Sl 10:55 0:00 | | | | \_ /opt/1Password/1password --type=gpu-process --field-trial-handle=16872656061184102403,4446034835829616376,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --gpu-preferences=UAAAAAAAAAAgAAAQAAAAAAAAAAAAAAAAAABgAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAACAAAAAAAAAA= --shared-files foobar 275556 0.0 0.2 213116 45692 ? S 10:55 0:00 | | | \_ /opt/1Password/1password --type=zygote foobar 275558 0.0 0.0 213116 12060 ? S 10:55 0:00 | | | | \_ /opt/1Password/1password --type=zygote foobar 275625 0.0 0.3 279804 54976 ? Sl 10:55 0:00 | | | \_ /opt/1Password/1password --type=utility --utility-sub-type=network.mojom.NetworkService --field-trial-handle=16872656061184102403,4446034835829616376,131072 --disable-features=CookiesWithoutSameSiteMustBeSecure,SameSiteByDefaultCookies,SpareRendererForSitePerProcess --lang=en-GB --service-sandbox-type=none --standard-schemes=resource,file-icon --enable-sandbox --secure-schemes --bypasscsp-schemes=resource,file-icon --cors-schemes --fetch-schemes=resource,file-icon --service-worker-schemes --streaming-schemes --shared-files=v8_context_snapshot_data:100 foobar 275626 0.0 0.0 614380 9596 ? Sl 10:55 0:00 | | | \_ /opt/1Password/1Password-KeyringHelper foobar 275601 0.0 0.0 614396 9584 ? Sl 10:55 0:00 | | \_ /opt/1Password/1Password-KeyringHelper foobar 307098 0.0 0.0 9036 740 pts/0 S+ 22:08 0:00 | \_ grep --color=auto -i 1passwordIf it is known, I imagine it'd be a straight-forward
$ kill -9 the-pid-number0 -
Hi @yallneedpswd_mgr, I've replied to your email and will plan to continue the conversation over there, to keep everything in one place. Good to connect with you!
ref: GXK-18787-533
0 -
Just want to state that I regularly experience this, too, and I have to log out and back in again in order to make it disappear, which is frustrating and disruptive.
Please post back here when you have more information about this issue or when it may be fixed - or let me know if there's anything I can do to help in this regard.
0 -
Hi, folks. This is a new one to me.
But, the "Authentication Required" window above is part of Gnome-Shell, not 1Password. For that form of authentication, we actually send a message over to Gnome-Shell to handle it.
Now, I did encounter a StackOverflow issue that seems related, and is even on Ubuntu 20.04: https://askubuntu.com/questions/1291732/authentication-required-window-stuck-after-login
It looks like you can do a
killall -3 gnome-shellto kill gnome-shell. If you're on X11, gnome-shell should automatically restart, and you should still have all of your windows since X11 itself didn't shut down. That's a big emphasis on "should" though, and potentially wouldn't in all use cases.I don't know how this will work out if you're on Wayland. I'll chat with the support team to see what other information they have and maybe brainstorm up a way to reproduce this myself.
0 -
I'm also experiencing this issue (on Ubuntu 20.04).
Savanni's suggestion above (
killall -3 gnome-shell) does work, but it keeps happening regularly, so I suspect there is something wrong in the implementation somewhere.I think it only happens after returning to my computer after a while (ie. unlocking after a few hours).
The prompt being positioned at 0,0 (rather than the proper center-of-screen) does suggest something is being called with the wrong parameters or before something in X is ready.
Also, maybe relevant: I have two monitors.
0 -
This does seem to be an upstream bug¹ that was fixed in gnome-shell². Ubuntu is tracking the issue³ and has backported the fix into hirsute (21.04)⁴ but the fix has not (yet 🤞) been backported into focal (20.04).
0
