Red Hat Bugzilla – Bug 446274
/usr/lib/libQtSql.so.4: undefined symbol: _ZN14QObjectPrivate15checkWindowRoleEv
Last modified: 2008-05-14 11:30:12 EDT
Description of problem:
Everytime when trying to start vym since the latest qt update today:
vym: symbol lookup error: /usr/lib/libQtSql.so.4: undefined symbol:
Version-Release number of selected component (if applicable):
Was working with former qt package before the update.
Looks like vym linked against a private symbol.
or not, I'm not sure now. any other takes here? (vym or qt maintainers)?
Are you sure you don't have any private copies of Qt 4 in some directory which
are conflicting with the system version? This sounds a lot like (non)
bug 439997 (in that case, the offending copies came from Aladin eToken).
And no, I don't think this is vym's fault, but a reference from one Qt 4 .so to
interesting, just installed vym, cannot reproduce here:
$ rpm -q qt4 vym
vym maintainer here. I have the same versions on fc8, not reproducible. I have
no access to a fc7 system to test there.
Looks like we're gonna go with conclusion in comment #3 (local/private copy of
qt4 interfering), since none of us can reproduce. CLOSING->WORKSFORME
Please reopen if you have more information or evidence to the contrary.
on kde-redhat-users ml, one user found nessus to be the culprit.
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping