etcher: Etcher won't launch on Fedora 35.

Etcher version: Latest (1.7.1)
Operating system and architecture: Fedora Linux 35 (Workstation Edition)
Image flashed: None

I tried to run the AppImage, but every time I execute ./balenaEtcher-1.7.1-x64.AppImage I get an error. This is the log:

[Axios v1.7.1] Transitional option 'clarifyTimeoutError' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.1] Transitional option 'forcedJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.1] Transitional option 'silentJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
{"message":"certificate has expired","stack":"Error: certificate has expired\n    at TLSSocket.onConnectSecure (_tls_wrap.js:1497:34)\n    at TLSSocket.emit (events.js:315:20)\n    at TLSSocket._finishInit (_tls_wrap.js:932:8)\n    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:706:12)","config":{"url":"https://balena.io/etcher/static/config.json","method":"get","headers":{"Accept":"application/json, text/plain, */*","User-Agent":"axios/1.7.1"},"transformRequest":[null],"transformResponse":[null],"timeout":0,"responseType":"json","xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1,"transitional":{"silentJSONParsing":true,"forcedJSONParsing":true,"clarifyTimeoutError":false}},"code":"CERT_HAS_EXPIRED"}
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[64615:1203/204326.427485:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
/tmp/.mount_balenalHVK8D/balena-etcher-electron: line 10: 64615 Trace/breakpoint trap   (core dumped) "${script_dir}"/balena-etcher-electron.bin "$@"

What do I do?

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 21 (6 by maintainers)

Commits related to this issue

BalenaEtcher: update to latest stable 1.14.3 version nearly a year late but upstream finally updated to 13.6.9 after my recommendation 4 months ago https://github.com/balena-io/etcher/issues/3647#iss... — committed to Botspot/pi-apps by theofficialgman a year ago

Most upvoted comments

Have the same problem on Ubuntu Jammy (22.04):

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[585023:0407/121615.076630:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
/tmp/.mount_balenaYKd1PH/balena-etcher-electron: liña 10: 585023 Trampa de seguemento/punto de ruptura             («core» xerado) "${script_dir}"/balena-etcher-electron.bin "$@"

leillo1975 on Apr 7, 2022

Same problem with etcher v1.7.7 and Fedora 35

$ /opt/balenaEtcher/balena-etcher-electron
[Axios v1.7.7] Transitional option 'clarifyTimeoutError' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.7] Transitional option 'forcedJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
[Axios v1.7.7] Transitional option 'silentJSONParsing' has been deprecated since v1.0.0 and will be removed in the near future
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[286457:0304/150419.065587:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
/opt/balenaEtcher/balena-etcher-electron: line 10: 286457 Trace/breakpoint trap   (core dumped) "${script_dir}"/balena-etcher-electron.bin "$@"

This appears to be due to a bug in electron which has been fixed: https://github.com/electron/electron/pull/31091 Etcher probably needs to be rebuilt with a newer version of electron to fix this issue.

It works if launched with the --no-sandbox or --disable-gpu-sandbox or --disable-seccomp-filter-sandbox flag but this is not advised.

adatum on Mar 4, 2022

@pavgup could you try v1.13.0 and above, should not need to add any args then.

Resolved at last! v13.3 launches properly.

I had to first uninstall balena-etcher-electron as the old package was named, otherwise the installation of balena-etcher failed due to conflicts.

adatum on Jan 16, 2023

@pavgup could you try v1.13.0 and above, should not need to add any args then.

mcraa on Jan 16, 2023

@mcraa still no fix? like I said. litearlly you need zero changes. bump to electron 13.5.0+ and spectron to 15.0.0 for testing. it works fully without this issue. I have built and tested locally with no problems.

a full rewrite can (and should) come later for modern electron

theofficialgman on Nov 13, 2022