kaffeine 0.7 errors

Zurvan · 08-16-2005, 09:11 PM

Hi, I recently update kaffeine to version 0.7 via yum. Now when ever I try to open an avi or any other video file, I get the following error;

Code:

kaffeine: symbol lookup error: kaffeine: undefined symbol: _ZN11KMainWindow7setIconERK7QPixmap

I have tried removing kaffeine and then installing kaffeine to see if it was just an oddball case. That did not fix the problem. I am rather at a loss as to what is causing this. I tried a google search on the error, to see if anyone else had the same issue, and came up dry. Does anyone have any idea as to what might be causing this?

-- Zurvan

bigrigdriver · 08-16-2005, 11:33 PM

Those *undefined symbol* errors usually mean that you are missing some header files which are usually contained in devel packages.

Having said that, check your system for kaffeine-devel, kaffeine-lib, or xine-devel and xine-lib (kaffeine is basically built on xine).

If they are not installed, uninstall kaffeine, install the necessary -devel or -lib packages, then try installing kaffeine again.

I'm not certain that will work. It's the best I can come up with. Hope it helps.

Zurvan · 08-17-2005, 06:29 AM

Thank you for the tips.

I tried what you suggested, and installed via yum xine-lib-devel-1.1.0-0.lvn.1.3, making sure that I had uninstalled kaffeine before installing the xine libs. Once the libs where installed, I then installed via yum kaffeine.x86_64 0:0.7-0.lvn.1.3, and then attempted to run kaffeine again. The result at the command line was this;

Code:

kaffeine
Link points to "/tmp/ksocket-root"
Link points to "/tmp/kde-root"
kbuildsycoca running...
Reusing existing ksycoca
KWrited - Listening on Device /dev/pts/2
kaffeine: symbol lookup error: kaffeine: undefined symbol: _ZN11KMainWindow7setIconERK7QPixmap
DCOP aborting (delayed) call from 'anonymous-5492' to 'kaffeine'
Mutex destroy failure: Device or resource busy
ICE default IO error handler doing an exit(), pid = 5503, errno = 2

From this it seems that I still have the errors and that something is not right with the package and with how my system is configured. Any ideas as to where I have gone wrong or does anyone know what misconfiguration might be causing this?

-- Zurvan