REMINDER: the community is in read-only mode until July 2nd. This is part of our platform upgrade! Learn more in the FAQs →
linux
725 Topics1Password on Linux crashes after 8.12.24 update
I tried posting info about a new fatal crash in the latest 8.12.24 deb package, but someone/something immediately marked the discussion as spam. Can someone on the community moderator team please take a look? I posted logs and a workaround in the thread, and I think other Linux users might appreciate knowing about it.Solved442Views0likes1CommentNo environment support in Linux
I tried following the instructions at https://www.1password.dev/cli/secrets-environment-variables. It says "use version 2.33.0-beta.02 or later" and I have 2.34.1 on Ubuntu but I get: $ op run --environment [ERROR] 2026/06/12 08:32:31 unknown flag: --environment I tried upgrading to 2.36.0-beta.03 but that fails to login: $ ./op_v2.36.0-beta-03 vault list [ERROR] 2026/06/15 09:14:33 connecting to desktop app: read: connection reset, make sure 1Password CLI is installed correctly, then open the 1Password app, select 1Password > Settings > Developer and make sure the 'Integrate with 1Password CLI' setting is turned on. If you're still having trouble connecting, visit https://www.1password.dev/cli/app-integration#troubleshooting for more help.94Views0likes2CommentsLinux app crashes on startup after 8.12.24 update
I've been using the deb package distribution for 1Password on Linux for a long time. The latest 8.12.24 deb package introduces a regression that causes the application to crash immediately upon opening the window with an `Illegal instruction (core dumped)` error. Running `/usr/bin/1password` from the terminal reveals the root cause, a strict sandbox/thread initialization failure tied to a VA-API version mismatch: /usr/bin/1password --log=trace ... [205370:0624/145107.193054:FATAL:sandbox/linux/services/thread_helpers.cc:104] Current process is not mono-threaded! (iterations: 30) [205265:0624/145107.283888:ERROR:content/browser/gpu/gpu_process_host.cc:999] GPU process exited unexpectedly: exit_code=133 [205443:0624/145107.296002:ERROR:media/gpu/vaapi/vaapi_wrapper.cc:1680] Installed VAAPI version is too old. min supported version: 1.17 installed version: 1.14 [205443:0624/145108.445056:FATAL:sandbox/linux/services/thread_helpers.cc:104] Current process is not mono-threaded! (iterations: 30) [205265:0624/145108.536510:ERROR:content/browser/gpu/gpu_process_host.cc:999] GPU process exited unexpectedly: exit_code=133 [205265:0624/145108.536532:FATAL:content/browser/gpu/gpu_data_manager_impl_private.cc:417] GPU process isn't usable. Goodbye. ERROR 2026-06-24T18:51:08.677+00:00 ThreadId(18) [1P:op-crash-reporting/src/crash_handler.rs:271] Failed to prepare for requesting dump Illegal instruction (core dumped) Through a lot of trial and error, I found a temporary but seemingly undocumented flag that can launch the app as a workaround: adding `--disable-gpu-sandbox` seems to resolve the crash and allows the app to function normally. The documented `--no-gpu` flag did not actually help and seems to have no effect on this crash. I confirmed my VA-API version is 1.14 like the error says: $ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.14 (libva 2.12.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.3.1 () I'm running on Pop!_OS 22.04 LTS with all current stable package updates applied. Pop!_OS 22.04 is basically a fork of Ubuntu 22.04 LTS "Jammy" and I believe should work unless you've dropped support for Ubuntu 22.04 LTS. Please look into making the GPU sandbox more resilient to older system VA-API libraries in the Electron build, gracefully falling back without hard-crashing, or yanking the 8.12.24 release and provide the old package.24Views0likes0CommentsSUGGESTION W/ DEMO: Auto Refresh ICONS + App/Website TILES
I believe I recall this being mentioned a few months ago and it being a pretty popular request. I made a simple demo animation in hopes that this gets more traction because, code wise, it's a very simple 1-2hr implementation (although I guess there might be SOME security concerns with fetching images/svgs/favicons? but probably not many)? Also, I hope you like my beautiful art. Shoutout to DAVE TEARE and SAN JOSE MARIOTT if they're real people (or twins?) (i got the screenshot from 1P website lol).Solved152Views0likes2CommentsImproved date formatting in the 1Password desktop app
Hello 1Password Community! With the next update to the 1Password desktop app (version 8.10.80), we have improved how date formats are handled when viewing and editing an item. Leading up to this update, there has been some inconsistency with how the desktop application has handled date formats when viewing and editing items. In some cases, date formats were being determined by the display language set in 1Password whereas in other cases, date formats were being determined by the language set against the device. This has led to some users seeing different date formats within the desktop app causing confusion. With this update, we've made things consistent by ensuring that dates saved against items always appear in a format determined by the locale set against your device (both when viewing and editing items) and never by the display language set in 1Password. This way, the desktop application can support more date formats than just the ones tied to the display languages that we support. Along with the recent improvements that we made to the date picker, we are hoping that you enjoy a much improved experience with dates in the 1Password desktop application! Thank you!1.5KViews4likes29CommentsCan we get 1st-party support for keyboard shortcuts?
Now that the interface to edit/set keyboard shortcuts has been removed from 1Password running under Wayland, It would be preferable if the installation package made the shortcuts available to configure by default, rather than https://support.1password.com/keyboard-shortcuts/?linux#wayland. I https://www.1password.community/discussions/1password/1password-shortcuts-on-wayland/90319/replies/158201 under a blog of post yours, but it was ignored. It's trivial to add Desktop Action sections to your existing launcher file, and reference them in an Actions= directive: [Desktop Entry] Name=1Password Exec=/opt/1Password/1password %U Terminal=false Type=Application Icon=1password StartupWMClass=1Password Comment=Password manager and secure wallet MimeType=x-scheme-handler/onepassword;x-scheme-handler/onepassword8; Categories=Office; Actions=Show;QuickAccess;Lock;Fill; [Desktop Action Show] Name=Show 1Password Icon=window-symbolic Exec=1password --show [Desktop Action QuickAccess] Name=Show Quick Access Icon=search-symbolic Exec=1password --quick-access [Desktop Action Lock] Name=Lock 1Password Icon=lock-symbolic Exec=1password --show [Desktop Action Fill] Name=Fill in Browser Icon=web-browser-symbolic Exec=1password --fill Putting a symlink to this expanded .desktop file under /usr/share/kglobalaccel/ makes those keyboard shortcuts appear in KDE Plasma's Settings app:114Views1like4CommentsFeature Request - MCP Limiting Controls
I really love using the MCP service with Claude CLI on my Mac, but it bothers me that it can somewhat easily see all my Vaults. Feature Request Please implement in the 1password App's MCP Settings: 1. Ability to toggle read access for individual vaults 2. Ability to toggle write access for individual vaults Mock-up Here's what I'd like in the 1Password App settings - This would be great for easing my mind specifically not that I don't accidentally give it keys to my kingdom (like the bank) (Props @ GPT and my ability to write a simple prompt) Failed Work-Around Attempt I tried creating another family member account in my family org and just shared the Vaults that I wanted my Claude to use with that, but the desktop app won't let me sign in to multiple accounts in the same org at the same time and I'm not really sure this would have been a good enough work-around for me anyway. The feature I'm requesting above would solve this perfectly. Successful Work-Around Attempt - But sucks So as it stands, the best that I guess I can do is login to my 1password desktop app with only to the dedicated account I made for Agentic access. This would not give any read-only support either, which is not epic.56Views0likes0CommentsFace recognition unlock for 1Password
I found the exact topic of my issue as well - not sure why the post was closed without ever posting any response other than some diagnostics... https://1password.community/discussion/138500/howdy-facial-recognition-doesnt-integrate-with-1password-in-fedora-37 I'm also running the latest RPM-based version. I've followed the thread mentioned to add the schema line to my settings file, and I do get a fingerprint button. When tapping it, I just get the password entry. To enable howdy, you need to add the howdy PAM authenetication step to the polkit service's authentication: add the line to /etc/pam.d/polkit-1 : auth sufficient pam_python.so /lib64/security/howdy/pam.py and restart polkit: sudo systemctl restart polkit.service 1Password Version: Not Provided Extension Version: Not Provided OS Version: Fedora 39 Browser: Not Provided266Views0likes2CommentsService Accounts in the GUI?
Are service accounts supposed to be manageable in the GUI/desktop app? I'm running Linux, and I don't see them in my account, despite being on the subscription that has them and them being available on the website. And if not, is this a feature that is coming soon? Because it's fairly impractical to manage them through the website. I'd also add that it's annoying having to recreate the service account every time I want to change permissions on it (add a vault, remove a vault, adjust a vaults permissions, rename it, etc). I understand that you've made it this way for additional security, but I don't think it's actually buying much added security in most circumstances, and I think it should at least be opt-out.28Views0likes0Comments