[GH-ISSUE #244] .deb package file is broken #84

Open
opened 2026-03-03 00:18:13 +03:00 by kerem · 26 comments
Owner

Originally created by @825i on GitHub (Dec 29, 2019).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/244

Originally assigned to: @Rokt33r on GitHub.

Issuehunt badges

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
  1. Change ownership of chrome-sandbox as above.
  2. Error occurs when trying to open the app via the terminal command " boostnote "
  3. 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)

Become a backer now!

Or submit a pull request to get the deposits!

Tips

Originally created by @825i on GitHub (Dec 29, 2019). Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/244 Originally assigned to: @Rokt33r on GitHub. <!-- Issuehunt Badges --> [<img alt="Issuehunt badges" src="https://img.shields.io/badge/IssueHunt-%2420%20Funded-%2300A156.svg" />](https://issuehunt.io/r/BoostIO/BoostNote-App/issues/244) <!-- /Issuehunt Badges --> # 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 content --> --- <details> <summary> <b>IssueHunt Summary</b> </summary> ### Backers (Total: $20.00) - [<img src='https://avatars3.githubusercontent.com/u/13612118?v=4' alt='boostio' width=24 height=24> boostio](https://issuehunt.io/u/boostio) ($20.00) #### [Become a backer now!](https://issuehunt.io/r/BoostIO/BoostNote-App/issues/244) #### [Or submit a pull request to get the deposits!](https://issuehunt.io/r/BoostIO/BoostNote-App/issues/244) ### Tips - Checkout the [Issuehunt explorer](https://issuehunt.io/r/BoostIO/BoostNote-App/) to discover more funded issues. - Need some help from other developers? [Add your repositories](https://issuehunt.io/r/new) on IssueHunt to raise funds. </details> <!-- /Issuehunt content-->
Author
Owner

@Rokt33r commented on GitHub (Dec 30, 2019):

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

<!-- gh-comment-id:569658173 --> @Rokt33r commented on GitHub (Dec 30, 2019): @pythonInRelay We are also providing AppImage. https://github.com/BoostIO/BoostNote.next/releases It might be better than snapcraft. How do you think?
Author
Owner

@RyanGreenup commented on GitHub (Dec 30, 2019):

@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.

<!-- gh-comment-id:569818931 --> @RyanGreenup commented on GitHub (Dec 30, 2019): @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: ```bash 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.
Author
Owner

@Rokt33r commented on GitHub (Jan 3, 2020):

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

<!-- gh-comment-id:570699736 --> @Rokt33r commented on GitHub (Jan 3, 2020): @RyanGreenup Okay, I'll try snap soon. Btw did you also confront this problem?
Author
Owner

@Rokt33r commented on GitHub (Jan 4, 2020):

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

<!-- gh-comment-id:570739780 --> @Rokt33r commented on GitHub (Jan 4, 2020): I confirmed the deb package file is broken. I'll replace its link with the AppImage link until I fix this problem
Author
Owner

@RyanGreenup commented on GitHub (Jan 5, 2020):

@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) ...
<!-- gh-comment-id:570953876 --> @RyanGreenup commented on GitHub (Jan 5, 2020): @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. ```bash 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) ... ```
Author
Owner

@Rokt33r commented on GitHub (Jan 14, 2020):

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

<!-- gh-comment-id:574343214 --> @Rokt33r commented on GitHub (Jan 14, 2020): @RyanGreenup I'll change the name in this month. Until I change it, please use AppImage one.
Author
Owner

@Rokt33r commented on GitHub (Jan 29, 2020):

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

<!-- gh-comment-id:579613115 --> @Rokt33r commented on GitHub (Jan 29, 2020): @RyanGreenup https://github.com/BoostIO/BoostNote.next/issues/319 Please follow this issue. I'll try to resolve in this week.
Author
Owner

@Rokt33r commented on GitHub (Feb 14, 2020):

@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

<!-- gh-comment-id:586251706 --> @Rokt33r commented on GitHub (Feb 14, 2020): @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
Author
Owner

@philippludwig commented on GitHub (May 11, 2020):

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.

<!-- gh-comment-id:626528331 --> @philippludwig commented on GitHub (May 11, 2020): 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.
Author
Owner

@Flexo013 commented on GitHub (May 11, 2020):

@philippludwig What OS are you running on?

<!-- gh-comment-id:626837977 --> @Flexo013 commented on GitHub (May 11, 2020): @philippludwig What OS are you running on?
Author
Owner

@philippludwig commented on GitHub (May 11, 2020):

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

<!-- gh-comment-id:626962300 --> @philippludwig commented on GitHub (May 11, 2020): As I wrote above, I am running Debian. The release is 10.4.
Author
Owner

@luoxiao78 commented on GitHub (May 13, 2020):

same here, also using Debian 10.

<!-- gh-comment-id:628254321 --> @luoxiao78 commented on GitHub (May 13, 2020): same here, also using Debian 10.
Author
Owner

@Flexo013 commented on GitHub (May 18, 2020):

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)

<!-- gh-comment-id:630347645 --> @Flexo013 commented on GitHub (May 18, 2020): 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)
Author
Owner

@philippludwig commented on GitHub (May 18, 2020):

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

<!-- gh-comment-id:630389981 --> @philippludwig commented on GitHub (May 18, 2020): I installed the `boost-note-linux.deb` package from the main page, which carries version 0.4.1 apparently.
Author
Owner

@myOmikron commented on GitHub (May 29, 2020):

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.

<!-- gh-comment-id:635929795 --> @myOmikron commented on GitHub (May 29, 2020): 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.
Author
Owner

@SamsiFPV commented on GitHub (Jun 12, 2020):

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

<!-- gh-comment-id:643524898 --> @SamsiFPV commented on GitHub (Jun 12, 2020): I've got the same problem, also running Debian 10 Buster. Boostnote.next version 0.6.1
Author
Owner

@AkhilVinayakp commented on GitHub (Jul 1, 2020):

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

<!-- gh-comment-id:652214939 --> @AkhilVinayakp commented on GitHub (Jul 1, 2020): Getting a trace trap "/opt/Boost Note/boostnote.next" error in parrot linux 4.8
Author
Owner

@revive commented on GitHub (Jul 2, 2020):

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

<!-- gh-comment-id:652849516 --> @revive commented on GitHub (Jul 2, 2020): I got the same issue on Debian 10.4 with the latest deb package.
Author
Owner

@Rokt33r commented on GitHub (Jul 21, 2020):

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

<!-- gh-comment-id:662021434 --> @Rokt33r commented on GitHub (Jul 21, 2020): Thanks for the reporting. I'll check again in this week.
Author
Owner

@pablodz commented on GitHub (Feb 7, 2021):

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

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

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

<!-- gh-comment-id:774732471 --> @pablodz commented on GitHub (Feb 7, 2021): Same here, using Debian 10 64bits. ![image](https://user-images.githubusercontent.com/28235457/107156356-d1e76a80-694b-11eb-8977-faffdc1e2c2d.png) With Boostnote.next version 0.12.4 and `.deb` package Also with `.AppImage` package ![image](https://user-images.githubusercontent.com/28235457/107156535-d8c2ad00-694c-11eb-8233-eee5da21ca69.png) After one hour checking for solutions, we need to run `--no-sandbox` arg to run the program. See below: ![image](https://user-images.githubusercontent.com/28235457/107156591-33f49f80-694d-11eb-8d81-eb567866fdd1.png) ![image](https://user-images.githubusercontent.com/28235457/107156600-41118e80-694d-11eb-936c-e0089b80ff5b.png) In Debian with KDE Plasma you need to add `--no-sandbox` like the image below in properties ![image](https://user-images.githubusercontent.com/28235457/107157565-bb90dd00-6952-11eb-8b7d-48fb61728f66.png)
Author
Owner

@Rokt33r commented on GitHub (Feb 22, 2021):

@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

<!-- gh-comment-id:783107350 --> @Rokt33r commented on GitHub (Feb 22, 2021): @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
Author
Owner

@rome-legacy commented on GitHub (Jul 25, 2021):

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

<!-- gh-comment-id:886172666 --> @rome-legacy commented on GitHub (Jul 25, 2021): had the same problem with latest deb package on debian buster --no-sandbox flag helped to get app running. thx
Author
Owner

@Rokt33r commented on GitHub (Aug 25, 2021):

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"
    ]
  },
  1. Add .env file
NODE_ENV=production
BOOST_HUB_BASE_URL=https://boostnote.io
  1. Run these script
npm run build:electron
npm run pack
  1. Test .deb and .AppImage files in dist directory
<!-- gh-comment-id:905268090 --> @Rokt33r commented on GitHub (Aug 25, 2021): 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 ```js "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
Author
Owner

@revive commented on GitHub (Sep 7, 2021):

@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.
<!-- gh-comment-id:913927957 --> @revive commented on GitHub (Sep 7, 2021): @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. ```
Author
Owner

@issuehunt-oss[bot] commented on GitHub (Sep 14, 2021):

@boostio has funded $20.00 to this issue.


<!-- gh-comment-id:918966178 --> @issuehunt-oss[bot] commented on GitHub (Sep 14, 2021): [@boostio](https://issuehunt.io/u/boostio) has funded $20.00 to this issue. --- - Submit pull request via [IssueHunt](https://issuehunt.io/repos/74213528/issues/244) to receive this reward. - Want to contribute? Chip in to this issue via [IssueHunt](https://issuehunt.io/repos/74213528/issues/244). - Checkout the [IssueHunt Issue Explorer](https://issuehunt.io/issues) to see more funded issues. - Need help from developers? [Add your repository](https://issuehunt.io/r/new) on IssueHunt to raise funds.
Author
Owner

@exitflynn commented on GitHub (Feb 11, 2023):

is this issue still active?

<!-- gh-comment-id:1426703273 --> @exitflynn commented on GitHub (Feb 11, 2023): is this issue still active?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/BoostNote-App#84
No description provided.