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

.deb package should depend on libasound2 #3985

Open
dkg opened this issue Jun 28, 2024 · 3 comments
Open

.deb package should depend on libasound2 #3985

dkg opened this issue Jun 28, 2024 · 3 comments
Labels
bug Something isn't working build build and release related issues

Comments

@dkg
Copy link

dkg commented Jun 28, 2024

  • Operating System (Linux/Mac/Windows/iOS/Android): debian stable (12.5), amd64 (x86_64) architecture
  • Delta Chat Version: 1.46.1 (from .deb package)
  • Expected behavior: launching deltachat from the command line as "deltachat-desktop" should work.
  • Actual behavior: fails with deltachat-desktop: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory
  • Steps to reproduce the problem: do a minimal debian stable installation. as the superuser: apt install --no-install-recommends ./deltachat-desktop_1.46.1_amd64.deb. as a normal, non-priv user, run deltachat-desktop from a terminal emulator within a graphical session
@hpk42 hpk42 added bug Something isn't working build build and release related issues labels Jul 1, 2024
@nicodh
Copy link
Contributor

nicodh commented Jul 8, 2024

Can't reproduce this. Can you be more specific what kind of graphical session you mean.
It seems even a minimal desktop brings the required dependencies?

Might be related to electron-userland/electron-builder#4346 which is pretty old...

@link2xt
Copy link
Collaborator

link2xt commented Jul 16, 2024

electron-userland/electron-builder#4346 seems to be closed by stale bot without fixing, so the problem is likely still there.

@Simon-Laux
Copy link
Member

Simon-Laux commented Aug 1, 2024

https://www.electron.build/configuration/linux#debian-package-options

seems then we need to specify all dependencies it needs, not only the new/missing one. (setting it seems to replace the default selection, not argument it, when I understand the docs correctly)

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

No branches or pull requests

5 participants