gqrx fails to start due to a symbol lookup error on Fedora 42. This is the package information: ``` $ dnf info gqrx Aktualisiere und lade Paketquellen: Paketquellen geladen. Installierte Pakete Name : gqrx Epoch : 0 Version : 2.17.6 Release : 2.fc42 Architektur : x86_64 Installationsgröße : 1.9 MiB Quelle : gqrx-2.17.6-2.fc42.src.rpm Aus dem Repository : fedora Zusammenfassung : Software defined radio receiver powered by GNU Radio and Qt URL : https://gqrx.dk/ Lizenz : GPL-3.0-or-later AND GPL-2.0-or-later AND LicenseRef-Callaway-BSD Beschreibung : Gqrx is a software defined radio receiver powered by the GNU Radio SDR : framework and the Qt graphical toolkit. Anbieter : Fedora Project ``` When starting gqrx from the command line, we can see the symbol ookup error. ``` $ gqrx gqrx: symbol lookup error: /lib64/libosmodsp.so.0: undefined symbol: _ZGVbN4v_sinf ``` Reproducible: Always Steps to Reproduce: 1. install gqrx from dnf 2. start it from start menue: nothing seems to happen 3. starting from cmdline shows the symbol lookup error Actual Results: I got this error: gqrx: symbol lookup error: /lib64/libosmodsp.so.0: undefined symbol: _ZGVbN4v_sinf Expected Results: Would be great, if gqrx would start up.
It seems the problem is in the libosmo-dsp, reassigning.
Upstream bug report: https://osmocom.org/issues/6764
FEDORA-2025-c36ebf2a00 (libosmo-dsp-0.3-27.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-c36ebf2a00
FEDORA-2025-c36ebf2a00 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c36ebf2a00` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c36ebf2a00 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-c36ebf2a00 (libosmo-dsp-0.3-27.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.