You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Saturday, November 27th 2004, 4:13pm

can't start koffice/kword

Installed koffice and kword 1.3.5. The installation went well, but when I try to start kword I get the following error:

./kword: relocation error: /opt/kde3/lib/libkofficecore.so.2: undefined symbol:_ZN11KMainWindow7setIconERK7QPixmap

I tried it with diffrent versions of koffice, but it didn't help. I use SuSE 9.0 with the KDE 3.3.1.

Has anybody an idea... Thanx for your help!

Chris

2

Saturday, November 27th 2004, 4:57pm

Re: can't start koffice/kword

Quoted

Original von chris

Installed koffice and kword 1.3.5. The installation went well, but when I try to start kword I get the following error:

./kword: relocation error: /opt/kde3/lib/libkofficecore.so.2: undefined symbol:_ZN11KMainWindow7setIconERK7QPixmap

I tried it with diffrent versions of koffice, but it didn't help. I use SuSE 9.0 with the KDE 3.3.1.

Has anybody an idea... Thanx for your help!

Chris
This kind of error can be caused by a version conflict. Either a wrong version of a library is installed instead of the correct one, or more than one is installed at the same time and the wrong one is picked up... Did you compile any parts of KDE from source and installed it in parallel to another one?

3

Saturday, November 27th 2004, 11:33pm

I had an older version of the KDE and updated it with yast from an ftp server (rpms). So there are still some old packages from the old version?

So if I have this conflict, what can I do?

The libaries installed are (maybe it helps):

-rwxr-xr-x 1 root root 1640 2004-11-11 07:12 libkofficecore.la
lrwxrwxrwx 1 root root 23 2004-11-27 16:49 libkofficecore.so -> libkofficecore.so.2.0.0
lrwxrwxrwx 1 root root 23 2004-11-27 16:49 libkofficecore.so.2-> libkofficecore.so.2.0.0
-rwxr-xr-x 1 root root 814154 2004-11-11 07:12 libkofficecore.so.2.0.0
-rwxr-xr-x 1 root root 1710 2004-11-11 07:13 libkofficeui.la
lrwxrwxrwx 1 root root 21 2004-11-27 16:49 libkofficeui.so -> libkofficeui.so.2.0.0
lrwxrwxrwx 1 root root 21 2004-11-27 16:49 libkofficeui.so.2 -> libkofficeui.so.2.0.0
-rwxr-xr-x 1 root root 852703 2004-11-11 07:13 libkofficeui.so.2.0.0


Thank you for your fast reply!

4

Saturday, November 27th 2004, 11:57pm

Quoted

Original von chris

I had an older version of the KDE and updated it with yast from an ftp server. So there are still some old packages from the old version?

So if I have this conflict, what can I do???
Unfortunately I'm no expert in these matters. But I think it could just as well be a version incompatibility.

Normally yast should have taken care of the dependencies and should have ensured that you have the proper versions.

Some questions:
- Did you install any rpms with the --nodeps option?
- Did you update KOffice and the rest of KDE at the same time?
- Do you have the up-to-date versions of all packages, especially kdelibs and all of KOffice? If not then you could try to update to the most current version. SuSE keeps releasing new packages between KDE releases that contain minor changes, for example from kdelibs3-doc-3.3.1-5.i586.rpm to kdelibs3-doc-3.3.1-13.i586.rpm

I think ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.0 is the location to check for updates. You can also enter the following URL into yast: ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.0/yast-source (I cannot check this, though, as I don't have a SuSE here.)

5

Sunday, November 28th 2004, 12:44pm

its working

Hi,

I updated the kdelibs with yast and everything works fine now. So thanks for your help...

Chris :-)

6

Sunday, November 28th 2004, 1:40pm

Re: its working

Quoted

Original von chris

Hi,

I updated the kdelibs with yast and everything works fine now. So thanks for your help...

Chris :-)
Good to hear :)