Description of problem: Audacity fails to start Version-Release number of selected component (if applicable): audacity.x86_64 2.1.2-0.7.rc1.fc23 How reproducible: Steps to Reproduce: 1. Run 'audacity' from command line Actual results: "audacity: symbol lookup error: audacity: undefined symbol: _ZN10soundtouch10SoundTouch14setTempoChangeEf" Expected results: Audacity opens
I'm only seeing the string _ZN10soundtouch10SoundTouch14setTempoChangeEd in the file /usr/lib64/libSoundTouch.so.1.9.2. soundtouch-1.9.2-3.fc23.x86_64 on my end.
Same happens here. I'm on Fedora 23 Cinnamon Spin. Just updated and I get this error: audacity: symbol lookup error: audacity: undefined symbol: _ZN10soundtouch10SoundTouch14setTempoChangeEf
Should I change this bug to be against the "soundtouch" component?
Looking closer to the error message, seems to me the problem is in Soundtouch really and not in Audacity as a whole. So yes, Devin, I think you should change it.
Thanks Sylvia. I've updated the component.
*** Bug 1311309 has been marked as a duplicate of this bug. ***
Sorry I mess up , we need rebuild for new soundtouch 1.9.2 on F23 and F24 . https://bugzilla.redhat.com/show_bug.cgi?id=1311295
Until someone not rebuild audacity , you may downgrade soundtouch: dnf downgrade "soundtouch*"
Downgrading works fine. Thank you very much!
we need rebuild and test audacity for new soundtouch 1.9.2 on F23 and F24
I think audacity needs to be rebuilt. Soundtouch switched from floats to doubles internally. So soundtouch would have to be downgraded to get it to work, or audacity recompiled. Also, to me, floats -> doubles sounds like an improvement and I don't see the point in going back.
I agree. By now, downgrading works but it's not a solution. And as Benji says there's no point in going back. So hope this get rebuilt ASAP. Thanks!
Hi, To workaround, I built it in copr [1]: dnf copr enable sergiomb/buildsforF21 dnf update audacity and we may test with soundtouch 1.9.2 , after that you may disable it: dnf copr disable sergiomb/buildsforF21 rm /etc/yum.repos.d/_copr_sergiomb-buildsforF21.repo you won't need it anymore, sorry for the trouble . [1] https://copr.fedorainfracloud.org/coprs/sergiomb/buildsforF21/
(In reply to Sergio Monteiro Basto from comment #13) > Hi, > > To workaround, I built it in copr [1]: > > dnf copr enable sergiomb/buildsforF21 > dnf update audacity > > and we may test with soundtouch 1.9.2 , after that you may disable it: > > dnf copr disable sergiomb/buildsforF21 > rm /etc/yum.repos.d/_copr_sergiomb-buildsforF21.repo > > you won't need it anymore, sorry for the trouble . > > > [1] https://copr.fedorainfracloud.org/coprs/sergiomb/buildsforF21/ This does work.
audacity-2.1.2-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ee19511560
audacity-2.1.2-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ee19511560
audacity-2.1.2-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
this is happening on f24
Audacity is FTBFS in rawhide (and F24) [1] that's why we still haven't the rebuild of audacity in F24 (and rawhide) . [1] https://bugzilla.redhat.com/show_bug.cgi?id=1307335
audacity-2.1.2-4.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-bfddbfb488
audacity-2.1.2-4.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-bfddbfb488
audacity-2.1.2-4.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.