This forum has been archived. All content is frozen. Please use KDE Discuss instead.

"undefined symbol" --> incorrect Qt?

Tags: None
(comma "," separated)
teun
Karma
0
when i start amarok, it immediately crashes, saying:

amaroK: [Loader] Starting amarokapp..
amaroK: [Loader] Don\'t run gdb, valgrind, etc. against this binary! Use amarokapp.
kbuildsycoca running...
DCOP Cleaning up dead connections.
QObject::connect: Cannot connect Engine::Base::statusText( const QString& ) to (null)::shortMessage( const QString& )
QObject::connect: Cannot connect Engine::Base::infoMessage( const QString& ) to (null)::longMessage( const QString& )
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
amarokapp: symbol lookup error: amarokapp: undefined symbol: _ZN12QProgressBarD2Ev




==> on the amarok FAQ i found this:
http://amarok.kde.org/wiki/index.php/FA ... ed_symbols

if you get this error : \"amarokapp: symbol lookup error: amarokapp: undefined symbol: _ZN11KSystemTray9setPixmapERK7QPixmap\", then check that amarokapp uses the correct libqt (check with : ldd `which amarokapp` | grep qt).
To fix it, you might have to remove any conflicting libqt and/or edit /etc/ld.so.conf so it pick up the correct version first.


==> When i did this i got
# ldd `which amarokapp` | grep qt
libqt-mt.so.3 => /usr/lib/qt-3.3/lib/libqt-mt.so.3 (0x04a74000)

# locate libqt-mt.so.3
/usr/lib/qt-3.3/lib/libqt-mt.so.3
/usr/lib/qt-3.3/lib/libqt-mt.so.3.3.4
/usr/lib/qt-3.3/lib/libqt-mt.so.3.3

# rpm -qi qt
Name : qt Relocations: /usr/lib/qt-3.3
Version : 3.3.4 Vendor: Red Hat, Inc.
Release : 0.fc3.0


==> i don\'t really understand what i should do next. It seems allright, no? amarok wants qt-3.3 and my qt is 3.3.4?
Can anyone help me with what i should do now, or with what i should check next?
teun
Karma
0
OK, I solved it. On the same repository
http://apt.kde-redhat.org/apt/kde-redha ... MS.stable/
i found a slightly newer version of qt : 3.3.4-17 instead of 3.3.4-0...
qt-3.3.4-17.3.fc3.kde.i386.rpm

intalling this solved my problem.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]