Ubuntu 20.04.1 LTS Crash [Investigating]

fpk
fpk
Community Member
edited November 2021 in Desktop betas (Mac, Windows, and Linux)

While the registration was easy and successful, the client silently crashed right after launch. I can run it again from bash, but it a) flickers from time to time (which I also experience with the Vivaldi browser, btw.) and b) will also crash after a few minutes. This is on Ubuntu 20.04.1 LTS (5.4.0-51-generic, 64bit) with Nvidia drivers (nvidia-driver-450, proprietary, tested).

The output to bash is:
$ 1password
INFO 2020-10-23T20:33:58.112 op_executor:invocation_loop [op-app/src/app.rs:132] App::new(/ (EN_US), Some())
INFO 2020-10-23T20:33:58.124 op_executor:invocation_loop [op-app/src/app/backend/config.rs:33] Settings changed.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
INFO 2020-10-23T20:34:08.897 op_executor:invocation_loop [op-data-layer/src/load.rs:216] loaded items in vaults for account:
ERROR 2020-10-23T20:34:08.898 op_executor:invocation_loop [op-app/src/app/backend/unlock.rs:92] NotImplemented
INFO 2020-10-23T20:34:08.898 op_executor:invocation_loop [op-app/src/app/backend/unlock.rs:100] Lock state changed: Unlocked
INFO 2020-10-23T20:34:08.898 ThreadId(21) [client:typescript] Lock Manager started.
INFO 2020-10-23T20:34:15.223 tokio-runtime-worker [op-data-layer/src/sync.rs:159] synced account:
INFO 2020-10-23T20:34:15.223 op_executor:invocation_loop [op-data-layer/src/load.rs:56] reloading data layer...
INFO 2020-10-23T20:34:15.275 op_executor:invocation_loop [op-data-layer/src/load.rs:216] loaded items in vaults for account:
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
[...]
ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
Gtk-Message: 20:43:23.838: Failed to load module "canberra-gtk-module"
Gtk-Message: 20:43:23.839: Failed to load module "canberra-gtk-module"
Opening in existing browser session.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
[276085:1023/204324.596739:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)

On another run I also encountered:
$ 1password
INFO 2020-10-23T20:52:23.772 op_executor:invocation_loop [op-app/src/app.rs:132] App::new(/ (EN_US), Some())
INFO 2020-10-23T20:52:23.783 op_executor:invocation_loop [op-app/src/app/backend/config.rs:33] Settings changed.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
INFO 2020-10-23T20:52:34.949 op_executor:invocation_loop [op-data-layer/src/load.rs:216] loaded items in vaults for account:
ERROR 2020-10-23T20:52:34.949 op_executor:invocation_loop [op-app/src/app/backend/unlock.rs:92] NotImplemented
INFO 2020-10-23T20:52:34.949 op_executor:invocation_loop [op-app/src/app/backend/unlock.rs:100] Lock state changed: Unlocked
INFO 2020-10-23T20:52:34.950 ThreadId(21) [client:typescript] Lock Manager started.
INFO 2020-10-23T20:52:41.389 tokio-runtime-worker [op-syncer/src/sync_job.rs:576] Updated items in vault
INFO 2020-10-23T20:52:41.546 tokio-runtime-worker [op-syncer/src/sync_job.rs:576] Updated items in vault
INFO 2020-10-23T20:52:41.581 tokio-runtime-worker [op-data-layer/src/sync.rs:159] synced account:
INFO 2020-10-23T20:52:41.581 op_executor:invocation_loop [op-data-layer/src/load.rs:56] reloading data layer...
INFO 2020-10-23T20:52:41.649 op_executor:invocation_loop [op-data-layer/src/load.rs:216] loaded items in vaults for account:
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
[...]
ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
Gtk-Message: 20:52:44.904: Failed to load module "canberra-gtk-module"
Gtk-Message: 20:52:44.905: Failed to load module "canberra-gtk-module"
Opening in existing browser session.
ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
Warning: 'sandbox' is not in the list of known options, but still passed to Electron/Chromium.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
Warning: 'sandbox' is not in the list of known options, but still passed to Electron/Chromium.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure

I have just installed 1Password by adding the repository and then installing 1Password via apt. Let me also emphasize that this is the single most important feature for me since I have become a customer - I am very much looking forward to using this client. Thank you very much for implementing it.

PS:
It is not trivial to lookup the version. I assume it would be possible via apt show 1password, but suggest to make the version clearly accessible in the application. If that is already possible, it was not obvious where to find it.

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Ubuntu 20.04.1
Sync Type: Not Provided
Referrer: forum-search:Ubuntu 20.04 crash

Comments

  • fpk
    fpk
    Community Member

    Interestingly, this even happens when disabling GPU acceleration via the CLI:

    $ 1password --disable-gpu --disable-software-rasterizer
    INFO 2020-10-23T21:03:00.283 op_executor:invocation_loop [op-app/src/app.rs:132] App::new(/ (EN_US), Some())
    INFO 2020-10-23T21:03:00.295 op_executor:invocation_loop [op-app/src/app/backend/config.rs:33] Settings changed.
    INFO 2020-10-23T21:03:12.340 op_executor:invocation_loop [op-data-layer/src/load.rs:216] loaded items in vaults for account:
    ERROR 2020-10-23T21:03:12.340 op_executor:invocation_loop [op-app/src/app/backend/unlock.rs:92] NotImplemented
    INFO 2020-10-23T21:03:12.340 op_executor:invocation_loop [op-app/src/app/backend/unlock.rs:100] Lock state changed: Unlocked
    INFO 2020-10-23T21:03:12.341 ThreadId(21) [client:typescript] Lock Manager started.
    ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
    INFO 2020-10-23T21:03:18.681 tokio-runtime-worker [op-data-layer/src/sync.rs:159] synced account:
    INFO 2020-10-23T21:03:18.681 op_executor:invocation_loop [op-data-layer/src/load.rs:56] reloading data layer...
    INFO 2020-10-23T21:03:18.729 op_executor:invocation_loop [op-data-layer/src/load.rs:216] loaded items in vaults for account:
    ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
    ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:CRASHING:(tg)kill() failure
    [279830:1023/210357.601749:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
    Trace/breakpoint trap (core dumped)

  • fpk
    fpk
    Community Member

    The AppImage version exhibits the same problem.

  • fpk
    fpk
    Community Member
    edited October 2020

    Uninstalling 1Password and reinstalling it via snap (snap install --edge 1password) seems to work more robustly, but also prints errors:

    The old binary seems to keep an invalid link, so I have to find the snap binary first:
    $ 1password
    bash: /usr/bin/1password: No such file or directory
    $ which 1password
    /snap/bin/1password

    And when launching the snap binary, it seems more stable and does not flicker (afaict), but it prints a 2FA error (that might also have been present in the repository version which I didn't run from bash on first execution):
    $ /snap/bin/1password
    ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
    [...]
    ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
    INFO 2020-10-23T21:15:00.298 op_executor:invocation_loop [op-app/src/app.rs:132] App::new(/ (EN_US), Some())
    INFO 2020-10-23T21:15:00.414 op_executor:invocation_loop [op-db/src/sqlite/db.rs:93] Database is being created at
    INFO 2020-10-23T21:15:00.450 op_executor:invocation_loop [op-app/src/app/backend/config.rs:33] Settings changed.
    ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
    ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
    INFO 2020-10-23T21:15:22.603 op_executor:invocation_loop [op-b5-client/src/internal/unauthorized_session.rs:66] registered device
    ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
    WARN 2020-10-23T21:15:39.251 op_executor:invocation_loop [op-b5-client/src/internal/unauthorized_session.rs:415] Failed to save an account's 2FA token with an error of SystemKeyringError(LinuxError(DbusError(D-Bus error: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.1995" (uid=1000 pid=282815 comm="/snap/1password/11/app/1password --no-sandbox " label="snap.1password.1password (enforce)") interface="org.freedesktop.Secret.Service" member="OpenSession" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=2338 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined") (org.freedesktop.DBus.Error.AccessDenied),),),). 2FA will only be valid for this unlock session!
    INFO 2020-10-23T21:15:40.161 op_executor:invocation_loop [op-syncer/src/sync_job.rs:576] Updated items in vault
    INFO 2020-10-23T21:15:40.977 op_executor:invocation_loop [op-syncer/src/sync_job.rs:576] Updated items in vault
    INFO 2020-10-23T21:15:41.366 op_executor:invocation_loop [op-syncer/src/sync_job.rs:576] Updated items in vault
    INFO 2020-10-23T21:15:41.539 op_executor:invocation_loop [op-syncer/src/sync_job.rs:576] Updated items in vault
    INFO 2020-10-23T21:15:41.606 op_executor:invocation_loop [op-data-layer/src/load.rs:216] loaded items in vaults for account:
    ERROR 2020-10-23T21:15:41.611 op_executor:invocation_loop [op-app/src/app/backend/signin.rs:170] NotImplemented
    INFO 2020-10-23T21:15:41.611 op_executor:invocation_loop [op-app/src/app/backend/signin.rs:179] Lock state changed: Unlocked
    INFO 2020-10-23T21:15:41.612 op_executor:invocation_loop [op-data-layer/src/load.rs:56] reloading data layer...
    ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
    INFO 2020-10-23T21:15:41.621 ThreadId(47) [client:typescript] Lock Manager started.
    INFO 2020-10-23T21:15:41.638 op_executor:invocation_loop [op-data-layer/src/load.rs:216] loaded items in vaults for account:

    To my best knowledge, the snap version seems to work (1password 0.9.0, rev. 11, latest/edge).

  • MikeT
    MikeT

    Hi @fpk,

    Thanks for reporting this. We're not able to yet reproduce this but we're looking into it. It looks like Brave had the same issue and it had to do with the enable-oop-rasterization flag.

    While we're investigating what the crash could be, the 2FA error is expected because by default, snaps don't have default permission to integrate with the system's keyring.

    If you open up your software center or snap tool to manage permissions, you should be able to give 1Password permission to integrate with the system's keyring. Here's more details: https://1password.community/discussion/115935/1password-for-linux-2fa-faq

  • fpk
    fpk
    Community Member

    Thank you - hope you figure out how to reproduce this. Could be related to GPU/SLI? I'm a little surprised this works with snap and not apt-get - usually it's the other way around. Maybe the system specs help:

    OS: Ubuntu 20.04.1 LTS x86_64
    Host: Z390 DESIGNARE
    Kernel: 5.4.0-52-generic
    Uptime: 2 days, 14 hours, 4 mins
    Packages: 3267 (dpkg), 20 (snap)
    Shell: bash 5.0.17
    Resolution: 3840x2160, 3840x2160, 3840x2160
    DE: GNOME
    WM: Mutter
    WM Theme: Adwaita
    Theme: Yaru-dark [GTK2/3]
    Icons: Yaru [GTK2/3]
    Terminal: gnome-terminal
    CPU: Intel i7-8700K (12) @ 4.700GHz
    GPU: NVIDIA GeForce GTX 1080 Ti
    GPU: NVIDIA GeForce GTX 1080 Ti
    Memory: 8656MiB / 64256MiB
    NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020
    GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)

  • MikeT
    MikeT

    Hi @fpk,

    We haven't been able to see this yet. Can you tell us if anything has changed since your last post here with our recent updates and OS updates as well?

  • fpk
    fpk
    Community Member

    I don't quite recall this issue, but the ESET errors are caused by ESET Security Suite to the best of my knowledge. The core application now seems to work fine, so I suggest we close this as solved for now. Thanks for following up.

  • Dayton_ag
    Dayton_ag

    Hey @fpk, glad to hear things are working! We're always happy to help out if you run into this (or any) issue in the future. :smile: We're here for you!

This discussion has been closed.