.deb package file is broken

[825i]

Current behavior

After running

root@debian:/opt/Boost Note# chown root chrome-sandbox
root@debian:/opt/Boost Note# chmod 4755 chrome-sandbox

I receive the error

Trace/breakpoint trap

The software does not run.

Expected behavior

Boostnote should open.

Steps to reproduce

1. Download the .deb file from the Boostnote website
2. Install the .deb and dependencies with

dpkg -i boostnote.deb
apt install -f

3. Change ownership of chrome-sandbox as above.
4. Error occurs when trying to open the app via the terminal command " boostnote "
5. Trying to open boostnote with the application icon doesn't work either.

Environment

• Version: v0.14.0-0
• OS Version and name: Debian 10.1 buster

Snapcraft

P.S. I know it is not related but please consider adding this software to the Snapcraft Library to make the installation and update process MUCH easier on Linux: https://snapcraft.io/first-snap

---

IssueHunt Summary

Backers (Total: $20.00)

• boostio ($20.00)

Become a backer now!

Or submit a pull request to get the deposits!

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

[Rokt33r]

@pythonInRelay We are also providing AppImage. https://github.com/BoostIO/BoostNote.next/releases It might be better than snapcraft. How do you think?

[RyanGreenup]

@Rokt33r The advantage to snap (or any package manager e.g. apt or pacman is that all packages can be updated with one command, e.g on Ubuntu/Mint/Debian you could update the entire system and all programs with:

sudo apt update
sudo apt upgrade
sudo snap refresh

Moreover, Snap will automatically put the package into a location that is in the path, whereas with a .appimage the user needs to edit there ~/.profile to add something like ~/bin to the path.

So although an app image is really convenient, snap would be even easier because users wouldn’t need to watch Github for releases.

[Rokt33r]

@RyanGreenup Okay, I'll try snap soon. Btw did you also confront this problem?

[Rokt33r]

I confirmed the deb package file is broken. I'll replace its link with the AppImage link until I fix this problem

[RyanGreenup]

@Rokt33r I have not actually encountered this problem with v 0.1.1, although I install the new version over the old version so maybe that's why, it might be nice to give the binary a slightly different name so the old version and new version can be run concurrently.

udo dpkg -i boost-note-linux.deb
dpkg: warning: downgrading boostnote from 0.14.0-0-1 to 0.1.1
(Reading database ... 853268 files and directories currently installed.)
Preparing to unpack boost-note-linux.deb ...
Unpacking boostnote (0.1.1) over (0.14.0-0-1) ...
Setting up boostnote (0.1.1) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.24-1ubuntu1) ...
Processing triggers for mime-support (3.63ubuntu1) ...
Processing triggers for gnome-menus (3.32.0-1ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...

[Rokt33r]

@RyanGreenup I'll change the name in this month. Until I change it, please use AppImage one.

[Rokt33r]

@RyanGreenup https://github.com/BoostIO/BoostNote.next/issues/319 Please follow this issue. I'll try to resolve in this week.

[Rokt33r]

@RyanGreenup @pythonInRelay Both of your issues should be fixed in v0.2.1. Please try it and reopen the issue if the problem still exist. https://github.com/BoostIO/BoostNote.next/releases/tag/v0.2.1

[philippludwig]

Sadly this issue still occurs, at least for me on Debian. However, this is not unique to the .deb package; the AppImage does not work either.

[Flexo013]

@philippludwig What OS are you running on?

[philippludwig]

As I wrote above, I am running Debian. The release is 10.4.

[luoxiao78]

same here, also using Debian 10.

[Flexo013]

Reopening this as it still seems to be an issue with the latest version.

@philippludwig @luoxiao78 Do either of you have Boostnote and BoostNote.next installed? What version are you trying to install? (Probs 0.4.1)

[philippludwig]

I installed the boost-note-linux.deb package from the main page, which carries version 0.4.1 apparently.

[myOmikron]

Same here, running Debian bullseye/sid. I'm getting following error when executing the binary or the AppImage:

[116110:0529/134857.575581:FATAL:setuid_sandbox_host.cc(157)] 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_boost-v4zR1R/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap

When I'm correcting the Sandbox permissions only the last line appears.

[SamsiFPV]

I've got the same problem, also running Debian 10 Buster. Boostnote.next version 0.6.1

[AkhilVinayakp]

Getting a trace trap "/opt/Boost Note/boostnote.next" error in parrot linux 4.8

[revive]

I got the same issue on Debian 10.4 with the latest deb package.

[Rokt33r]

Thanks for the reporting. I'll check again in this week.

[pablodz]

Same here, using Debian 10 64bits. With Boostnote.next version 0.12.4 and .deb package Also with .AppImage package

After one hour checking for solutions, we need to run --no-sandbox arg to run the program. See below:

In Debian with KDE Plasma you need to add --no-sandbox like the image below in properties

[Rokt33r]

@ZurMaD Thanks for the comment. Apparently we can set the argument by default. I'll try to apply it from the next version. https://github.com/electron-userland/electron-builder/pull/4364

[rome-legacy]

had the same problem with latest deb package on debian buster --no-sandbox flag helped to get app running. thx

[Rokt33r]

Is there anyone able to try the steps below? I don't have a device using Debian so it is a bit difficult for me to test the solution.

1. set ["--no-sandbox"] to "build.linux.executableArgs" of package.json

  "linux": {
    "icon": "static/icon.icns",
    "target": [
      "deb",
      "rpm",
      "AppImage"
    ],
    // Add the below
    "executableArgs": [
      "--no-sandbox"
    ]
  },

2. Add .env file

NODE_ENV=production
BOOST_HUB_BASE_URL=https://boostnote.io

3. Run these script

npm run build:electron
npm run pack

4. Test .deb and .AppImage files in dist directory

[revive]

@Rokt33r I tried with my Debian box, currently with Debian 10.9. It seems that the additional argments of "--no-sandbox" in the package.json file does not resolve the problem. When I tried to run the generated boost-note-linux.AppImage, I got following messages

[16145:0907/093219.679087:FATAL:setuid_sandbox_host.cc(158)] 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_boost-yPAGMj/chrome-sandbox is owned by root and has mode 4755.

[issuehunt-oss[bot]]

@boostio has funded $20.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[exitflynn]

is this issue still active?