Flatpak Browser and Native Desktop App
Thought I would share this as I've managed to get the native desktop app working with my flatpak installation of Firefox. I'm on Arch and using the version of 1Password from the AUR and the standard flatpak version of Firefox from flathub. Add permissions to Firefox Flatpak via Flatseal: Session Bus Talks: org.freedesktop.Flatpak As root, create /etc/1password folder if it does not exist As root, create /etc/1password/custom_allowed_browsers file if it does not exist As root, edit /etc/1password/custom_allowed_browsers file and set content to: flatpak-session-helper As user, create ~/.var/app/org.mozilla.firefox/data/bin folder if it does not exist As user, create ~/.var/app/org.mozilla.firefox/data/bin/1password-wrapper.sh file if it does not exist As user, edit ~/.var/app/org.mozilla.firefox/data/bin/1password-wrapper.sh and set content to: ``` #!/bin/bash flatpak-spawn --host /opt/1Password/1Password-BrowserSupport "$@" - As user, mark ~/.var/app/org.mozilla.firefox/data/bin/1password-wrapper.sh as executable via `chmod +x ~/.var/app/org.mozilla.firefox/data/bin/1password-wrapper.sh` - As user, create ~/.var/app/org.mozilla.firefox/.mozilla/native-messaging-hosts folder if it does not eixst - As user, create ~/.var/app/org.mozilla.firefox/.mozilla/native-messaging-hosts/com.1password.1password.json file if it does not exist - As user, edit ~/.var/app/org.mozilla.firefox/.mozilla/native-messaging-hosts/com.1password.1password.json and set content to: { "name": "com.1password.1password", "description": "1Password BrowserSupport", "path": "/home/{USERNAME}/.var/app/org.mozilla.firefox/data/bin/1password-wrapper.sh", "type": "stdio", "allowed_extensions": [ "{0a75d802-9aed-41e7-8daa-24c067386e82}", "{25fc87fa-4d31-4fee-b5c1-c32a7844c063}", "{d634138d-c276-4fc8-924b-40a0ea21d284}" ] } ``` Where {USERNAME} is the name of your user, essentially full path to the file we created before. - Restart Firefox and 1Password The above can be broken down into (mostly) the following commands: ``` sudo mkdir -p /etc/1password sudo vim /etc/1password/custom_allowed_browsers mkdir -p ~/.var/app/org.mozilla.firefox/data/bin vim ~/.var/app/org.mozilla.firefox/data/bin/1password-wrapper.sh chmod +x ~/.var/app/org.mozilla.firefox/data/bin/1password-wrapper.sh mkdir -p ~/.var/app/org.mozilla.firefox/.mozilla/native-messaging-hosts vim ~/.var/app/org.mozilla.firefox/.mozilla/native-messaging-hosts/com.1password.1password.json ``` I had also added xdg-run/1Password-BrowserSupport.sock , however it doesn't appear this socket file is actually needed for the extension to work from what I can tell so far. This does somewhat break the isolation of Flatpak as it can now execute anything on the host via flatpak-spwan --host and there's no real easy way to whitelist specific host binaries that can run via Flatpak, kind of all or nothing annoyingly. I also want to see if sometihng similar is possible for getting the Flatpak 1Password app communicating with a Flatpak browser, as KeePassXC has a kind of workaround for this that is similar. This does somewhat break the isolation of Flatpak as it can now execute anything on the host via flatpak-spwan --host and there's no real easy way to whitelist specific host binaries that can run via Flatpak, kind of all or nothing annoyingly. I also want to see if sometihng similar is possible for getting the Flatpak 1Password app communicating with a Flatpak browser, as KeePassXC has a kind of workaround for this that is similar. 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided Browser: Not Provided1.1KViews1like7Comments1Password window blank on gnome 48, wayland , fedora 42
1Password for Linux 8.10.68 (81068014) opens correctly but within a minute the app window goes blank. Behaviour is the same with wayland and x11 ELECTRON_OZONE_PLATFORM_HINT=auto 1password --disable-gpu ELECTRON_OZONE_PLATFORM_HINT=x11 1password --disable-gpu Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed at s.send (node:electron/js2c/browser_init:2:93065) at _.send (node:electron/js2c/browser_init:2:76113) at te.send (/opt/1Password/resources/app.asar/main.js:1:105968) at BrowserWindow.<anonymous> (/opt/1Password/resources/app.asar/main.js:1:105382)16Views0likes0CommentsRegression in 1Password Auto-Fill for Directory-Protected Links
Previously, 1Password reliably auto-filled credentials when accessing directory-protected URLs. However, for the past 10-14 days, this functionality has stopped working on both macOS Sequoia and Pop!_OS (Ubuntu 22.04). Given that I frequently work with such URLs, this regression significantly impacts my workflow. Has there been a recent change affecting this behavior, and if so, is there a way to restore it? Would appreciate any insights or workarounds.64Views0likes5CommentsTurn Off Dialogs
I use Google for work and sign in with google frequently. I'm very tired of having to constantly close the "Save in 1Password" dialogs. I DON'T WANT TO. I even get the dialogs if I turn off the main "Offer to fill and save passwords" setting. The only way to stop them seems to be to uninstall the browser extension. FYI - The option to turn off the Google integration that seems to work for other users does not appear to exist for Firefox (actually I'm using LibreWolf). I'm pretty close to uninstalling the extension. And without a browser integration, I don't see why I would continue to use (or pay for) 1Password.Solved43Views0likes3CommentsError when adding 1Password beta RPM repo.
I followed the instructions listed at https://support.1password.com/betas/?linux#centos-fedora-or-red-hat-enterprise-linux for installing 1Password beta on Fedora. When I issued the command to install 1Password, I got the error shown below. % sudo dnf install 1password Updating and loading repositories: 1Password Beta Channel 100% | 17.9 KiB/s | 3.8 KiB | 00m00s >>> Librepo error: repomd.xml GPG signature verification error: Signing key not foundSolved53Views0likes3CommentsVault Naming Convention – Security & Usability Concern
The recent decision to name all core vaults as "Employee" in 1Password is highly counter-intuitive and introduces unnecessary risk. In environments where multiple 1Password accounts are used, we've observed that users frequently misplace credentials in the wrong "Employee" vault. As a result, sensitive data—including API keys, passwords, and banking details—has been inadvertently exposed to unintended users with access to these vaults, despite the correct Primary Vault being set. This naming convention creates significant ambiguity. Why wasn't a more logical format such as "$AccountName - Employee" considered to differentiate vaults across multiple accounts?Solved68Views0likes3Comments[Bug Report] Dates with year 3000+ show as 0
Add a Date field to an item in the 1Password client Set the date to year 3000 or beyond Save the item View the field in the saved item In my clients all such dates which I tested show the entire value of the field as "0"; that is, the date, not just the year, is "0". It should show any date which can be set. Tested on clients on three Linux platforms: Android, Ubuntu and NixOS*. Observation confirmed in Chrome extension version 2.19.1. Note that this is not an invitation to speculate on circumstances in which dates may be valid, applicable or useful, nor how this kind of thing is a symptom of the kind of poor programming which kept me in the office tomorrow twenty-four years ago. *[The required category options include just "Linux" and "Android", but nothing for desktop, mobile or or all clients.] PS. The rich text editor applies common markup for _italic_ but then fails to render it when a footnote line begins with an unescaped asterisk (*). 1Password Version: 8.10.23 Extension Version: N/A OS Version: Various Browser: N/ASolved66Views0likes3CommentsCustom autofill behavior for OPNsense
Hi there, I finally moved to 1Password 8 after resisting the cloud for what seems like a dozen years. Glad to see the new autofill behavior customisations (at least I hope they're new and I didn't miss them all this time). However, I can't get the autofill to work for one site, the OPNsense 25.1 login page. It's on a subdomain, and because I have other stuff on other subdomains, I have all that stuff on the domain set to "only fill on this exact domain". The OPNsense login is the only one that doesn't work in Safari on the Mac or in Firefox in Linux Mint. It does work fine on my iPhone, though. Anybody else? Thanks, JimSolved97Views0likes2CommentsFedora 41 Installation error
Hello, I just installed 1Password on a brand new Fedora 41 installation following the instructions. 1Password is the first app I installed after the setup and a sudo dnf upgrade command. I followed the instructions at https://support.1password.com/install-linux/#fedora-or-red-hat-enterprise-linux. After running sudo dnf install 1password, the system showed the error message: Librepo error: repomd.xml GPG signature verification error: Signing key not found The installation continued and 1Password is running fine but I would rather it didn't. That's not your problem but it seems something has changed in the key management of Fedora 41 as I have never seen this error in 39 or 40. Kind regards. 1Password Version: Not Provided Extension Version: Not Provided OS Version: Fedora 41 Browser: Not Provided332Views2likes1Comment