Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

balenaEtcher (upstream needs to update to electron 13+) #1828

Closed
2 tasks done
Crilum opened this issue May 16, 2022 · 18 comments
Closed
2 tasks done

balenaEtcher (upstream needs to update to electron 13+) #1828

Crilum opened this issue May 16, 2022 · 18 comments
Labels
Upstream Bug something isn't working that can only be fixed upstream

Comments

@Crilum
Copy link
Contributor

Crilum commented May 16, 2022

Confirmations

What happened?

Etcher fails with seccomp sandbox error (see #1828 (comment) for upstream issues)

Description

Etcher has been broken for some time now..
See logs below.

This might have something to do with #1

What is your operating system?

Raspberry Pi OS 11 (Bullseye)

(Optional) Error log? Terminal output? Debug messages?

$ /opt/balenaEtcher/balena-etcher-electron
[Axios v1.7.9+5945ab1f] Transitional option 'clarifyTimeoutError' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.9+5945ab1f] Transitional option 'forcedJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.9+5945ab1f] Transitional option 'silentJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
[3191:0516/164142.592492:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
/opt/balenaEtcher/balena-etcher-electron: line 10:  3191 Trace/breakpoint trap   "${script_dir}"/balena-etcher-electron.bin "$@"
@Crilum Crilum added the bug Something isn't working label May 16, 2022
@Crilum
Copy link
Contributor Author

Crilum commented May 16, 2022

Adding --disable-seccomp-filter-sandbox fixes the problem.

@ryanfortner
Copy link
Collaborator

ryanfortner commented May 16, 2022

Interesting. I built the v1.7.9 debs using Debian Buster. I’ll try with Bullseye and see if there is any difference.

In the meantime, are you able to test on Buster @Crilum ?

@Crilum
Copy link
Contributor Author

Crilum commented May 16, 2022

Yeah, I can do that.

@Crilum
Copy link
Contributor Author

Crilum commented May 16, 2022

On bullseye, etcher just stalls after selecting an image..

@ryanfortner
Copy link
Collaborator

On bullseye, etcher just stalls after selecting an image..

did you select an .xz image? I remember having problems with etcher using those in the past.

@Crilum
Copy link
Contributor Author

Crilum commented May 16, 2022

Yeah, I did actually.. It seemed to work before I did that.

@Crilum
Copy link
Contributor Author

Crilum commented May 16, 2022

It works fine in buster. I noticed during the install that chmod failed to, well, chmod /opt/balenaEtcher/chrome-sandbox. It said there was no such file or directory.

$ /opt/balenaEtcher/balena-etcher-electron
[Axios v1.7.9+5945ab1f] Transitional option 'clarifyTimeoutError' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.9+5945ab1f] Transitional option 'forcedJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.9+5945ab1f] Transitional option 'silentJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
ready-to-show: 4.397s

@ryanfortner
Copy link
Collaborator

I noticed during the install that chmod failed to, well, chmod /opt/balenaEtcher/chrome-sandbox. It said there was no such file or directory.

That is safe to ignore.

I will add this to my to-do list and get new debs released as soon as I can.

@Crilum
Copy link
Contributor Author

Crilum commented May 17, 2022

I just built on bullseye, we still have the seccomp-sandbox error:

webpack 5.11.0 compiled successfully in 41623 ms
do you want to run a test of etcher to see if compilation worked [y/n]? y
close etcher window to continue to packaging.
waiting for 5 seconds.....
Starting Etcher...

> balena-etcher@1.7.9 start
> ./node_modules/.bin/electron .

[Axios v1.7.9] Transitional option 'clarifyTimeoutError' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.9] Transitional option 'forcedJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.9] Transitional option 'silentJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403
[8023:0516/181257.120324:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
/home/pi/src/etcher/etcher/node_modules/electron/dist/electron exited with signal SIGTRAP
Etcher failed to start!

Here's the deb:

balena-etcher-electron_1.7.9%2B5945ab1f_armv7l.deb

@theofficialgman
Copy link
Collaborator

theofficialgman commented May 17, 2022

I have already told you before, this is an upstream etcher issue (balena-io/etcher#3647) due to a glibc change electron/electron#31091 . the version of electron used with etcher (12.2.3) is very very old and has this bug. they need to upgrade their codebase to one of the versions that doesn't have this issue.
The fix is available in Electron >= 14

this is an over 6 month old issue. until etcher gets their act together, just consider it unmaintained

@theofficialgman theofficialgman added Upstream Bug something isn't working that can only be fixed upstream and removed bug Something isn't working labels May 17, 2022
@Botspot
Copy link
Owner

Botspot commented May 18, 2022

Would it be worthwhile to add the --disable-seccomp-filter-sandbox flag for the time being?

@Crilum
Copy link
Contributor Author

Crilum commented May 18, 2022

@Botspot I think it would. Otherwise Etcher is completely broken for all Bullseye users..

@Botspot
Copy link
Owner

Botspot commented May 18, 2022

@Botspot I think it would. Otherwise Etcher is completely broken for all Bullseye users..

I've opened an issue on @Itai-Nelken's repo.
Itai-Nelken/BalenaEtcher-arm#6

@ryanfortner
Copy link
Collaborator

@Crilum this issue should be fixed with #1838. The desktop entry in the new debs has --disable-seccomp-filter-sandbox included in the run command.

@theofficialgman
Copy link
Collaborator

lets keep this open for tracking upstream electron, since this is only a temporary fix until they update

@theofficialgman theofficialgman changed the title balenaEtcher broken - seccomp failure balenaEtcher (upstream needs to update to electron 13+) May 18, 2022
@Botspot
Copy link
Owner

Botspot commented Jul 17, 2022

Has balena updated their Electron version yet?

@theofficialgman
Copy link
Collaborator

Etcher hasn't had a commit since April.
I think balena may have abandoned the software

@theofficialgman
Copy link
Collaborator

upstream is opposed to fixing their repo balena-io/etcher#3647 (comment)

this issue is closed in pi-apps as since the v1.10.0 release I have packaged it with electron ^13.5.0
a09e87f
https://github.com/Pi-Apps-Coders/files/blob/main/CompileCommands.md#balenaetcher

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Upstream Bug something isn't working that can only be fixed upstream
Projects
None yet
Development

No branches or pull requests

4 participants