-
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. |
Same on Ubuntu 22.04 with balenaEtcher-1.19.21-x64.AppImage. |
same issue on fedora 39 and balena-etcher-1.19.21-1.x86_64.rpm |
PR welcomes :) |
fixed by running as administrator on windows |
Same error here on Fedora 40 with Wayland. Using version 1.18.11 this issue does not appears. The link below is to this version that worked for me. |
Old version 1.18.11 worked for me. @aethernet Can we rollback recent changes from 1.19.11 to 1.18 ? This is a regression blocker to use it. |
Hello, |
balenaEtcher-1.19.21-x64.AppImage on Ubuntu 20.04, same issue 1.18.11 works |
for ubuntu on windows, worked for me thanks |
Hi all, it happened to me as well but worked when I fixed the issue on my own system, ubuntu 24.04. I suggest to run the program through terminal, then when you encounter this issue you can see more detailed log in the terminal. In my case it is said that there was no space to write on device. The error message is more descriptive there and might not be belong to balena. Hope it helps. |
Same issue here on Fedora 40. Spent a bit of time debugging. Running from terminal with --no-sandbox and checking output I got to: DRM kernel driver 'nvidia-drm' in use. NVK requires nouveau. |
I also had the same problem when I plugged in two USB devices, then I unplugged one of the devices, restarted ether, and there was no error when I selected the image file again |
@qichengzx it worked for me also, Actually, I copied the iso file from USB pendrive to my system and then trying to open it in etcher, but got this (0, h.requestMetadata) error. Then I removed the USB and restarted the etcher and now no error. I'm installing Linux Mint Cinnamon 21.6 on Windows 10 as my secondary OS. Thanks to @qichengzx |
That worked. Had the same issue with win10 and newest version from Website. Removing USB flash and restarting program fixed issue while loading image. Thank you! Till the image is loading very long, a loading spinner would be nice to be sure the program didn't crashed |
I downgraded to 1.18.11 to overcome the issue. |
I had same issue on Win 10. Even running as Administrator does not work as others mentioned here. When I run with --no-sandbox option, it resolved the issue. Then start it with the option, e.g.: |
current version broken, can confirm this, windows 10, same "requestMetaData" error. 1.18.11 indeed still works, but sad for this project that no one fixes this longer existing error ... |
Same problem on Ubuntu 22.04.4 LTS and AppImage. Running on 1.18.11 worked flawlessly. |
same on mac m1 sonoma 14.5 |
Win10. This was the only aforementioned method that worked for me. |
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: