-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Error: (0 , h.requestMetadata) is not a function #4150
Comments
Also having this issue on Manjaro |
Like you but I'm using ArchLinux :( |
I'm getting this with version 1.18.14 on Garuda. |
Same for me on ArchLinux. |
Getting this on Nobara 38 |
Was initially trying on Hyprland, which is on Wayland. I download Cinnamon to test and Xorg environment and it worked for me. I used 1.8.13. Is anyone else on Wayland? |
I was on wayland |
I'm getting this issue on Manjaro with the 1.18.14 version from the AUR and I'm on X11. However, it lools like 1.18.14 released just a couple of days before #4132 was merged, meaning that the fix for #4138 wasn't included in that version. So any Arch/Manjaro issues (@Sargeanthost, @devM7MD, @myxor) should hopefully be fixed when 1.19.x lands on the AUR. Maybe I can try and manually build a 1.19 package and see if it works? |
It looks like the move to building with electron-forge causes build issues on Arch, and this is why the AUR package is still on version 1.18. |
I have the same issue on openSUSE using the RPM and appimage |
Same problem here with EndeavourOS. |
Same issue on Ubuntu 22.04 with X11 using balenaEtcher-1.19.3-x64.AppImage but no error when using balenaEtcher-1.18.11-x64.AppImage |
Same issue with balena-etcher-1.19.3-1.x86_64.rpm on Fedora 39 |
also have same issue with balena-etcher-1.19.3-1.x86_64.rpm on Fedora 39 |
This issue does not occur on the appimage version of Etcher |
I use archlinux ,balenaEtcher-1.18.8-x64.AppImage can use |
…v1.19.2)" This reverts commit 3906e49. Reverting update(v1.19.2 -> v1.18.12) Upstream Bug #4150 - balena-io/etcher#4150
Thanks for the reports guys. |
Getting the same on Fedora 39 with version v1.19.3. Tried both RPM and AppImage formats. Same result. |
Same on Arch on both x11 and wayland, installed with yay from aur (since people above were talking abt wayland) AppImage works fine |
Unfortunately console does not have much info |
OS: Fedora 39 Looking at the inspector the error is thrown in the
https://github.com/balena-io/etcher/blob/v1.19.4/lib/gui/app/app.ts#L139-L157 Since |
still an issue on arch |
same problem, archlinux |
Experiencing the same issue here on Manjaro and Garuda Linux with balena-etcher-2:1.18.14-1. Just as @Kaiddd commented, I can confirm that the balenaEtcher-1.5.109-x64.AppImage version works fine on both systems. |
Same issue here on ElementaryOS and Zorin OS with balenaEtcher-1.19.5-x64.AppImage. |
Experiencing this problem on my Dell XPS 9520 running Arch Linux. This is with balenaEtcher v1.18.14 from AUR, v1.18.12 AppImage, and v1.19.5 AppImage. Running GNOME 45.4 on Wayland with Intel GPU. |
|
rpmbuild strips executables by default when generating an rpm packge. This was causing the JavaScript code bundled in the etcher-util file to be removed, causing "Pkg: Error reading from file." whenever etcher-util was called. This in turn caused balena-etcher to generate the error message `Error: (0, h.requestMetadata) is not a function` when attempting to write an SD card. This fixes the issue for RPM builds by replacing the `strip` command with `true` so that rpmbuild no longer strips the executables and the embeded code stays intact. See: #4150 Signed-off-by: Richard Glidden <richard@glidden.org>
rpmbuild strips executables by default when generating an rpm packge. This was causing the JavaScript code bundled in the etcher-util file to be removed, causing "Pkg: Error reading from file." whenever etcher-util was called. This in turn caused balena-etcher to generate the error message `Error: (0, h.requestMetadata) is not a function` when attempting to write an SD card. This fixes the issue for RPM builds by replacing the `strip` command with `true` so that rpmbuild no longer strips the executables and the embeded code stays intact. See: #4150 Signed-off-by: Richard Glidden <richard@glidden.org>
Also same error opening source on LMDE6 with latest version balenaEtcher-1.19.25-x64.AppImage. |
I tested the latest AppImage version, balenaEtcher-1.19.25-x64.AppImage, on Kubuntu 22.04.5. |
I was receiving the same error - v1.19.25 and ubuntu 24.04.1 amd64 iso Subsequently, this has worked fine (twice) Just adding in case this helps anybody out. |
Same issue here with version 1.19.25-x64.appImage. Running my old version 1.7.9-x64.appImage works. |
This worked for me, too! In addition, I started the balenaEtcher using 'Run as Administrator.' |
guys. stahp. this isn't a windows-related thread. linux. 1.18.13+ appimage. we already know about the windows fix. kthxbye. <3 |
I've had the same issue with version 19 on Mac OS Monterey trying to flash an Ubuntu 24 LTS iso image. After downgrad to balenaEtcher 18.11., it worked. |
This isn't a Windows related issue. This GitHub issue is related to the Linux version of the 'AppImage'. Please find or open a separate thread for the Windows release. |
Hi Samuel,
Thanks for sharing your experience and the details about the workaround you
found! It’s great to see how others are troubleshooting similar issues.
Could you clarify more on how this relates to future updates for Windows
users? It would be helpful to understand if there’s any expected impact or
changes we should be aware of.
Looking forward to your insights!
Best,
Imad
في السبت، 19 أكتوبر 2024 في 7:41 م تمت كتابة ما يلي بواسطة Samuel Banya
***@***.***>:
… I was receiving the same error - v1.19.25 and ubuntu 24.04.1 amd64 iso
Windows 11 10.0.22631 Build 22631 The error occurred when running from
downloads *or* trying to use the iso from downloads folder I created a
folder in the root of C:\ , excluded folder from windows defender (this may
or may not have been necessary, just including for completeness)
Subsequently, this has worked fine (twice)
Just adding in case this helps anybody out.
This worked for me, too! In addition, I started the balenaEtcher using
'Run as Administrator.' Since then, I can also start the program in normal
mode, and it works without errors.
This isn't a Windows related issue. This GitHub issue is related to the
Linux version of the 'AppImage'.
Please find or open a separate thread for the Windows release.
—
Reply to this email directly, view it on GitHub
<#4150 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEBMLJHQXOAMGOPSUPEO3UDZ4KRWRAVCNFSM6AAAAABA6XXUY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGEZTIMRWG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
... It's NOT for the Windows version lol. The Windows users should file a separate thread as that's a separate OS altogether, and this issue is for the AppImage version on Linux. |
I'm having the same issue attempting to use the latest AppImage 64 Bit on Mint Linux. I have switched to the DEB installer and that has mounted the image without any issues. |
Got the same issue on oct 30, 2024. did the make compatible with windows 8.... it works... |
I ran into this issue on a Raspberry Pi 5 and could resolve it with this:
Maybe this helps some other poor soul. |
I had the problem on windows. running belenaEtcher as admin helped. |
I have the same issue on Windows 10. |
restarting etcher worked |
Same issue with: Working for me without issues: |
You may need to run it as Administrator. |
As @RodrickM says - RUN AS ADMINISTRATOR |
Guys just open balena etcher with administrator |
Dude, this is a Linux based GitHub issue. Not the same OS. |
This problem also applies to Mac OS. |
In Nixpkgs we package Etcher on the basis of the official deb. The procedure no longer works as of 1.18.13.
Likely a continuation of #4138. Probably that issue should be reopened? @dfunckt
The text was updated successfully, but these errors were encountered: