[SOLVED] 1Password on Bazzite
In the past, I've been able to get 1Password browser integration with Vivaldi by following this post here: https://forum.vivaldi.net/topic/91288/1password-extension-doesn-t-unlock-in-step-w-the-1password-desktop-application
which outlines adding the file
/etc/1password/custom_allowed_browsers and putting vivaldi-bin into the file. This has not worked for me yet in Bazzite. Both 1Password and Vivaldi are installed with layering, so they should be able to communicate properly, as there's no sandboxing. Can anyone help me understand what's going on?Vivaldi Forum
1Password extension doesn't unlock in-step w/ the 1Password desktop...
Note: These instructions are for the Linux desktop, but this issue will occur on all platforms. I just don't have a solution for Windows or Mac or anything e...
Solution:Jump to solution
Here's what I think happened.
1. I installed 1Password using the .rpm file.
2. It created a symlink for /opt/1Password, possibly due to how the atomic distro works, or maybe that's just normally how this gets installed
3. I then uninstalled 1Password, but the symlink was left behind (broken) (I can't remember why I did this)
4. I re-installed 1Password, but using the tar method. This overwrote the symlink, as it's a manual process...
10 Replies
I've gone ahead and sent an email to 1Password to see if they have any ideas, as even Firefox, one of their supported browsers, does not work. (I layered firefox on)
Have you tried using the flatpak version of 1Password with the flatpak of Vivaldi? https://support.1password.com/install-linux/#flatpak
the flatpak versions are specifically unsupported for that feature
I use all three of those features 😂
and the last two actually work perfectly ootb, it's just the browser unlock that's not working
@Kyle Gospo is there any reason I shouldn't change
kernel.yama.ptrace_scope to 1? The 1password support team is suggesting to do sudo sysctl -w kernel.yama.ptrace_scope=1go for it
hmmmmm
are kernel flags part of the image?
oh wait
gimme sec
that was done in a distrobox 😅
oh, ok so I did a reboot though, and it put it back. How do I make kernel flags permenant?
ok, so that changed the value, but unfortunately didn't fix 1Password. It sounds like 1password needs to run as root. Is there a way to get rpm-ostree to install an rpm as root instead of user?
just from trying to run it, it appears I need to add the
--no-sandbox flag to the processrpm-ostree install is always root
it's the exact same thing as dnf install
I just checked my bazzite 1Password installation against my Nobara one (it works on my nobara one) and I can't see a difference haha hopefully the 1Password support has some ideas
One of the errors that the 1password support dev is looking into is a line that says this:
process detected it was running without libc's security. Any idea what that could mean? Googling it doesn't yield much when googling it with quotes
maybe SELinux is interfering?
LMAO I got it to work. This was the dumbest thing that's happened in a while hahahaSolution
Here's what I think happened.
1. I installed 1Password using the .rpm file.
2. It created a symlink for /opt/1Password, possibly due to how the atomic distro works, or maybe that's just normally how this gets installed
3. I then uninstalled 1Password, but the symlink was left behind (broken) (I can't remember why I did this)
4. I re-installed 1Password, but using the tar method. This overwrote the symlink, as it's a manual process
5. I ran into the exact same issue I just showed you. The Read-only filesystem would not let me install properly
6. I then installed using the .rpm file again, but I did not first remove the manual installation. This would have effectively broken the chain of dependencies (I suspect) resulting in the issues I've been having, especially if the .rpm chose not to overwrite the pre-existing contents of /opt/1Password
However, the 1Password tech support asked me to try the
tar method again, and asked that I completely uninstall the old installation. This included deleting the contents of /opt/1Password. While this didn't work, it did make me realize that the .rpm version of the installation expected /opt/1Password to not already exist, and so there were installation problems.