You are not logged in.

[kopete] annoying popup error messages

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.

Dralan

Beginner

  • "Dralan" started this thread

Posts: 2

  • Send private message

1

Tuesday, April 26th 2005, 11:02pm

[kopete] annoying popup error messages

Hello All,

I keep getting these annoying popup errors reading "An unknown error has occurred and the connection has been closed." This happens seemingly randomly for each and every account I am logged in as, however, I cannot notice any loss in connection. I do not have to log in or out when this happens, but I have to click OK each and every time before I can do anything with kopete. If I leave my computer for 30 mintues, I might have 10 or 15 of these messages, or sometimes more, which is quite annoying.

I ran kopete from the console to see if I could get any useful output, and this is what I have:

Quoted


libkopete: WARNING: [Kopete::Plugin* Kopete::PluginManager::loadPluginInternal(const QString&)] Unable to find a plugin named ''!
QGArray::find: Index 0 out of range
kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17
QGArray::find: Index 0 out of range
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QObject::connect: No such signal TypingNotifyTask::gotInfo(const QString&)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'oscarclient')
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QObject::connect: No such signal TypingNotifyTask::gotInfo(const QString&)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'oscarclient')
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QObject::connect: No such signal TypingNotifyTask::gotInfo(const QString&)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'oscarclient')
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QObject::connect: No such signal TypingNotifyTask::gotInfo(const QString&)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'oscarclient')
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QMetaObject::findSignal:ClientStream: Conflict with Stream::readyRead()
QObject::connect: No such signal TypingNotifyTask::gotInfo(const QString&)
QObject::connect: (sender name: 'unnamed')
QObject::connect: (receiver name: 'oscarclient')


I did get a few of these errors in the span of that output.

This post has been edited 1 times, last edit by "Dralan" (Apr 26th 2005, 11:03pm)

Dralan

Beginner

  • "Dralan" started this thread

Posts: 2

  • Send private message

2

Wednesday, April 27th 2005, 4:59pm

I thought I should also mention that this is a new SuSE 9.3 install which gives me Kopete version "0.10 (Using KDE 3.4.0 Level "b")". Also, my home computers do not suffer from this problem so I am starting to think that there could be a network setup issue that Kopete is not liking.