Arch Linux User Repository

That’s a Chromium/Electron sandbox issue, based on the distro you're using, not an anytype-specific crash. Electron-based AppImages try to use Chromium’s sandbox helper (chrome-sandbox), which needs setuid permissions to work correctly. On some systems with stricter defaults, this fails and the AppImage “aborts” instead of running.

[FATAL:sandbox/linux/suid/client/setuid_sandbox_host.cc:169] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_anytyp*/chrome-sandbox is owned by root and has mode 4755.

Run:

  mount | grep /tmp

If it shows nosuid, it means all binaries under /tmp can't use setuid, and that kills the sandbox.

You can then test user namespace support with:

    sysctl kernel.unprivileged_userns_clone

If it's 0, the kernel doesn't allow unprivileged sandboxes and electron sandbox will fail. But if it's 1, then it's allowed.

If it's 0, you can try enabling it temporarily running:

    sudo sysctl -w kernel.unprivileged_userns_clone=1

If it then runs, without extra params, you will need to alternate the appimage deployment, but you will have confirmed that it's a distro issue and not the package issue.

Adding --no-sandbox to the Exec line in anytype.desktop solved the issue.

That’s a Chromium/Electron sandbox issue, based on the distro you're using, not an anytype-specific crash. Electron-based AppImages try to use Chromium’s sandbox helper (chrome-sandbox), which needs setuid permissions to work correctly. On some systems with stricter defaults, this fails and the AppImage “aborts” instead of running.

[FATAL:sandbox/linux/suid/client/setuid_sandbox_host.cc:169] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_anytyp*/chrome-sandbox is owned by root and has mode 4755.

Run:

  mount | grep /tmp

If it shows nosuid, it means all binaries under /tmp can't use setuid, and that kills the sandbox.

You can then test user namespace support with:

    sysctl kernel.unprivileged_userns_clone

If it's 0, the kernel doesn't allow unprivileged sandboxes and electron sandbox will fail. But if it's 1, then it's allowed.

If it's 0, you can try enabling it temporarily running:

    sudo sysctl -w kernel.unprivileged_userns_clone=1

If it then runs, without extra params, you will need to alternate the appimage deployment, but you will have confirmed that it's a distro issue and not the package issue.

Adding --no-sandbox to the Exec line in anytype.desktop solved the issue.

Thank you for this package Kaleb/(@phil-gru)!

I use Anytype for a lot of notes and courses. I am having an issue with this version.

System Specs:

• OS: Omarchy 3.3.0 (Arch-based)
• WM: Hyprland 0.53.1 (Wayland)
• CPU: 12th Gen Intel Core
• GPU: Intel Iris Xe Graphics
• RAM: 40 GB

Issue:

Launching anytype-bin via Walker/uwsm or terminal fails with Chromium sandbox errors from the AppImage:

[FATAL:sandbox/linux/suid/client/setuid_sandbox_host.cc:169] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_anytyp*/chrome-sandbox is owned by root and has mode 4755.

After adding --disable-setuid-sandbox, it still crashed with: [FATAL:content/browser/zygote_host/zygote_host_impl_linux.cc:132] No usable sandbox! If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.

Cause:

AppImages mount under /tmp with nosuid, so Chromium’s SUID sandbox cannot work...

Fix:

Adding --no-sandbox to the Exec line in anytype.desktop solved the issue. My working Exec line:

Exec=anytype --no-sandbox %U

I am happy it's now working but hopefully there's a future fix or something else I could do so the --no sandbox flag is unneeded in the future? Thank you!

Hey zw9seq it seems that you are not the only one with the problem: https://github.com/anyproto/anytype-ts/issues/1748

I don’t know if you have a chance to register a new vault on a mobile device (Android or iOS). Maybe you could try to copy the key from there and paste that key into the desktop app. Otherwise, you’ll have to wait until it’s fixed.

I´d really like to use this app but im having problems with the passkey. I've tried using this package and even the official AppImage file but I still find the same error. When starting the app for first time, in the passkey screen (where u can copy the 12 words) the field for the pass appears empty and doesn't let me copy any value. Later in the setting of the app it happens the same; it doesn't show any value. Can anyone help me?

Thank you, @phil-gru! I successfully installed version 51.1.

@neo-clon It works on my machine. You might should clear the yay cache or delete the anytype-bin folder in your cache from yay. I forgot to add the checksum of anytype.desktop yesterday, but I added about 40 minutes later.

The cache from yay on may system was in: /home/$USER/.cache/yay/anytype-bin/ You can also use yay -Sc to clear the full cache of yay.

Checksum invalid

==> Validating source files with sha256sums... Anytype-0.51.0.AppImage ... Passed anytype.desktop ... FAILED anytype.png ... Passed ==> ERROR: One or more files did not pass the validity check!

Thx guys for maintaining and your effort. It is highly appreciated!

That's fine, it's a AUR feature that i don't really like, that the one requesting does not have a priority, but the more people helping, the better. Just add me as a co-maintainer and i'll be sure to help if you miss anything.

Hey Kaleb, I adopted the package shortly after it was disowned since I actively use it and plan to keep it up to date. Sorry the timing was a bit unfortunate, I hadn't noticed that you were the one who submitted the orphan request.

If you'd like, I can add you as a co-maintainer so we can maintain it together or if you'd rather take over maintaining it yourself, just let me know. Otherwise, I plan to keep the package consistently updated.