Error downloading documents from 1Password Linux App

bertez

Hello, I'm using the 1Password App on Arch Linux, and virtually everything is functioning OK so far... except for when I try to download a document stored in 1Password, which does not work at all and no error message is shown on the UI.

This is the error message that appears on the console:

INFO  2022-06-13T11:13:33.051 tokio-runtime-worker(ThreadId(7)) [1P:op-data-layer/src/file.rs:306] downloading: '/home/$USER/.config/1Password/files/7BCJF7XC7NHT3AMPMYD25GWY5E/az7ax52jhjdade666e5muvkufm.download'
ERROR 2022-06-13T11:13:33.709 tokio-runtime-worker(ThreadId(7)) [1P:op-app/src/app/backend/field_action.rs:563] OpOpen(InvalidPath)
ERROR 2022-06-13T11:13:33.739 tokio-runtime-worker(ThreadId(7)) [1P:op-app/src/app/backend.rs:209] AppError at op-app/src/app/backend/field_action.rs:170:20
Decrypt(OpOpen(InvalidPath))

Stack backtrace:
   0: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
   1: tokio::runtime::task::harness::poll_future
   2: tokio::runtime::task::harness::Harness<T,S>::poll
   3: std::thread::local::LocalKey<T>::with
   4: tokio::runtime::thread_pool::worker::Context::run_task
   5: tokio::runtime::thread_pool::worker::Context::run
   6: tokio::macros::scoped_tls::ScopedKey<T>::set
   7: tokio::runtime::thread_pool::worker::run
   8: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
   9: tokio::runtime::task::harness::Harness<T,S>::poll
  10: tokio::runtime::blocking::pool::Inner::run
  11: std::sys_common::backtrace::__rust_begin_short_backtrace
  12: core::ops::function::FnOnce::call_once{{vtable.shim}}
  13: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/alloc/src/boxed.rs:1854:9
      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/alloc/src/boxed.rs:1854:9
      std::sys::unix::thread::Thread::new::thread_start
             at /rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/std/src/sys/unix/thread.rs:108:17
  14: <unknown>
  15: clone

(node:25072) UnhandledPromiseRejectionWarning: Error: Decrypt(OpOpen(InvalidPath))
(Use `1password --trace-warnings ...` to show where the warning was created)
(node:25072) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

---

1Password Version: 8.7.1
Extension Version: Not Provided
OS Version: Arch Linux kernel 5.18.3

Dayton_ag

Hello @bertez , I'm really sorry you're running into this issue with 1Password! Let's get things back up and running.

When saving an attachment, 1Password automatically places the decrypted file in the XDG_DOWNLOAD_DIR directory, as declared in .bashrc or .zshrc. On many distros, this environment variable is set automatically by the package xdg-user-dirs. To get things working, you can declare a directory for XDG_DOWNLOAD_DIR in ..bashrc or .zshrc, in the format below:

XDG_DOWNLOAD_DIR="$HOME/Downloads"

Alternately, you can install the xdg-user-dirs package. If you'd like to read a little more about xdg-user-dirs and the function it provides before installing, you can find more information at the link below:

XDG user directories - ArchWiki

ref: dev/core/core#15581

bertez

Thank you very much, the problem is solved!

Dayton_ag

No problem, I'm glad I could help! 😄 Let me know if there's anything else I can do to assist.

fortes

Hi, I'm getting this same error and setting XDG_DOWNLOAD_DIR to any directory does not resolve it, still getting the same exception:

INFO  2022-07-05T12:25:52.192 tokio-runtime-worker(ThreadId(1)) [1P:op-data-layer/src/sync.rs:529] The B5 Notifier for (ET7TM7WVEVFANMTN7RYLHFY5OE) has connected, now monitoring for events.
ERROR 2022-07-05T12:26:50.074 tokio-runtime-worker(ThreadId(1)) [1P:op-app/src/app/backend.rs:209] AppError at op-app/src/app/backend/field_action.rs:688:20
Export(OpOpen(InvalidPath))

Stack backtrace:
   0: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
   1: tokio::runtime::task::harness::poll_future
   2: tokio::runtime::task::harness::Harness<T,S>::poll
   3: std::thread::local::LocalKey<T>::with
   4: tokio::runtime::thread_pool::worker::Context::run_task
   5: tokio::runtime::thread_pool::worker::Context::run
   6: tokio::macros::scoped_tls::ScopedKey<T>::set
   7: tokio::runtime::thread_pool::worker::run
   8: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
   9: tokio::runtime::task::harness::Harness<T,S>::poll
  10: tokio::runtime::blocking::pool::Inner::run
  11: std::sys_common::backtrace::__rust_begin_short_backtrace
  12: core::ops::function::FnOnce::call_once{{vtable.shim}}
  13: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/alloc/src/boxed.rs:1854:9
      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/alloc/src/boxed.rs:1854:9
      std::sys::unix::thread::Thread::new::thread_start
             at /rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/std/src/sys/unix/thread.rs:108:17
  14: start_thread
  15: clone

(node:8570) UnhandledPromiseRejectionWarning: Error: Export(OpOpen(InvalidPath))

fortes

Hi, I'm getting this same error and setting XDG_DOWNLOAD_DIR to the any directory does not resolve it, still getting the same exception:

INFO  2022-07-05T12:25:52.192 tokio-runtime-worker(ThreadId(1)) [1P:op-data-layer/src/sync.rs:529] The B5 Notifier for (ET7TM7WVEVFANMTN7RYLHFY5OE) has connected, now monitoring for events.
ERROR 2022-07-05T12:26:50.074 tokio-runtime-worker(ThreadId(1)) [1P:op-app/src/app/backend.rs:209] AppError at op-app/src/app/backend/field_action.rs:688:20
Export(OpOpen(InvalidPath))

Stack backtrace:
   0: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
   1: tokio::runtime::task::harness::poll_future
   2: tokio::runtime::task::harness::Harness<T,S>::poll
   3: std::thread::local::LocalKey<T>::with
   4: tokio::runtime::thread_pool::worker::Context::run_task
   5: tokio::runtime::thread_pool::worker::Context::run
   6: tokio::macros::scoped_tls::ScopedKey<T>::set
   7: tokio::runtime::thread_pool::worker::run
   8: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
   9: tokio::runtime::task::harness::Harness<T,S>::poll
  10: tokio::runtime::blocking::pool::Inner::run
  11: std::sys_common::backtrace::__rust_begin_short_backtrace
  12: core::ops::function::FnOnce::call_once{{vtable.shim}}
  13: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/alloc/src/boxed.rs:1854:9
      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/alloc/src/boxed.rs:1854:9
      std::sys::unix::thread::Thread::new::thread_start
             at /rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/std/src/sys/unix/thread.rs:108:17
  14: start_thread
  15: clone

(node:8570) UnhandledPromiseRejectionWarning: Error: Export(OpOpen(InvalidPath))

PeterG_1P

Hi @fortes, a few questions for you:

1. Are you able to download the relevant file on other devices successfully?

2. Do you have xdg-user-dirs installed?

3. If so, do you have a ~/.config/user-dirs.dirs file?

Thank you!

fortes

Some combination of installing xdg-user-dirs and restarting did the trick, thanks.

Now just gotta get the 2FA saved via KWallet or Gnome Keyring (I'm running i3, so things are unnecessarily hard)

PeterG_1P

Hey, that's great @fortes. Congrats on resolving the issue, and thanks for letting us know that this approach was effective for you!

Let us know if you'd like a consult on the 2FA setup - we're happy to help. 👍