By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 579 - Amarok don't start, amarokapp: symbol lookup error
Summary: Amarok don't start, amarokapp: symbol lookup error
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdemultimedia (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: amd64 Debian Squeeze
: P5 enhancement
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-11-04 09:31 CDT by RADICS Áron
Modified: 2012-10-19 15:56 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RADICS Áron 2011-11-04 09:31:36 CDT
Hello,


I upgrade to 3.5.13. I get this message, when I start amarok.

$ amarok
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
amarokapp: symbol lookup error: /opt/trinity/lib/libamarok.so.0: undefined symbol: _ZN12KApplication18openX11RGBADisplayEv

$ amarokapp ; echo RESULT=$?
amarokapp: symbol lookup error: /opt/trinity/lib/libamarok.so.0: undefined symbol: _ZN12KApplication18openX11RGBADisplayEv
RESULT=127


Installed packages:
amarok-trinity: 4:3.5.13-0debian9+r1260411+pr4~squeeze
amarok-common-trinity: 4:3.5.13-0debian9+r1260411+pr4~squeeze
amarok-engine-xine-trinity: 4:3.5.13-0debian9+r1260411+pr4~squeeze
Comment 1 RADICS Áron 2011-11-07 14:57:19 CST
The other TDE updates solved.