-
Notifications
You must be signed in to change notification settings - Fork 5
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
missing dependencies on debian #28
Comments
Hello, I would like to add the following dependency-error to this issue:
With yields the following error:
|
With v0.0.45 the original dependency error disappears. |
Nice! I have no idea what change actually fixed it but 🤷 Glad its working |
I'm still facing the issue on Debian on Chrome OS, and I need to do the symbolic links mention by @c-mahn.
|
Hmm yeah, honestly I no idea why this is happening.. |
Well for now, as a kind of a workaround, I'm using the web app and have created it as a PWA on the Chromebook and in the Chrome browser. Works perfectly. |
@mrmaceurope, @c-mahn which version of the app are you using? .deb or .appimage? Can you please share more of your os and environment? (If you are not using a .deb package on a debian/fork of debian os, then I suggest to open a new ticket.) |
I downloaded the latest deb package, version v0.0.45. I tried to install it simply, just by clicking it on the https://music-assistant.io/companion-app/#debian-and-debian-based-distrobutions, and then launched the package from the Chrome OS side, which started the installation but ended with error. Since this installation method doesn't generally provide many details, I tried installing the package from the terminal - where I got the same mentioned errors as listed above and reported by @c-mahn. The ChromeOS Debian OS information
|
@cociweb I have currently installed the version 0.0.45 as amd64.deb under Debian 12. My current error-message after having done the steps above is still the following: |
Same here..
The error changes to:
|
You should get the same path for all of them.... Something like this: (if none of them, available install one of them, Eg.:
|
Hey I think i found the issue, could you guys try the new version (v0.0.54)? I did a lot of core changes and updated to the tauri 2.0 beta and also changed the openssl dependency to use vendored version. |
Merging with #11 |
Actually in 54 another issue arose, so its not fixed yet.. |
@arctixdev, maybe we can give a try for add libssl3 after libssl-dev (libssl-dev is based on libssl1.1) during build time. I don't really know, is there any effect of it, maybe. |
Yeah that could also help. Right now I am facing an error with the builds not getting uploaded to Github. But I will try a quick workaround just for now |
[off]
You have /home/runner/work/companion/companion/src-tauri/target/release/bundle/deb/Music Assistant Companion_0.0.56_amd64.deb only rpm is ok. |
Could you try the new version? (v0.0.57) |
Yeah i screwed up the path a few times.... |
Well, I had no issue with 0.45. but with 0.57 I've got another (new) one, and the app not starts: |
Oh damn.... Well, i am heading for bed now. I am pretty busy for the next couple of days. So fixing this will probably get delayed a bit... sorry. Till then you should be able to just continue to use v45 |
Actually it looks like its just because i switched it to build on ubuntu 24.04 https://tauri.app/v1/guides/building/linux/#limitations i will give it a shot now |
umm, in the meantime I see you have upgraded the build environment from ubuntu 20.04 to 24.04. on this release, the libssl3 is identical with libssl4t64. libssl-dev is lies on the same package libssl3t64. which have further dependency the libc6. |
Hm yeah... Looks like there are no runners picking up the ubuntu 18 job https://github.com/music-assistant/companion/actions/runs/9341463384/job/25708266887 😆 Gonna try 20 again |
my recommendation is to try with 22.04 since libssl3 is introduced on jammy, but we will get the same libc6, and maybe that will be the root cause in this lbssl1.1 vs libssl3 issue. |
Ah ok, yeah... Just tried with 20 now but can update if it dosnt fix it. Just thought to go as low as possible to support as many versions as possible |
Ok i am gonna go to bed now. I am way to tired to deal with this now 🤣 |
If you want you can create a pr and I could run the action to test it. But dont feel obligated to do so |
Couldnt help myself, got the build working in ubuntu 22, could you maybe test the newest release? |
As of now (0.0.65) it is working fine for me again, but I had no issues with incorrect ssl version in the past, so we need another confirmation from the guys above. As a plus, the relaunch of the app is working again. (y) |
Ah super cool! |
Version 0.0.65 seems to has fixed my issues. |
Ok super cool, closing this issue now then. If anyone has issue just comment / reopen |
Hello,
I'm getting the following log messages of the debian companion app, when i select the "show info" submenu of a yt (or local media) music element:
The text was updated successfully, but these errors were encountered: