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

libz.so: cannot open shared object file with Ubuntu arm64 #7835

Closed
yanguoyu opened this issue Oct 20, 2023 · 5 comments
Closed

libz.so: cannot open shared object file with Ubuntu arm64 #7835

yanguoyu opened this issue Oct 20, 2023 · 5 comments
Labels

Comments

@yanguoyu
Copy link

  • Electron-Builder Version: ^24.6.4
  • Node Version: >=18
  • Electron Version: ^26.2.1
  • Electron Type (current, beta, nightly):
  • Target: Ubuntu arm64

I can not open the AppImage on Ubuntu arm64, and when I execute with the terminal it throws en error, here is the log: "Error while loading shared libraries: libz.so: cannot open shared object file: No such file or directory."

Here is the repo that I package for Ubuntu arm64, I fork from electron-react-boilerplate, and here is the package result.
The x64 result runs successfully on the x64 Ubuntu.

@yanguoyu
Copy link
Author

https://github.com/yanguoyu/electron-quick-start is a smaller repo for reproducing this problem.

https://github.com/yanguoyu/electron-quick-start/actions/runs/6586287443 is the electron-builder build result. It runs failed on Ubuntu arm64.

https://github.com/yanguoyu/electron-quick-start/actions/runs/6586287445 is the electron-forge build result. It runs successfully on Ubuntu arm64.

@toastmanAu
Copy link

Hmm... I also found this: AppImage/AppImageKit#1092 (comment) Does that work?

Not sure if related but seems the team who referenced the same issue elsewhere found a solution.

@Keith-CY
Copy link

Keith-CY commented Mar 5, 2024

Hmm... I also found this: AppImage/AppImageKit#1092 (comment) Does that work?

Not sure if related but seems the team who referenced the same issue elsewhere found a solution.

Hi @toastmanAu
Sorry for replying late. @yanguoyu had tried this solution and found it requires users to install/link a dependency locally, as stated at ChurchApps/FreeShow#352 (comment)

IMO, it cannot be considered a solution because unnecessary complexity was introduced that users should be told about the problem and how to fix it before they download the application. The better one is to fix the dependency problem before the application is delivered to users.

Copy link
Contributor

github-actions bot commented May 5, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the Stale label May 5, 2024
Copy link
Contributor

github-actions bot commented Jun 5, 2024

This issue was closed because it has been stalled for 30 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants