You are not logged in.

Kopete .7.4 installation trouble

NoahsMyBro

Beginner

  • "NoahsMyBro" started this thread

Posts: 5

  • Send private message

1

Friday, December 26th 2003, 5:02am

Kopete .7.4 installation trouble

System is running Suse 8.2, with the default 3.1 KDE desktop.

I had Kopete .7.3, supplied by SuSE. Each time I tried to add an account, Kopete crashed (app simply disappeared - no error msg, no lockup).

SO, this evening I first used "rpm -e kopete" to remove .7.3. I then downloaded the tar of Kopete .7.4 from Sourceforge, and tried to install it.

I tar -xvzf'd it in a temporary directory. I then ran ./configure, make, and make install.

It took a short time for me to even find the program file, so maybe I'm just running the wrong executable, but each time I try to launch the program - "/usr/local/kde/bin/kopete", I get many errors, and the window that appears is clearly incomplete, missing menus and menu titles.

The errors include:
[code:1]
kio (KMimeType): WARNING: KServiceType::offers : servicetype Kopete/Plugin not found
kopete: [KopetePlugin* LibraryLoader::loadPlugin(const QString&)] No service implementing the given mimetype and fullfilling the given constraint expression can be found.
kopete: [KopetePlugin* LibraryLoader::loadPlugin(const QString&)] Loading plugin 'aim'failed, KLibLoader reported error:
kopete:
kopete: [void KopeteAccountManager::save()]
kopete: [virtual LibraryLoader::~LibraryLoader()] All plugins removed

[/code:1]
Help?

djtrippin

Trainee

Posts: 142

  • Send private message

2

Friday, December 26th 2003, 7:58pm

Two quick things that might help you out in this case.

1.) When you did the ./configure did you add the proper prefix for kde? You can find the proper prefix by typing 'which konqueror' in the console. The output should be something like '/usr/bin/konqueror' or '/opt/kde3' or 'usr/local/bin/konqueror' in which cases your prefix would be respectively '/usr' or '/optkde3' or '/usr/local'. Once you find your prefix go back to the directory you compiled the source in and type 'make distclean' to remove all compiles and configure scripts. Then run ./configure --prefix=prefix/that/I/found

2.) After doing the make install, did you run kbuildsycoca? kbuildsycoca updates kde's plugin base.

9 out of 10 times there is an install error when compiling from source tarball, its the prefix problem. The other time, its kbuildsycoca.
Simplicity is the staple of the working man.

NoahsMyBro

Beginner

  • "NoahsMyBro" started this thread

Posts: 5

  • Send private message

3

Saturday, December 27th 2003, 2:17am

Thanks!

I'm in WinXP right now, but will try that as soon as I reboot.

NoahsMyBro

Beginner

  • "NoahsMyBro" started this thread

Posts: 5

  • Send private message

4

Saturday, December 27th 2003, 12:25pm

Your first suggestion, to apply the correct prefix (in my case, /opt/kde3), was the solution.

Thanks again, you were a great help, and spelled out what I needed to do with enough detail and clarity that I was able to do exactly what I needed to with no trouble.

-- Steve