It's due to an accidental ABI change in 1.9, affecting anything compiled against 1.8 but using 1.9 at runtime.
Presumably the next upstream release will fix this - the workaround currently is to read back & save the fields again, at which point the bytes get swapped back to the correct order.
So, reassigning this to "taglib" and merging https://github.com/taglib/taglib/pull/307 would fix it?
Yes, that would fix it. Alternatively that commit has been merged into master, so the next upstream release will contain the fix too. But merging the individual fix will be a quicker fix.
taglib-1.9.1-2.fc20 has been submitted as an update for Fedora 20.
taglib-1.9.1-2.fc19 has been submitted as an update for Fedora 19.
taglib-1.9.1-2.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing taglib-1.9.1-2.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
taglib-1.9.1-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
taglib-1.9.1-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.