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

[BUG] cannot execute binary file: Exec format error #213

Closed
cantalupo555 opened this issue May 16, 2024 · 11 comments
Closed

[BUG] cannot execute binary file: Exec format error #213

cantalupo555 opened this issue May 16, 2024 · 11 comments
Assignees
Labels
bug Something isn't working

Comments

@cantalupo555
Copy link

cantalupo555 commented May 16, 2024

Bug Description
cannot execute binary file: Exec format error

To Reproduce
Using the latest Flatpak package.
Version: 3.17.4

Screenshots
image

Info (please complete the following information):

  • Operating system: Ubuntu 24.04 LTS (ARM64)
  • App version: 3.17.4
  • Package version: flatpak
@cantalupo555 cantalupo555 added the bug Something isn't working label May 16, 2024
@aandrew-me
Copy link
Owner

Interesting, I noticed that you're using arm64 processor.
Can you please provide the output of the command uname -m

And if you can (would be very helpful), download from here , ffmpeg_linux_arm64 , give it execution permission with chmod +x ffmpeg_linux_arm64 and see if it executes.

Thanks for reporting

@cantalupo555
Copy link
Author

I don't understand what could have happened, before it worked normally.

image

image

Log

cantalupo@orangepi5:~$ flatpak run io.github.aandrew_me.ytdn 
[3:0518/193438.195278:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Gtk-Message: 19:34:38.815: Failed to load module "canberra-gtk-module"
Gtk-Message: 19:34:38.816: Failed to load module "canberra-gtk-module"
[3:0518/193438.866473:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0518/193438.866650:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Locale:en-US
Version: 3.17.4
bounds: {}
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
glx: failed to create dri3 screen
failed to load driver: rockchip
APPIMAGE env is not defined, current application is not an AppImage
[42:0518/193439.074714:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
glx: failed to create dri3 screen
failed to load driver: rockchip
[91:0518/193439.312440:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
Auto update: true
Warning: vkCreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
    at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
    at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)
    at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344)
    at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)
    at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521)

@aandrew-me
Copy link
Owner

Oh so it worked fine before? Maybe try uninstalling the package (with its data) and installing again

@aandrew-me
Copy link
Owner

I am closing due to inactivity

@aandrew-me aandrew-me closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2024
@cantalupo555
Copy link
Author

Find out how to solve this @aandrew-me

@cantalupo555
Copy link
Author

cantalupo555 commented Jun 2, 2024

For it to work, it is essential to have access to /home
I solved this using "Flatseal".
https://flathub.org/apps/com.github.tchx84.Flatseal

Even with permission for the flatpak package to have access to the /home directory, another problem is emerging.
image

It downloads a wrong version of ytdlp for Linux, I need the aarch64 architecture.
I don't know if the problem is with flatpak or yt-dlp-wrap-plus-2.3.18 (downloadFromGithub).
image

@aandrew-me aandrew-me reopened this Jun 2, 2024
@aandrew-me
Copy link
Owner

Thanks for the info, I'm gonna find the problem and fix it

@cantalupo555
Copy link
Author

cantalupo555 commented Jun 2, 2024


image

image


So, I decided to manually replace yt-dlp_linux_aarch64
https://github.com/yt-dlp/yt-dlp/releases/download/2024.05.27/yt-dlp_linux_aarch64
image

Now ytDownloader is working again.
image

@aandrew-me
Copy link
Owner

aandrew-me commented Jun 2, 2024

Yes I see. The issue is with the yt-dlp-wrap-plus dependency. I didn't write it, I forked it from another one and made some modifications, so I can fix it

@aandrew-me
Copy link
Owner

Should be fine in latest release

@cantalupo555
Copy link
Author

cantalupo555 commented Jun 4, 2024

Great!
Big work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants