You are not logged in.

Kopete .8rc1 doesn't have any protocols

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.

Twiggy794

Trainee

  • "Twiggy794" started this thread

Posts: 101

  • Send private message

1

Thursday, January 22nd 2004, 12:35am

Kopete .8rc1 doesn't have any protocols

I reinstalled KDE 3.2rc1, but when I loaded up Kopete it had no protocols in it for me to connect to. Am I missing something vital here?

Twiggy794

Trainee

  • "Twiggy794" started this thread

Posts: 101

  • Send private message

2

Thursday, January 22nd 2004, 6:11am

Here's the console output:

kdecore (KIconLoader): WARNING: Icon directory /home/scott/.kde/share/icons/Gorilla/ group not valid.
libkopete: WARNING: [KopetePlugin* KopetePluginManager::loadPluginInternal(const QString&)] Unable to find a plugin named 'kopete_chatwindow'!
libkopete: WARNING: [KopetePlugin* KopetePluginManager::loadPluginInternal(const QString&)] Unable to find a plugin named 'kopete_connectionstatus'!
libkopete: WARNING: [KopetePlugin* KopetePluginManager::loadPluginInternal(const QString&)] Unable to find a plugin named 'kopete_aim'!
libkopete: WARNING: [KopetePlugin* KopetePluginManager::loadPluginInternal(const QString&)] Unable to find a plugin named 'kopete_aim'!

I'm using Suse 9 and KDE 3.2rc1. Anybody know what could cause this?

iapetus

Beginner

Posts: 9

  • Send private message

3

Thursday, January 22nd 2004, 8:53am

Have you run kbuildsyscoca yet? IIRC you need to run it as the user you're running kopete as (though you may need to do it as root instead/as well - the docs aren't that clear on that front).

Twiggy794

Trainee

  • "Twiggy794" started this thread

Posts: 101

  • Send private message

4

Thursday, January 22nd 2004, 9:08am

I actually got it all working. I completely removed KDE and reinstalled 3.2rc1 from scratch and it works fine now. I had a few warnings when I installed originally, so I'm assuming one of them caused it.