New Zorin17 install can't connect to 1Password from desktop app

I have a new/fresh install of Zorin OS 17.1 core on an Intel NUC 11 PC in a residential/home environment, connected to internet via a home WiFi network.

(Separate issue: attempting to connect to the WiFi network during installation caused install process to hang indefinitely. However, it connected to the WiFi network happily after install had completed).

I am unable to connect to my (remote) 1Password vault from the desktop app. I can log in to my 1Password account/vault via a web browser on the same machine, and also from several other machines on the same WiFi network.

1Password is the ONLY application I have added post OS install.

I installed 1Password via the Applications GUI (snap store version 8.10.27). I have (on a previous OS install on the same machine) also tried the .deb version. No difference.

I opened a support ticket with 1PW but they can't reproduce the problem, so can't help me further. I also have a second NUC on the same WiFi network with Zorin installed (from the same USB install media) and it has no problem. So it seems like something specific to this machine.

The 1PW desktop application opens fine, and takes me to a login screen. I provide valid credentials, and then it takes a long time to fail to connect, so it might be a network timeout or blocking issue.

I have followed most of the advice i have found on this forum, but nothing has solved it so far. Things I have done are:

sudo apt update; sudo apt upgrade
(FWIW this doesn't take very long, so internet connection seems okay)

sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf

Set DNS to Cloudflare (1.1.1.1, 1.0.0.1).

The network firewall is off by default, and I have not turned it on.

I have also tried disabling apparmor: via
sudo systemctl disable apparmor which didn't seem to make any difference.

So I still can't connect to 1PW from the desktop application :expressionless:

Has anybody else experienced a similar issue?
Any advise what else I could try to work around it?

Thanks in advance :slight_smile:

I don't have an account with them so I can't troubleshoot this but I would search for any log files produced by the client. These are probably stored somewhere in /var/log but being a snap package, the location may be different.

Have you followed these steps?

Thanks zenzen.

Just to clarify: I'm only having an issue with the 1PW desktop client on this one machine. The browser client works fine on the same machine. Both the desktop and browser clients work fine on my other Zorin machine installed from the same media and on the same WiFi network.

I did have a look at the 1PW account site, but it is mainly to do with the browser client which I don't have an issue with. I have also had a support ticket with them, but they can't reproduce the problem.

I ran the client again and had a look in /var/log but don't see anything that looks 1PW-related in there.

The client does have a button that dumps diagnostic information to a file on the desktop. There is a huge wall of text in that file, including a bunch of WARN and ERROR messages, which i've copied here (apologies if this is a bit long/repetitious; didn't want to miss anything that might matter):

ERROR 2024-03-12T01:23:00.121 ThreadId(11) [1P:/builds/dev/core/core/ssh/op-ssh-config/src/lib.rs:183] Failed to start ssh config file watcher: Io(Os { code: 2, kind: NotFound, message: \"No such file or directory\" })
...
WARN  2024-03-12T01:23:00.134 1Password Application Keyring Manager(ThreadId(19)) [1P:foundation/op-linux/src/kernel_keyring.rs:88] 1Password's application keyring failed to initialize (KeyringError(Os { code: 1, kind: PermissionDenied, message: \"Operation not permitted\" })), its functionality will be unavailable
WARN  2024-03-12T01:23:00.134 tokio-runtime-worker(ThreadId(13)) [1P:foundation/op-linux/src/kernel_keyring.rs:370] fallback keyring was not usable
WARN  2024-03-12T01:23:00.134 tokio-runtime-worker(ThreadId(13)) [1P:foundation/op-linux/src/kernel_keyring.rs:840] failed to initialize keyring helper, its functionality will be unavailable: KeyringError(Os { code: 1, kind: PermissionDenied, message: \"Operation not permitted\" })
WARN  2024-03-12T01:23:00.135 ThreadId(11) [1P:native-messaging/op-native-core-integration/src/lib.rs:167] detected 1Password was in an incompatible sandbox, disabling native messaging.
INFO  2024-03-12T01:23:00.137 tokio-runtime-worker(ThreadId(8)) [1P:ssh/op-agent-controller/src/lib.rs:492] Starting filesystem watcher for SSH agent configuration directories...
ERROR 2024-03-12T01:23:00.138 tokio-runtime-worker(ThreadId(8)) [1P:/builds/dev/core/core/ssh/op-agent-controller/src/lib.rs:493] Io(Os { code: 2, kind: NotFound, message: \"No such file or directory\" })
ERROR 2024-03-12T01:23:00.170 ThreadId(11) [client:typescript] Could not load window state.
...
ERROR 2024-03-12T01:25:57.560 tokio-runtime-worker(ThreadId(3)) [1P:app/op-app/src/app/backend/signin.rs:569] error signing in from data layer: UnableToCreateClient(HttpError((/rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/ops/function.rs:250, IoError(IoError(error sending request for url (<redacted URL>): operation timed out)))))
ERROR 2024-03-12T01:25:57.560 tokio-runtime-worker(ThreadId(3)) [1P:/builds/dev/core/core/op-signin/src/lib.rs:728] error signing in from data layer: other error
ERROR 2024-03-12T01:25:57.561 tokio-runtime-worker(ThreadId(3)) [1P:/builds/dev/core/core/ui/op-signin-ui/src/handlers.rs:1585] Error signing in: other error
"},{"title":"/1Password_rCURRENT","content":"INFO  2024-03-13T03:03:12.670 ThreadId(11) [1P:op-settings/src/store/json_store.rs:117] Settings file \"/home/$USER/snap/1password/149/.config/1Password/settings/settings.json\" missing, using defaults.
...
WARN  2024-03-13T03:03:13.747 ThreadId(11) [1P:op-crash-reporting/src/killswitch.rs:58] Failed to check Sentry enabled status, Sentry is disabled. Reason: IoError(IoError(error sending request for url (<redacted URL>): operation timed out))
...
WARN  2024-03-13T03:03:13.830 1Password Application Keyring Manager(ThreadId(19)) [1P:foundation/op-linux/src/kernel_keyring.rs:88] 1Password's application keyring failed to initialize (KeyringError(Os { code: 1, kind: PermissionDenied, message: \"Operation not permitted\" })), its functionality will be unavailable
WARN  2024-03-13T03:03:13.830 tokio-runtime-worker(ThreadId(13)) [1P:foundation/op-linux/src/kernel_keyring.rs:370] fallback keyring was not usable
WARN  2024-03-13T03:03:13.830 tokio-runtime-worker(ThreadId(13)) [1P:foundation/op-linux/src/kernel_keyring.rs:840] failed to initialize keyring helper, its functionality will be unavailable: KeyringError(Os { code: 1, kind: PermissionDenied, message: \"Operation not permitted\" })
WARN  2024-03-13T03:03:13.835 ThreadId(11) [1P:native-messaging/op-native-core-integration/src/lib.rs:167] detected 1Password was in an incompatible sandbox, disabling native messaging.
INFO  2024-03-13T03:03:13.840 tokio-runtime-worker(ThreadId(2)) [1P:ssh/op-agent-controller/src/lib.rs:492] Starting filesystem watcher for SSH agent configuration directories...
ERROR 2024-03-13T03:03:13.842 tokio-runtime-worker(ThreadId(2)) [1P:/builds/dev/core/core/ssh/op-agent-controller/src/lib.rs:493] Io(Os { code: 2, kind: NotFound, message: \"No such file or directory\" })
...
WARN  2024-03-12T01:44:27.731 tokio-runtime-worker(ThreadId(13)) [1P:foundation/op-linux/src/kernel_keyring.rs:370] fallback keyring was not usable
WARN  2024-03-12T01:44:27.731 tokio-runtime-worker(ThreadId(13)) [1P:foundation/op-linux/src/kernel_keyring.rs:840] failed to initialize keyring helper, its functionality will be unavailable: KeyringError(Os { code: 1, kind: PermissionDenied, message: \"Operation not permitted\" })
WARN  2024-03-12T01:44:27.731 1Password Application Keyring Manager(ThreadId(19)) [1P:foundation/op-linux/src/kernel_keyring.rs:88] 1Password's application keyring failed to initialize (KeyringError(Os { code: 1, kind: PermissionDenied, message: \"Operation not permitted\" })), its functionality will be unavailable
WARN  2024-03-12T01:44:27.737 ThreadId(11) [1P:native-messaging/op-native-core-integration/src/lib.rs:167] detected 1Password was in an incompatible sandbox, disabling native messaging.
INFO  2024-03-12T01:44:27.738 tokio-runtime-worker(ThreadId(2)) [1P:ssh/op-agent-controller/src/lib.rs:492] Starting filesystem watcher for SSH agent configuration directories...
ERROR 2024-03-12T01:44:27.738 tokio-runtime-worker(ThreadId(2)) [1P:/builds/dev/core/core/ssh/op-agent-controller/src/lib.rs:493] Io(Os { code: 2, kind: NotFound, message: \"No such file or directory\" })
INFO  2024-03-12T01:44:28.027 tokio-runtime-worker(ThreadId(2)) [1P:app/op-app/src/app/backend/unlock.rs:548] System unlock was attempted but we cannot use it.
ERROR 2024-03-12T01:47:01.954 tokio-runtime-worker(ThreadId(8)) [1P:app/op-app/src/app/backend/signin.rs:569] error signing in from data layer: UnableToCreateClient(HttpError((/rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/ops/function.rs:250, IoError(IoError(error sending request for url (<redacted URL>): operation timed out)))))
ERROR 2024-03-12T01:47:01.954 tokio-runtime-worker(ThreadId(8)) [1P:/builds/dev/core/core/op-signin/src/lib.rs:728] error signing in from data layer: other error
ERROR 2024-03-12T01:47:01.954 tokio-runtime-worker(ThreadId(8)) [1P:/builds/dev/core/core/ui/op-signin-ui/src/handlers.rs:1585] Error signing in: other error
INFO  2024-03-12T06:37:39.548 tokio-runtime-worker(ThreadId(8)) [1P:app/op-app/src/app/backend/unlock.rs:548] System unlock was attempted but we cannot use it.
ERROR 2024-03-12T06:38:43.332 tokio-runtime-worker(ThreadId(6)) [1P:app/op-app/src/app/backend/signin.rs:569] error signing in from data layer: UnableToCreateClient(HttpError((/rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/ops/function.rs:250, IoError(IoError(error sending request for url (<redacted URL>): operation timed out)))))
ERROR 2024-03-12T06:38:43.332 tokio-runtime-worker(ThreadId(6)) [1P:/builds/dev/core/core/op-signin/src/lib.rs:728] error signing in from data layer: other error
ERROR 2024-03-12T06:38:43.332 tokio-runtime-worker(ThreadId(6)) [1P:/builds/dev/core/core/ui/op-signin-ui/src/handlers.rs:1585] Error signing in: other error
"}]}

It does seem to be complaining that an application keyring operation is not permitted, and that the sandbox isn't right, and something is timing out... but i have no idea what any of it really means.

Any clues where I could be looking?

Properly because it's a snap package which runs in sandbox. Is there a linux client from their homepage you can download?

Is this it: Get the 1Password for Linux app

There is support for Ubuntu listed there, so assume its a .deb download, but not tried it myself.

Yes, I have (previously) downloaded and installed the .deb package instead of the snap one, but (unless I'm doing it wrong--which is entirely possible) it had exactly the same problem.

I used the automatic install process, by clicking the .deb (i didn't attempt the manual install process outlined for Ubuntu at the download link).

I could try it again, but I don't expect any different behaviour.

Is there any reason to think the automatic process wouldn't do all the stuff the manual process does?

Did you leave the Snap version installed at the time, and if so- when you launched 1Password, are you certain that the .deb version launched instead of the Snap?

I ask because everything you describe sounds like a permissions issue...

Pretty sure I had uninstalled the snap version, then installed the .deb version, so there was only one version installed at a time.

I will try the .deb again just to be sure...

I uninstalled the snap 1PW app, and installed the .deb 1PW app (by clicking on the deb package).

Same experience when I try to connect to my 1PW account, it times out and fails.

Exporting the diagnostics log, it's a lot shorter and ends with a different looking ERROR message:

INFO  2024-03-14T11:19:19.682 tokio-runtime-worker(ThreadId(8)) [1P:ssh/op-agent-controller/src/lib.rs:492] Starting filesystem watcher for SSH agent configuration directories...
ERROR 2024-03-14T11:19:19.682 tokio-runtime-worker(ThreadId(7)) [1P:op-global-shortcuts/src/lib.rs:69] AppError at /builds/dev/core/core/op-global-shortcuts/src/node.rs:62:6
binding shortcut

Caused by:
    BindRefused

ERROR 2024-03-14T11:19:19.682 tokio-runtime-worker(ThreadId(3)) [1P:op-global-shortcuts/src/lib.rs:69] AppError at /builds/dev/core/core/op-global-shortcuts/src/node.rs:62:6
binding shortcut

Caused by:
    BindRefused

ERROR 2024-03-14T11:19:19.682 tokio-runtime-worker(ThreadId(8)) [1P:/builds/dev/core/core/ssh/op-agent-controller/src/lib.rs:493] Io(Os { code: 2, kind: NotFound, message: \"No such file or directory\" })
ERROR 2024-03-14T11:19:19.707 ThreadId(11) [client:typescript] Could not load window state.
INFO  2024-03-14T11:19:20.037 tokio-runtime-worker(ThreadId(4)) [1P:app/op-app/src/app/backend/unlock.rs:548] System unlock was attempted but we cannot use it.
INFO  2024-03-14T11:20:51.255 tokio-runtime-worker(ThreadId(4)) [1P:op-b5-client/src/internal/unauthorized_session.rs:845] Registered device t2zywtt2ejgauixizjc7thskba
ERROR 2024-03-14T11:21:51.773 tokio-runtime-worker(ThreadId(4)) [1P:app/op-app/src/app/backend/signin.rs:569] error signing in from data layer: UnableToCreateClient(HttpError((/rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/ops/function.rs:250, IoError(IoError(error sending request for url (<redacted URL>): operation timed out)))))
ERROR 2024-03-14T11:21:51.773 tokio-runtime-worker(ThreadId(4)) [1P:/builds/dev/core/core/op-signin/src/lib.rs:728] error signing in from data layer: other error
ERROR 2024-03-14T11:21:51.773 tokio-runtime-worker(ThreadId(4)) [1P:/builds/dev/core/core/ui/op-signin-ui/src/handlers.rs:1585] Error signing in: other error
ERROR 2024-03-14T11:22:03.971 ThreadId(11) [client:typescript] Could not load window state.
"},{"title":"/KeyringHelper/1Password_rCURRENT","content":"INFO  2024-03-14T11:19:19.678 main(ThreadId(1)) [1P:foundation/op-linux/src/bin/keyring_helper.rs:134] initalizing keyring helper
"}]}

Looking each of these errors up leads to different discussions on different issues. For example:

In each case, the developers allude to further necessary work needed in the code.

I would recommend communicating via bug report with the 1password application developers. Each instance depicts an error within 1password, not Zorin OS.
Our history of behavior on this forum stand - we do not shy away from helping users resolve issues with software outside of Zorin OS purview, in order to get them up and running.
However, there are plenty of areas in which we are woefully unqualified to tackle.

I totally understand that Zorin forum users can't be expected to resolve all issues with all vendor software. That's perfectly natural.

What I don't understand, is why the 1PW desktop app works fine on one of my Zorin machines, and doesn't work on the other one :expressionless:

Both machines are on the same WiFi network.
Both machines have Zorin installed from the same media.

The only differences i can think of are:

  1. Hardware. The machine that works is NUC7. The machine that doesn't is NUC11.
  2. Maybe (can't recall exactly) Zorin had advanced from 16 to 17 between my installs? If it did, then one on which 1PW works was Zorin 16 on NUC7 with 1PW snap package; the one on which 1PW doesn't work was Zorin 17 on NUC11 (and neither snap or deb 1PW works).
  3. Another maybe... the order in which 1PW and other apps were installed post Zorin install?

FWIW, I have already raised a support ticket with 1PW, and they say they can't reproduce the problem.

This is a perfectly valid point. And while we can suggest exploring the App Developer for help, this does not mean that it is not something that needs to be addressed in Zorin OS, either.

Having the app developer take a look can provide better clues.
If... they do that, anyway.

In the meantime, have you tried creating a Bootable LiveUSB of Zorin OS 17 and then testing the 1PW application on that in the Live Trial Mode? It would be interesting to see if that works or not...
You could test this on both machines with their different hardware, then compare the results.

Remember that without Persistence setup, each boot of a LiveUSb will boot default as a fresh new start.

I haven't tried this.
Does this mean creating a new install media with BalenaEtcher, then booting from the install media and choosing the test/trial Zorin option, rather than the install Zorin option? Or is Live Trial Mode something else?

I can give it a go, for sure.

If you have ZorinOS installation USB already, then use that. Just select "Try Zorin" option instead of install Zorin.
You could also do the same if you have your old Z16 installation USB handy, to see if any difference on Z16 than Z17.

1 Like

Okay, some more information to wrap up.

I tried 1PW with Zorin running from the installation media ("Try Zorin" option) on the NUC11 (the problem machine) and it was the same experience as running it from Zorin actually installed on the machine.

Then I went back to my NUC7 (on which 1PW was working), and confirmed a few things:

  1. The NUC7 is running Zorin17 core, exactly the same as on the NUC11.
  2. 1PW was working on the NUC7, because I can still access a local copy of my password vault on the desktop app.
  3. HOWEVER. The big change is that I can no longer synch with my (remote) 1PW account from the desktop app on the NUC7. So this is now exactly the same behaviour as I am seeing on the NUC11 (it can't log in to my remote 1PW). Luckily, because I can still access my local vault on the NUC7, I am seeing a different error message reported in the logs on that machine, which complains about my email address (which is used as a user id credential).

This new information tells me that something has changed on the vendor's app side. It is an unfortunate coincidence that their change must have happened around the same time that I changed over to the NUC11.

I will report this info back to the vendor in another ticket.

Apologies for the noise, and thanks to everyone who replied for assisting me to zero in on the problem.

3 Likes

In hindsight, something that could've helped to detect this earlier is run the program from the terminal. This way you could've seen any error logs reporter by the program. Although this isn't necessarily always the case, it's very dependent on the program and type of error. Just a thought, for future reference.

Could you please update this thread once you have more information about the issue?