4 ms·
What is your X session? Gnome/KDE or plain window manager? It might be, that your wm is not launching some service that wayland session is and 1password needs.
by vetinari 8y ago
What is your X session? Gnome/KDE or plain window manager? It might be, that your wm is not launching some service that wayland session is and 1password needs.
- pdpi 8y agoThe fact that you're asking this question and suggesting that root cause is itself a significant part of the problem the OP was talking about.
- vetinari 8y agoUnfortunately, the openness allows for so much flexibility, that many people end up breaking it up. Invariably, they will blame the system and not their changes. If they used the defaults, like they do in other systems, it would not happen.
- joombaga 8y agoIn this case though LastPass is broken in Firefox on Ubuntu by default. Edit: akiselev said 1Password, not LastPass. My mistake. Interesting that I experienced this same issue with LastPass.
- vetinari 8y agoIt turns out to be ubuntu bug: https://discussions.agilebits.com/discussion/90011/p1 https://discussions.agilebits.com/discussion/90011/p1
- akiselev 8y agoThis was a clean install so Gnome shell - worked just fine on Ubuntu 17.10 and 18.10 with X and Wayland. After I login through the 1password website, the extension window opens just fine so it might be some input security service, but how would a Firefox extension even have access to a system service like that except through Firefox's built in APIs?
- vetinari 8y agoI don't know how 1password works; I'm using keepassxc. With keepassxc you have native application and extension, that communicate together via socket. The native application can use whatever native APIs it wants. However, back to you. What's more weird, if it is pure Firefox Webextension, that Firefox (still by default) launches as X11 application under Wayland, so the extension should have no way to know the difference.