Skip to content
This repository was archived by the owner on May 12, 2026. It is now read-only.
This repository was archived by the owner on May 12, 2026. It is now read-only.

.deb package file is broken #244

Description

@825i

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

Activity

  1. Rokt33r commented on Dec 30, 2019

    @Rokt33r
    Member

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

  2. RyanGreenup commented on Dec 30, 2019

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

  3. Rokt33r commented on Jan 3, 2020

    @Rokt33r
    Member

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

  4. Rokt33r commented on Jan 4, 2020

    @Rokt33r
    Member

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

  5. changed the title [-]"Trace/breakpoint trap"[/-] [+].deb package file is broken[/+] on Jan 4, 2020
  6. RyanGreenup commented on Jan 5, 2020

    @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) ...
  7. Rokt33r commented on Jan 14, 2020

    @Rokt33r
    Member

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

  8. Rokt33r commented on Jan 29, 2020

    @Rokt33r
    Member

    @RyanGreenup #319 Please follow this issue. I'll try to resolve in this week.

  9. self-assigned this
    on Feb 13, 2020
  10. Rokt33r commented on Feb 14, 2020

    @Rokt33r
    Member

    @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

  11. added this to the v0.2.0 milestone on Feb 14, 2020
  12. philippludwig commented on May 11, 2020

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

  13. Flexo013 commented on May 11, 2020

    @Flexo013
    Contributor

    @philippludwig What OS are you running on?

  14. 12 remaining items

  15. Rokt33r commented on Feb 22, 2021

    @Rokt33r
    Member

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

  16. modified the milestones: v0.2.0, on Feb 22, 2021
  17. rome-legacy commented on Jul 25, 2021

    @rome-legacy

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

  18. removed this from the milestone on Aug 24, 2021
  19. added
    help wanted 🆘Pull request/issue requires extra help from the community. Check these out if you're new!
    and removed
    bug 🐛Issue concerns a bug.
    on Aug 25, 2021
  20. Rokt33r commented on Aug 25, 2021

    @Rokt33r
    Member

    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
  21. revive commented on Sep 7, 2021

    @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.
    
  22. issuehunt-oss commented on Sep 14, 2021

    @issuehunt-oss

    @boostio has funded $20.00 to this issue.


  23. added
    funded on issuehunt 💵Issue has received funding that will be rewarded to the contributor solving this issue.
    on Sep 14, 2021
  24. added
    hacktoberfestContribute to the Boost Note and grab the swags! https://hacktoberfest.digitalocean.com/
    on Oct 4, 2021
  25. removed
    hacktoberfestContribute to the Boost Note and grab the swags! https://hacktoberfest.digitalocean.com/
    on Nov 9, 2021
  26. exitflynn commented on Feb 11, 2023

    @exitflynn

    is this issue still active?

  27. shriram-svg commented on May 12, 2026

    @shriram-svg

    Opened PR #1689 to apply the Linux no-sandbox launch flag both in package launcher metadata and in the packaged Electron main process: #1689

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

funded on issuehunt 💵Issue has received funding that will be rewarded to the contributor solving this issue.help wanted 🆘Pull request/issue requires extra help from the community. Check these out if you're new!needs investigation 🔬Issue requires further investigation to locate or narrow down the problem.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions