Etcher won't launch on Fedora 35. #3647

offensivetester · 2021-12-03T18:46:07Z

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?

The text was updated successfully, but these errors were encountered:

lurch · 2021-12-04T14:21:48Z

Duplicate of #3639 ?

adatum · 2022-03-04T20:19:18Z

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: electron/electron#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.

leillo1975 · 2022-04-07T10:19:09Z

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 "$@"

kayD · 2022-07-19T10:27:42Z

I have the same problem with version 1.7.9 on Ubuntu Jammy (22.04) (German output)

{12:11}/opt/Backup/balena-etcher ➭ ./balenaEtcher-1.7.9-x64.AppImage 
[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
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)
[41390:0719/121157.390911:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
/tmp/.mount_balenauPPptM/balena-etcher-electron: Zeile 10: 41390 Trace/Breakpoint ausgelöst   (Speicherabzug geschrieben) "${script_dir}"/balena-etcher-electron.bin "$@"

theofficialgman · 2022-09-16T14:58:08Z

@mcraa can you update etcher to electron >=14 or v13.5.0 (which has the change backported) instead of just marking issues

as you must be aware now, this is due to a GLIBC change on the host that required electron changes electron/electron#31091 . etcher uses an ancient 12.X.Y electron version and this needs to be updated for multiple reasons (security fixes, wayland improvements in recent versions, etc)

mcraa · 2022-09-16T15:19:51Z

@theofficialgman
Yes, I am aware, thanks for the reminder anyway.
By v14 there are so many breaking changes that would mean an almost complete rewrite.
{spoiler alert} Then why not a more recent version like v18? {/spoiler alert}
But with that, you don't want to exclude any of the current users so it is a lot of checking to prove it works like before.

theofficialgman · 2022-09-16T15:32:09Z

@mcraa and how about v13 then (v13.5.0+ which has the fix)? does this have any breaking changes that are critical to function?

yes I knew that one of the electron versions fundamentally changed how it worked (though it was 15 but I guess its 14) but a rewrite needs to be done at some point. Software which can't run an modern systems isn't helpful.

theofficialgman · 2022-09-16T15:34:04Z

But with that, you don't want to exclude any of the current users so it is a lot of checking to prove it works like before.

electron 18/19/20 have the same glibc minimum requirements as v12 across all linux platforms and great wayland/xorg compatibility. the external dependencies are still the same

mcraa · 2022-09-16T15:51:44Z

When bumping the version needs quite some effort and it will need the same effort in a short time, I think focusing on the rewrite with a more future-proof version makes sense. It is a pity that from the outside it looks like nothing is happening for a long time.

theofficialgman · 2022-09-16T23:02:53Z

When bumping the version needs quite some effort and it will need the same effort in a short time, I think focusing on the rewrite with a more future-proof version makes sense. It is a pity that from the outside it looks like nothing is happening for a long time.

this is just untrue and you know it. you have had over a year to deal with this issue and nothing has been done at all. all you do is bump the version from 12.x.y to ^13.5.0 and build. I have already checked v13 and there don't appear to be any breaking api changes that you depend on in it. please list any api changes you are aware of that prevent this simple change

theofficialgman · 2022-11-13T16:43:57Z

@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

adatum · 2022-11-13T19:47:23Z

@theofficialgman Since you've already tested locally, maybe you could make a pull request?

theofficialgman · 2022-11-14T00:45:12Z

@theofficialgman Since you've already tested locally, maybe you could make a pull request?

a PR is not what the devs want. they don't want to update, that is clear. For some reason they are opposed to doing anything. They would rather the bug reports pile up. They said it would be "quite some effort" and that it would "need a lot of checking to prove it works as before" (both of these quotes are from higher up the thread)

lurch · 2022-11-15T08:42:15Z

For some reason they are opposed to doing anything.

I wouldn't go that far - there's been a whole heap of updates recently? https://github.com/balena-io/etcher/blob/master/CHANGELOG.md
(although I dunno if any of them fix the original issue mentioned?)

theofficialgman · 2022-11-15T12:49:12Z

For some reason they are opposed to doing anything.

I wouldn't go that far - there's been a whole heap of updates recently? https://github.com/balena-io/etcher/blob/master/CHANGELOG.md (although I dunno if any of them fix the original issue mentioned?)

Yes I can go that far. There were no commits for over 6 months. All the commits from the last week are BOT merges simply bumping the version of dependencies. Except for one commit that changes how webpack is used to build the application, there haven't been any real changes.
Nothing changed to affect this bug either.

ThatOhio · 2022-12-01T19:39:01Z

Just chiming in to say that this same error happens on Pop!_OS.

pavgup · 2023-01-13T21:38:45Z

Found a solution by running with /opt/balenaEtcher/balena-etcher-electron --in-process-gpu -- not entirely certain if this is the right move.

mcraa · 2023-01-16T11:56:10Z

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

adatum · 2023-01-16T18:33:25Z

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

mcraa · 2023-01-16T18:38:02Z

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

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

Most package managers warn you about that, but thanks for pointing it out.
The name change made it from the command line launch work more or in more cases out of the box.

theofficialgman · 2023-01-16T18:39:00Z

over a year late and 4 months after I said there were no issues... its about time you make the minor version bump. finally its been done

nearly a year late but upstream finally updated to 13.6.9 after my recommendation 4 months ago balena-io/etcher#3647 (comment)

This was referenced May 17, 2022

balenaEtcher (upstream needs to update to electron 13+) Botspot/pi-apps#1828

Closed

Not opening in Ubuntu 22.04 #3761

Open

mcraa mentioned this issue Jun 20, 2022

I can´t open balena etcher in Ubuntu 22.04 #3777

Closed

mcraa closed this as completed Jan 16, 2023

theofficialgman added a commit to Botspot/pi-apps that referenced this issue Jan 31, 2023

BalenaEtcher: update to latest stable 1.14.3 version

83c2fa6

nearly a year late but upstream finally updated to 13.6.9 after my recommendation 4 months ago balena-io/etcher#3647 (comment)

theofficialgman mentioned this issue Jan 28, 2024

Debian Testing has removed gconf2 packages. #4096

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Etcher won't launch on Fedora 35. #3647

Etcher won't launch on Fedora 35. #3647

offensivetester commented Dec 3, 2021 •

edited

Loading

lurch commented Dec 4, 2021

adatum commented Mar 4, 2022 •

edited

Loading

leillo1975 commented Apr 7, 2022 •

edited by jellyfish-bot

Loading

kayD commented Jul 19, 2022 •

edited by jellyfish-bot

Loading

theofficialgman commented Sep 16, 2022

mcraa commented Sep 16, 2022

theofficialgman commented Sep 16, 2022

theofficialgman commented Sep 16, 2022 •

edited

Loading

mcraa commented Sep 16, 2022

theofficialgman commented Sep 16, 2022

theofficialgman commented Nov 13, 2022 •

edited

Loading

adatum commented Nov 13, 2022

theofficialgman commented Nov 14, 2022 •

edited

Loading

lurch commented Nov 15, 2022

theofficialgman commented Nov 15, 2022 •

edited

Loading

ThatOhio commented Dec 1, 2022

pavgup commented Jan 13, 2023

mcraa commented Jan 16, 2023

adatum commented Jan 16, 2023

mcraa commented Jan 16, 2023

theofficialgman commented Jan 16, 2023 •

edited

Loading

Etcher won't launch on Fedora 35. #3647

Etcher won't launch on Fedora 35. #3647

Comments

offensivetester commented Dec 3, 2021 • edited Loading

lurch commented Dec 4, 2021

adatum commented Mar 4, 2022 • edited Loading

leillo1975 commented Apr 7, 2022 • edited by jellyfish-bot Loading

kayD commented Jul 19, 2022 • edited by jellyfish-bot Loading

theofficialgman commented Sep 16, 2022

mcraa commented Sep 16, 2022

theofficialgman commented Sep 16, 2022

theofficialgman commented Sep 16, 2022 • edited Loading

mcraa commented Sep 16, 2022

theofficialgman commented Sep 16, 2022

theofficialgman commented Nov 13, 2022 • edited Loading

adatum commented Nov 13, 2022

theofficialgman commented Nov 14, 2022 • edited Loading

lurch commented Nov 15, 2022

theofficialgman commented Nov 15, 2022 • edited Loading

ThatOhio commented Dec 1, 2022

pavgup commented Jan 13, 2023

mcraa commented Jan 16, 2023

adatum commented Jan 16, 2023

mcraa commented Jan 16, 2023

theofficialgman commented Jan 16, 2023 • edited Loading

offensivetester commented Dec 3, 2021 •

edited

Loading

adatum commented Mar 4, 2022 •

edited

Loading

leillo1975 commented Apr 7, 2022 •

edited by jellyfish-bot

Loading

kayD commented Jul 19, 2022 •

edited by jellyfish-bot

Loading

theofficialgman commented Sep 16, 2022 •

edited

Loading

theofficialgman commented Nov 13, 2022 •

edited

Loading

theofficialgman commented Nov 14, 2022 •

edited

Loading

theofficialgman commented Nov 15, 2022 •

edited

Loading

theofficialgman commented Jan 16, 2023 •

edited

Loading