-
-
Notifications
You must be signed in to change notification settings - Fork 650
Trigger re-test #3616
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
base: master
Are you sure you want to change the base?
Trigger re-test #3616
Conversation
probonopd
commented
Dec 13, 2025
- ossia-score: update buggy screenshot #3604
|
It doesn't pass the test anymore, unlike back in the day. Apparently the program has now gained additional dependencies which are missing in the AppImage or are not being loaded from there. cc @jcelerier |
|
Arf, these are all dependencies that I have found out to have to be loaded specifically from the OS as they could sometimes cause crashes due to changing ABIs / protocols on various distros. So I added a banner script that would check for them on the host OS. e.g. an appimage cannot ship the pipewire or jackd binaries but I had too many problems of people telling me that it wouldn't work and it turns out these basic dependencies wouldn't be installed on their system. Same for v4l2 where shipping a more recent version is a recipe for crashes, it's too tied to the kernel version. But shipping an older one means that users on newer distros won't have the entirety of the supported pixel formats their kernel provide. |
|
Did it work without Pipewire and jack in older versions? |
|
it "works" in the sense that it's possible to run it but I get too much complaints to not have a banner warning people that they won't get all the features |
|
Maybe it'd be possible to make the message non-fatal - show it but continue with just ALSA? |
|
It wouldn't fix the screenshot issue though if it shows first, nor the issues for xcb and xkbcommon ; neither for v4l2, libbluetooth and avahi which are also all tied to either services / daemons with unstable IPC across service versions (for bluetooth and avahi) and kernel versions (for v4l2) running on the host. |
|
maybe I could try to detect if there is an env var set and skip that check though, which will fix at least since they are all dlopen'd or interacted with through some IPC. This won't fix OTOH the following, but I'd really assume they are on any GUI Linux: |