Unable to download documents/attachments

Options
Fooligan
Fooligan
Community Member
edited June 2023 in Linux

Hello,

I am not able to download any of my documents or item attachments for some reason?

I can see the following happening in the syslog when I try to download something:

Dec 14 10:58:03 my_username 1password.desktop[PID]: INFO  2022-12-14T10:58:03.546 tokio-runtime-worker(ThreadId(1)) [1P:data/op-file-transfer/src/lib.rs:306] Using the local cache for this file
Dec 14 10:58:03 my_username 1password.desktop[PID]: ERROR 2022-12-14T10:58:03.550 tokio-runtime-worker(ThreadId(1)) [1P:op-app/src/app/backend.rs:234] AppError at op-app/src/app/backend/field_action.rs:200:20
Dec 14 10:58:03 my_username 1password.desktop[PID]: Open(InvalidPath)
Dec 14 10:58:03 my_username 1password.desktop[PID]: Stack backtrace:
Dec 14 10:58:03 my_username 1password.desktop[PID]:    0: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
Dec 14 10:58:03 my_username 1password.desktop[PID]:    1: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
Dec 14 10:58:03 my_username 1password.desktop[PID]:    2: tokio::runtime::task::core::CoreStage<T>::poll
Dec 14 10:58:03 my_username 1password.desktop[PID]:    3: tokio::runtime::task::harness::Harness<T,S>::poll
Dec 14 10:58:03 my_username 1password.desktop[PID]:    4: std::thread::local::LocalKey<T>::with
Dec 14 10:58:03 my_username 1password.desktop[PID]:    5: tokio::runtime::thread_pool::worker::Context::run_task
Dec 14 10:58:03 my_username 1password.desktop[PID]:    6: tokio::runtime::thread_pool::worker::Context::run
Dec 14 10:58:03 my_username 1password.desktop[PID]:    7: tokio::macros::scoped_tls::ScopedKey<T>::set
Dec 14 10:58:03 my_username 1password.desktop[PID]:    8: tokio::runtime::thread_pool::worker::run
Dec 14 10:58:03 my_username 1password.desktop[PID]:    9: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
Dec 14 10:58:03 my_username 1password.desktop[PID]:   10: std::panicking::try
Dec 14 10:58:03 my_username 1password.desktop[PID]:   11: tokio::runtime::task::harness::Harness<T,S>::poll
Dec 14 10:58:03 my_username 1password.desktop[PID]:   12: tokio::runtime::blocking::pool::Inner::run
Dec 14 10:58:03 my_username 1password.desktop[PID]:   13: std::sys_common::backtrace::__rust_begin_short_backtrace
Dec 14 10:58:03 my_username 1password.desktop[PID]:   14: core::ops::function::FnOnce::call_once{{vtable.shim}}
Dec 14 10:58:03 my_username 1password.desktop[PID]:   15: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
Dec 14 10:58:03 my_username 1password.desktop[PID]:              at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/alloc/src/boxed.rs:1940:9
Dec 14 10:58:03 my_username 1password.desktop[PID]:       <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
Dec 14 10:58:03 my_username 1password.desktop[PID]:              at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/alloc/src/boxed.rs:1940:9
Dec 14 10:58:03 my_username 1password.desktop[PID]:       std::sys::unix::thread::Thread::new::thread_start
Dec 14 10:58:03 my_username 1password.desktop[PID]:              at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/sys/unix/thread.rs:108:17
Dec 14 10:58:03 my_username 1password.desktop[PID]:   16: start_thread
Dec 14 10:58:03 my_username 1password.desktop[PID]:   17: clone
Dec 14 10:58:03 my_username 1password.desktop[PID]: 
Dec 14 10:58:03 my_username 1password.desktop[PID]: (node:PID) UnhandledPromiseRejectionWarning: Error: Open(InvalidPath)
Dec 14 10:58:03 my_username 1password.desktop[PID]: (node:PID) 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: 4)

1Password Version: 1Password for Linux 8.9.11 (80911014)
Extension Version: 2.6.1
OS Version: Ubuntu 20.04.5 LTS
Browser:_ Chrome

Comments

  • PeterG_1P
    PeterG_1P
    Options

    Hey @Fooligan, thanks for letting us know of this issue.

    The log output is helpful (thank you!). It looks like there may be some internal app errors that need to be addressed.

    I'd love to investigate this for you and get a full report to our developers. In order to do so, I'll ask that you send us a diagnostic file from the device where this problem occurred. Here's how:

    How to Send Us Diagnostics from Your Linux Device

    1. Open the 1Password for Linux app on your device.
    2. Select the vertical ellipses button ⋮
    3. Select Settings > Advanced > Send Diagnostics.
    4. Select Reveal to see the directory where the diagnostic file was generated (typically, it goes to your desktop).

    Once you have that file, send us an email at support+linux@1Password.com, and we'll let you know what we've found as well as assemble a report for our dev team.

    Thanks again for informing us of this, and we look forward to setting it right!

  • Fooligan
    Fooligan
    Community Member
    Options

    Hi @PeterG_1P,

    Unfortunately, I removed 1Password from the machine where I was having issues. The primary reason is related to this discussion. I want to protect my personal 1Password data and not have it on a work machine. I opted to go with a local KeePass vault for my work login items and it has been going well.

    Thanks for the reply.

  • vitalyzdanevich
    vitalyzdanevich
    Community Member
    Options

    I have the same problem, my logs:

    INFO  2023-06-09T15:00:04.351 ThreadId(10) [client:typescript] Client starting.
INFO  2023-06-09T15:00:04.418 ThreadId(10) [1P:op-localization/src/lib.rs:227] system locale detected as 'C'
INFO  2023-06-09T15:00:04.418 ThreadId(10) [1P:op-localization/src/lib.rs:242] C isn't directly supported; falling back to en-US
INFO  2023-06-09T15:00:04.418 ThreadId(10) [1P:op-localization/src/lib.rs:253] selected translations for EN_US based on detected locale en-US
INFO  2023-06-09T15:00:04.418 ThreadId(10) [status:op-app/src/app.rs:481] App::new(1Password for Linux/81007041 (EN_US), /home/$USER/.config/1Password/1password.sqlite)
INFO  2023-06-09T15:00:04.419 ThreadId(10) [1P:data/op-db/src/db.rs:427] Table Integrity Check Succeeded
INFO  2023-06-09T15:00:04.420 ThreadId(10) [1P:data/op-db/src/db.rs:443] DB Integrity Check Succeeded
INFO  2023-06-09T15:00:04.420 ThreadId(10) [1P:data/op-db/src/db.rs:137] Starting DB at version: 28
ERROR 2023-06-09T15:00:04.421 ThreadId(10) [1P:ssh/op-ssh-config/src/lib.rs:188] Could not open ssh config file in ~/.ssh/config
ERROR 2023-06-09T15:00:04.421 ThreadId(10) [1P:/builds/dev/core/core/ssh/op-ssh-config/src/lib.rs:161] Failed to start ssh config file watcher: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" })
INFO  2023-06-09T15:00:04.422 tokio-runtime-worker(ThreadId(3)) [1P:native-messaging/op-native-core-integration/src/lib.rs:324] Starting IPC listener on 1Password-BrowserSupport
INFO  2023-06-09T15:00:04.422 tokio-runtime-worker(ThreadId(3)) [1P:native-messaging/op-native-core-integration/src/lib.rs:336] Active native core integration is awaiting messages
INFO  2023-06-09T15:00:04.423 invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome/NativeMessagingHosts/com.1password.1password.json
INFO  2023-06-09T15:00:04.423 invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome-beta/NativeMessagingHosts/com.1password.1password.json
INFO  2023-06-09T15:00:04.423 invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome-unstable/NativeMessagingHosts/com.1password.1password.json
INFO  2023-06-09T15:00:04.423 invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/chromium/NativeMessagingHosts/com.1password.1password.json
INFO  2023-06-09T15:00:04.423 invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/microsoft-edge-dev/NativeMessagingHosts/com.1password.1password.json
INFO  2023-06-09T15:00:04.423 invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/com.1password.1password.json
INFO  2023-06-09T15:00:04.423 invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/vivaldi/NativeMessagingHosts/com.1password.1password.json
INFO  2023-06-09T15:00:04.423 invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/vivaldi-snapshot/NativeMessagingHosts/com.1password.1password.json
INFO  2023-06-09T15:00:04.423 invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.mozilla/native-messaging-hosts/com.1password.1password.json
INFO  2023-06-09T15:00:04.423 invocation_loop(ThreadId(17)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests.
INFO  2023-06-09T15:00:06.351 tokio-runtime-worker(ThreadId(8)) [1P:data/ext/op-account-ext-items/src/lib.rs:236] loaded 54 items in 3 vaults for account: I45SCFGPMJDUHP5BRHZUXB6Z74
INFO  2023-06-09T15:00:06.354 tokio-runtime-worker(ThreadId(3)) [1P:op-app/src/app/backend/unlock.rs:105] Lock state changed: Unlocked
INFO  2023-06-09T15:00:08.192 tokio-runtime-worker(ThreadId(4)) [1P:op-syncer/src/sync_job.rs:306] synced account I45SCFGPMJDUHP5BRHZUXB6Z74 (0.202499976s)
INFO  2023-06-09T15:00:08.192 tokio-runtime-worker(ThreadId(4)) [1P:data/op-file-transfer/src/lib.rs:563] find_and_complete_pending_uploads: 'I45SCFGPMJDUHP5BRHZUXB6Z74'
INFO  2023-06-09T15:00:08.825 tokio-runtime-worker(ThreadId(4)) [1P:data/ext/op-account-ext-syncer/src/lib.rs:256] The B5 Notifier for (I45SCFGPMJDUHP5BRHZUXB6Z74) has connected, now monitoring for events.
INFO  2023-06-09T15:00:09.235 tokio-runtime-worker(ThreadId(3)) [1P:data/op-file-transfer/src/lib.rs:320] downloading: '/home/$USER/.config/1Password/files/I45SCFGPMJDUHP5BRHZUXB6Z74/g43xr5uryrxi3txokbd43ohwpa.download'
ERROR 2023-06-09T15:00:10.608 tokio-runtime-worker(ThreadId(4)) [1P:op-app/src/app/backend.rs:264] AppError at op-app/src/app/backend/field_action.rs:235:20
Open(InvalidPath)

Stack backtrace:
   0: op_app::app::backend::async_task::{{closure}}
   1: op_executor::spawn_no_span::{{closure}}
   2: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
   3: tokio::runtime::task::harness::Harness<T,S>::poll
   4: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
   5: tokio::runtime::scheduler::multi_thread::worker::Context::run
   6: tokio::macros::scoped_tls::ScopedKey<T>::set
   7: tokio::runtime::scheduler::multi_thread::worker::run
   8: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
   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/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/alloc/src/boxed.rs:1987:9
      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/alloc/src/boxed.rs:1987:9
      std::sys::unix::thread::Thread::new::thread_start
             at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys/unix/thread.rs:108:17
  14: <unknown>
  15: <unknown>

(node:5793) UnhandledPromiseRejectionWarning: Error: Open(InvalidPath)
(Use `1password --trace-warnings ...` to show where the warning was created)
(node:5793) 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)
  • vitalyzdanevich
    vitalyzdanevich
    Community Member
    Options

    I tried to send diagnostics, got another silent error:

    ERROR 2023-06-09T15:01:49.056 tokio-runtime-worker(ThreadId(6)) [1P:op-app/src/app/backend.rs:264] AppError at op-app/src/app/backend/settings.rs:92:17
LinuxError(DBus(MethodError(OwnedErrorName(ErrorName(Str(Owned("org.freedesktop.DBus.Error.ServiceUnknown")))), Some("The name org.freedesktop.FileManager1 was not provided by any .service files"), Msg { type: Error, sender: UniqueName(Str(Borrowed("org.freedesktop.DBus"))), reply-serial: 2, body: Signature("s") })))

Stack backtrace:
   0: op_app::app::backend::settings::settings::{{closure}}
   1: op_app::app::backend::async_task::{{closure}}
   2: op_executor::spawn_no_span::{{closure}}
   3: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
   4: tokio::runtime::task::harness::Harness<T,S>::poll
   5: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
   6: tokio::runtime::scheduler::multi_thread::worker::Context::run
   7: tokio::macros::scoped_tls::ScopedKey<T>::set
   8: tokio::runtime::scheduler::multi_thread::worker::run
   9: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
  10: tokio::runtime::task::harness::Harness<T,S>::poll
  11: tokio::runtime::blocking::pool::Inner::run
  12: std::sys_common::backtrace::__rust_begin_short_backtrace
  13: core::ops::function::FnOnce::call_once{{vtable.shim}}
  14: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/alloc/src/boxed.rs:1987:9
      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/alloc/src/boxed.rs:1987:9
      std::sys::unix::thread::Thread::new::thread_start
             at /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/std/src/sys/unix/thread.rs:108:17
  15: <unknown>
  16: <unknown>

Error occurred in handler for 'invoke': [Error: LinuxError(DBus(MethodError(OwnedErrorName(ErrorName(Str(Owned("org.freedesktop.DBus.Error.ServiceUnknown")))), Some("The name org.freedesktop.FileManager1 was not provided by any .service files"), Msg { type: Error, sender: UniqueName(Str(Borrowed("org.freedesktop.DBus"))), reply-serial: 2, body: Signature("s") })))]
  • vitalyzdanevich
    vitalyzdanevich
    Community Member
    Options

    Upgraded to 8.10.16, when running from terminal I see this error:

    INFO  2023-10-11T15:01:55.635 tokio-runtime-worker(ThreadId(26)) [1P:data/op-file-transfer/src/lib.rs:307] Using the local cache for this file
ERROR 2023-10-11T15:01:55.635 tokio-runtime-worker(ThreadId(26)) [1P:op-app/src/app/backend.rs:296] Write(OpOpen(InvalidPath))
(node:7230) UnhandledPromiseRejectionWarning: Error: Write(OpOpen(InvalidPath))
(Use `1password --trace-warnings ...` to show where the warning was created)
(node:7230) 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)
  • FrankyO1P
    FrankyO1P
    Options

    Hi @vitalyzdanevich,

    I'm sorry to hear you've experienced this issue. I'd like to look into this issue further.

    Could you send an email to support+linux@1Password.com?

    With your email please include:

    We'll look forward to hearing from you.

  • vitalyzdanevich
    vitalyzdanevich
    Community Member
    Options

    From your link, point 4

    Click Reveal.

    do nothing. What location should I check?

  • FrankyO1P
    FrankyO1P
    Options

    Hi @vitalyzdanevich,

    I'm sorry to hear that the default file manager did not open when you clicked reveal. Usually 1Password for Linux will open the default file manager using the path /home/Desktop.

    You should be able to find the file there. Attach this diagnostics report to your email and we'll take a look and see what we can find.

    Franky

  • vitalyzdanevich
    vitalyzdanevich
    Community Member
    Options

    I have /home/vitaly/Desktop and no new files here.

  • klieber
    klieber
    Community Member
    edited October 2023
    Options

    I had a similar issue - try running:

    find ~/ -type f -name "*1pdiagnostics*"

    That should find the file(s).

  • FrankyO1P
    FrankyO1P
    edited October 2023
    Options

    Hi @vitalyzdanevich,

    I'm sorry to hear the diagnostics report did not show in your desktop folder. I'd like to ask you to complete the following:

    1. Recreate the problem by trying to download an attachment in 1Password for Linux.
    2. Open your file browser and go to ~/.config/1Password/
    3. Compress the logs folder and attach it to an email at support+linux@1Password.com.

    With your email please include:

    I apologize for the inconvenience and hope to hear from you soon!

    Franky

    ref: dev/core/core#15581

  • EGr
    EGr
    Community Member
    Options

    Was there any resolution on this? I'm seeing the same (or similar) with 1Password for Linux 8.10.18 on Ubuntu 22.04

  • FrankyO1P
    FrankyO1P
    Options

    Hi @EGr,

    I'm sorry to hear you're also experiencing this issue. To further investigate the issue, I'd like to ask you to also complete the following:

    1. Recreate the problem by trying to download an attachment in 1Password for Linux.
    2. Open your file browser and go to ~/.config/1Password/
    3. Compress the logs folder and attach it to an email at support+linux@1Password.com.

    With your email please include:

    I apologize for the inconvenience and hope to hear from you soon!

    Franky

  • cediddi
    cediddi
    Community Member
    Options

    I'm also having this issue and I can't understand why. It was working before I reinstalled my operating system.

  • FrankyO1P
    FrankyO1P
    Options

    Hi @cediddi

    I'm sorry to hear you're also experiencing this issue. To further investigate the issue, I'd like to ask you to also complete the following:

    Could you send an email to support+linux@1Password.com?

    With your email please include:

    We'll look forward to hearing from you.

    Franky