You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 12, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on May 12, 2026. It is now read-only.
Error occurs when trying to open the app via the terminal command " boostnote "
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
@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:
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 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) ...
@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
@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.
Activity
Rokt33r commentedon 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?
RyanGreenup commentedon Dec 30, 2019
@Rokt33r The advantage to
snap(or any package manager e.g.aptorpacmanis 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:Moreover, Snap will automatically put the package into a location that is in the path, whereas with a
.appimagethe user needs to edit there~/.profileto add something like~/binto 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 commentedon Jan 3, 2020
@RyanGreenup Okay, I'll try snap soon. Btw did you also confront this problem?
Rokt33r commentedon 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
[-]"Trace/breakpoint trap"[/-][+].deb package file is broken[/+]RyanGreenup commentedon 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.
Rokt33r commentedon Jan 14, 2020
@RyanGreenup I'll change the name in this month. Until I change it, please use AppImage one.
Rokt33r commentedon Jan 29, 2020
@RyanGreenup #319 Please follow this issue. I'll try to resolve in this week.
Rokt33r commentedon 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
philippludwig commentedon 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.
Flexo013 commentedon May 11, 2020
@philippludwig What OS are you running on?
12 remaining items
Rokt33r commentedon 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. electron-userland/electron-builder#4364
rome-legacy commentedon Jul 25, 2021
had the same problem with latest deb package on debian buster
--no-sandbox flag helped to get app running.
thx
Rokt33r commentedon 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.
["--no-sandbox"]to "build.linux.executableArgs" of package.jsondistdirectoryrevive commentedon 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 thepackage.jsonfile does not resolve the problem.When I tried to run the generated
boost-note-linux.AppImage, I got following messagesissuehunt-oss commentedon Sep 14, 2021
@boostio has funded $20.00 to this issue.
exitflynn commentedon Feb 11, 2023
is this issue still active?
shriram-svg commentedon May 12, 2026
Opened PR #1689 to apply the Linux no-sandbox launch flag both in package launcher metadata and in the packaged Electron main process: #1689