Description of problem: Error Message: -- fontmatrix: symbol lookup error: fontmatrix: undefined symbol: _ZN9QListData7detach3Ev -- Version-Release number of selected component (if applicable): fontmatrix-0.6.99-4.r1073.fc12.x86_64 How reproducible: 100% Steps to Reproduce: 1. after updating fontmartix, run it, 2. 3. Actual results: not running Expected results: should run Additional info:
fontmatrix-0.6.99-5.r1073.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/fontmatrix-0.6.99-5.r1073.fc12
Umm... http://koji.fedoraproject.org/koji/buildinfo?buildID=156925 says this fontmatrix was rebuilt against qt-4.6.1-3.fc12, (and the submitted fontmatrix-0.6.99-5.r1073.fc12 also uses this qt) which is in fact still in dist-f12-updates-testing (not in dist-f12-updates), but in F-12 buildroot because this qt has dist-f12-override tag. ref: https://admin.fedoraproject.org/updates/F12/FEDORA-2010-1895 (still F-12 updates-testing) This new qt provides _ZN9QListData7detach3Ev symbol. On the other hand current dist-f12-updates qt is still qt-4.5.3-9.fc12 and this qt does not provide _ZN9QListData7detach3Ev symbol. So perhaps enabling testing repo and updating qt related packages should fix this, however I think this kind of things should be handled somehow by release engineering.
The problem here is folks not reading our devel-announce e-mails! Each time there's the odd package getting built against the new Qt and pushed directly, or at least too early, to stable. :-/ Packagers of Qt packages are responsible for making sure they don't push their package to stable before the Qt they built against goes stable.
As for the workaround to this bug: downgrade to fontmatrix-0.6.99-3.r1073.fc12 from the F12 release.
fontmatrix-0.6.99-4.r1073.fc12.1 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/fontmatrix-0.6.99-4.r1073.fc12.1
fontmatrix-0.6.99-4.r1073.fc12.1 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.