You are not logged in.
Hello Arch Linux maintainers and community,
I am writing to report a critical packaging issue. The recent build of GNU Jami (`jami-qt`) is completely broken because it was pushed to the official repositories without proper runtime verification. It feels like a sloppy compilation job.
Here is the exact terminal error log when trying to launch the application:
jami: symbol lookup error: /usr/lib/libjami.so.17: undefined symbol: ydoc_observe_updates_v1
Please start testing all packages manually before pushing them to users. Rolling release is fine, but shipping completely untested, non-functional binaries feels unprofessional.
To anyone who might respond with "just use Flatpak" or "well, that's just rolling release for you" — my answer is that rolling release packages must be held back for basic smoke testing. Let's remember the XZ Utils backdoor incident: it was caught only because an attentive developer was actually testing and measuring sshd performance. If we blindly pull, compile, and ship upstream code without any runtime checks, we will keep getting broken builds like this, or worse, critical security incidents.
Also, to anyone who tells me to go open a formal bug report on GitLab — I literally cannot. I tried to register an account using multiple email addresses, including my main Gmail account, but the Arch Linux sign-up filter instantly flags and bans my accounts (likely because I am using LibreWolf for privacy). The registration system is completely hostile to new users.
Since I am locked out of the official issue tracker, I am posting this here. If you have an active, verified Arch GitLab account, please forward this bug to the distribution developers and package maintainers immediately.
Offline
jami: symbol lookup error: /usr/lib/libjami.so.17: undefined symbol: ydoc_observe_updates_v1
Cannot reproduce.
$ ldd /usr/bin/jami
$ pacman -Q jami-daemon y-crdt
$ pacman -Qkk jami-daemon y-crdtLast edited by dimich (Yesterday 22:39:04)
Offline