Bug 485843 - kde4-config: symbol lookup error: /usr/lib/libQtNetwork.so.4:
kde4-config: symbol lookup error: /usr/lib/libQtNetwork.so.4:
Product: Fedora
Classification: Fedora
Component: kdelibs (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-02-16 18:43 EST by Ray Van Dolson
Modified: 2009-02-17 02:11 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-02-17 02:11:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ray Van Dolson 2009-02-16 18:43:24 EST
Description of problem:
Whenever I open a shell or terminal (either from a text tty or within GNOME, XFCE, etc), the following error appears:

  kde4-config: symbol lookup error: /usr/lib/libQtNetwork.so.4: undefined symbol: _ZN14QObjectPrivate15checkWindowRoleEv

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start shell
Actual results:
kde4-config complaint shown.

Expected results:
No error output.

Additional info:
This seems to have begun with the latest kdelibs updated on Feb 14th.  I have tested on two Fedora 10 machines and both exhibit this issue.
Comment 1 Kevin Kofler 2009-02-17 00:53:40 EST
Please check the output of:
ldd `which kde4-config`
for what Qt libraries it is using. The command:
ldd `which kde4-config` | grep Qt
should return:
        libQtCore.so.4 => /usr/lib/libQtCore.so.4 (0x07cfa000)
        libQtDBus.so.4 => /usr/lib/libQtDBus.so.4 (0x00634000)
        libQtNetwork.so.4 => /usr/lib/libQtNetwork.so.4 (0x0053a000)
        libQtXml.so.4 => /usr/lib/libQtXml.so.4 (0x004ac000)
(the 0x... addresses may vary, but the path must be /usr/lib!)

If you have any private copies of Qt shipped with some broken (usually proprietary) software there, delete those private copies and complain to the supplier of that software.
Comment 2 Ray Van Dolson 2009-02-17 02:11:20 EST
Good call.  Should have checked this first!  Nessus is to blame here.  Sorry for the noise.

Note You need to log in before you can comment on or make changes to this bug.