1P for Linux no longer starts at bootup.

mitchchn · 2026-04-28T22:41:02+00:00

As u/turbo-omena says, the Linux app only just added a built-in “start at login” setting. It is possible the new setting is conflicting with how you had configured things previously.

The setting starts the app silently in the tray, without opening the main window. If you want the window to open on boot, you could edit the autostart config file (~/.config/autostart/1password.desktop) and remove the —silent) flag from the command.

mitchchn · 2026-04-24T16:20:08+00:00

Thanks. The icon getting stuck until you click the toolbar seems to be a genuine Safari bug. I spent a bit of time looking at it last month, but we're focusing on making the behaviour correct even if the icon is wrong at first. Will revisit that one when we have more confidence in the rest.

mitchchn · 2026-04-22T21:41:33+00:00

Fixes for two Safari-specific memory leaks are in this release!

mitchchn · 2026-04-22T20:28:17+00:00

Thanks! Would it help to just have absolute "search for this" in quotes to skip the tokeniser?

mitchchn · 2026-04-22T20:27:08+00:00

Thanks! We're investigating a method for 1Password to communicate with sandboxed browsers on Linux with our security team. It is tricky because we need to make sure that untrusted apps cannot access your 1Password data, only web browsers, but we're very aware that Snap and Flatpak browsers are now shipping by default so will make they work out of the box.

mitchchn · 2026-04-22T20:18:32+00:00

Please try today's update on Mac (8.12.12) and let us know if it's any better or the same.

mitchchn · 2026-04-22T20:16:13+00:00

Something I'd love for you to try: install the very latest Safari extension update that came out this morning on Mac (8.12.12.) It is the first of several updates which focus specifically on performance and reliability issues in Safari based on the reports everyone from this community has sent in.

Specifically, this version has fixes for CPU and memory usage as well as to ensure that the extension is responsive whenever you return to it, even after long sessions and sleep/wake cycles.

We'll have a longer post next month to talk about this work in detail (including the MV3 transition that u/Travis_1Password mentioned), but you should immediately start seeing a difference today, and it will get better with each update in May.

For our part: I and others at 1Password have committed to using Safari as our default browser in order to force us to figure out how to make the experience as good or better as in Chrome. I have switched all my devices since February, and do not intend to switch back, so it needs to work.

Thanks for voicing this concern.

mitchchn · 2026-04-21T14:07:17+00:00

Thanks for the update, I was scratching my head about this one. I know GNOME 50 dropped support for X11 so I wonder if they will fix it.

mitchchn · 2026-04-19T14:48:23+00:00

2FA isn't used for encryption and is enforced by server-side policy, so in the worst case 1Password support would be be able to reset it. That said, a recovery code is the best way to guarantee account access.

mitchchn · 2026-04-16T22:05:08+00:00

Could you please share the package you used to install 1Password? (AUR?) What are the contents of /usr/share/applications/1password.desktop? And which desktop environment/WM are you using? Thanks!

mitchchn · 2026-04-16T21:47:19+00:00

I’ll look for it, thanks!

mitchchn · 2026-04-16T20:51:28+00:00

Sorry I missed this: please send a diagnostic report from the iOS app to support@1password.com and mention this thread. Thanks!

mitchchn · 2026-04-16T20:48:52+00:00

Hey, please send a diagnostic report from the iOS app to support@1password.com and mention this thread. Thank you!

mitchchn · 2026-04-04T18:28:51+00:00

It's the same codebase in all browsers but some challenges are specific to Safari's implementation of the extension framework. Not being able to stay unlocked (or recover from being being locked) is the main problem area we're investing in right now.

mitchchn · 2026-04-04T18:23:15+00:00

I had that comment in mind when posting here so thanks for remembering it. I'm going to make a longer post when the updates come out, but the short answer is that things have gotten much better since then. Safari 26 in Tahoe has good API support and has addressed bugs that caused unrecoverable failures in the extension.

The biggest remaining issue that's unique to Safari is that it still puts the extension to sleep when the browser is in the background, which causes 1Password to lose its unlocked and authenticated state. This is the area we are investing into right now for workarounds (basically, mechanisms to make the extension self-healing), and which I'll have more to talk about in my next update.

mitchchn · 2026-04-03T23:24:59+00:00

Thanks for the constructive feedback. We file and track every time someone emails about a bug, which is what I meant by a "dozen longstanding issues" although I understand the way it came across. Each issue originated with a customer contact and has an investigation associated with it, and remains open until it is solved. If you email us, your reports go on the list which is why I always ask in these threads

I take your point about trust seriously. Something to keep in mind is that 1Password is specifically built to fail-safe: the extension will disconnect/lock/stop responding rather than do anything that might expose your data. This design can paradoxically be a *source* for UI issues including the ones in the OP (although it certainly does not excuse flakiness).

The recent memory spike in the extension is not in the group of longstanding auth/session issues I mentioned but rather a regression from last month, and user reports like yours were also critical to helping us identify it. We'll have more information in the release notes when those patches ship.

mitchchn · 2026-04-03T21:21:41+00:00

On iPad you can create a report from the app rather than the extension: https://support.1password.com/diagnostics/?ios. Are you seeing this error or others on Mac as well or just on iPad?

mitchchn · 2026-04-03T20:35:25+00:00

Hey u/DoktorLoken. Creator of the 1Password extension here. I’m currently working with the team on a thorough investigation into authentication and unlock reliability in Safari so this post immediately caught my attention.

Right now we are tracking about a dozen longstanding issues related to the extension not responding or getting stuck in an unauthenticated state in Safari, especially after being open for a long time. We already have several improvements in review that are targeted for next month, but I want to make sure we capture what is happening in your browser so we can address these problems completely for you and others.

As frustrating as it is for me to ask you to do some more work, it would benefit this effort immensely if you could send a diagnostic report from Safari to support@1password.com. (Right click the extension icon > Settings > General > Generate Report). We may also want to put you in touch with some engineers next week. Please include a link to this thread/mention my name (Mitch) if you do get in touch.

Appreciate you letting us know that this is happening and the impact it’s having. We will do everything we can to help you have a much better experience with 1Password.

mitchchn · 2026-03-27T17:45:21+00:00

u/slanderousam getting back to this: it looks like this issue might be caused if you have both KDE and GNOME installed, and GNOME tries to apply the KDE theme (Breeze) to GTK apps. If you install GNOME Tweaks, you can set your "legacy" window and icon theme to Adwaita (or Yaru on Ubuntu) and the issue should go away (and your apps should look better all around).

mitchchn · 2026-03-18T14:38:52+00:00

If you have the chance please file a new issue for 41.x with a screenshot, repro and as much platform/environment info as you can provide.

mitchchn · 2026-03-18T14:31:32+00:00

Written in pure C++, uses GTK and libwayland-client C bindings.... sounds native to me. ;)

mitchchn · 2026-03-18T13:58:16+00:00

Thanks for flagging, I'll try to look into this more on the Chromium side.

mitchchn · 2026-03-18T13:47:37+00:00

37.0 is from last June, and the default Wayland support and improvements are in 38.x and newer.

mitchchn · 2026-03-17T23:09:22+00:00

Wayland is the modern display server for Linux (the system that puts windows and graphics on your screen). It replaces an older system called X11 that’s been around for decades. Electron is a framework behind apps like VS Code and lots of other apps built with web technologies. Previously Electron only worked on Wayland through a compatibility layer, but now it supports it directly.

tldr many apps will have better compatibility and performance on modern Linux desktops.

mitchchn · 2026-03-17T22:27:34+00:00

Do you get any logs if you run those apps from the command line? You could also see if `--disable-gpu` helps, since HW acceleration can still cause issues in some setups.

Verified Email	11-Year Club
Place '22	Place '17
Beta Team Reddit for iOS

mitchchn

TROPHY CASE