Sunday, September 23, 2007

Konversation: Error 65 and 3

I haven't used Konversation for a few weeks, and when I did.. Konversation returned this error:
Server sent error 65: Access to restricted port in POST denied.
and
Server sent error 3: Could not start process Unable to create io-slave: klauncher said: Unknown protocol ". .



It's been like this for three weeks and I was forced to rely on IRSSI and IceApe's Chatzilla. My cravings for Konversation grew stronger that I finally ranted about this at #ubuntu-ph. I gave Jucato and Ahmuck this error:

0xffffe410 in ?? ()
#0  0xffffe410 in ?? ()
#1  0xbf909888 in ?? ()
#2  0xb79f1ff4 in ?? () from /lib/tls/i686/cmov/libc.so.6
#3  0xbf909874 in ?? ()
#4  0xb793ee96 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#5  0xb793eca7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#6  0xb744cad9 in KCrash::startDrKonqi () from /usr/lib/libkdecore.so.4
#7  0xb74634de in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4

and this

Failed to open device
konversation: WARNING: Cannot execute call to system.login: empty server URL
QGDict::hashKeyString: Invalid null key
QGDict::hashKeyString: Invalid null key
konversation: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Unknown protocol ''.
konversation:
konversation: ERROR: <qt>Server sent error 3: <b>Could not start process Unable to create io-slave:
klauncher said: Unknown protocol ''.
.</b></qt>
konversation: ERROR: <qt>Server sent error 3: <b>Could not start process Unable to create io-slave:
klauncher said: Unknown protocol ''.
.</b></qt>
konversation: WARNING: Cannot execute call to addressbook.boaddressbook.search: empty server URL
konversation: WARNING: Cannot execute call to addressbook.boaddressbook.categories: empty server URL
konversation: WARNING: Cannot execute call to addressbook.boaddressbook.customfields: empty server URL
dax@knightlust:~$ QGDict::hashKeyString: Invalid null key
konversation: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Unknown protocol ''.
konversation:
QGDict::hashKeyString: Invalid null key
konversation: ERROR: : couldn't create slave : Unable to create io-slave:
klauncher said: Unknown protocol ''.
konversation:
KCrash: Application 'konversation' crashing...

It was Jucato who asked the maintainer of Konversation (Sho) what's happening.

Jucato: That has something to do with the KAddressBook integration, from the looks of it
Jucato: My guess is that he's using eGroupWare or IMAP to store his address book on a server, and something goes wrong in KIMProxy
Jucato: If it's a dialog box, you can be fairly sure it's not Konversation, we don't use them
Jucato: "kresources/egroupware/kabc_resourcexmlrpc.cpp: QString msg = i18n( "Server sent error %1: %2" ).arg( error ).arg( errorMsg );" btw
from kdepim
Jucato: Perhaps he set up eGroupware, but removed eGroupWare again but forgot to remove the resources in Kontact/KAddressBook

So there it is.... the solution to my problem. Sho was right.. I used (past tense) eGroupware and forgot to delete any reference to it from KAddressbook.

I deleted it.. and it worked. Ha! I said my goodbye to Chatzilla (no.. I'm still fond of IRSSI) and went to bed. This all happened last night.

For those curious how to remove the XML-RPC entry in KAddressbook, just go to Settings > Show Extension > Address Books. That's where you delete it.

Blogged with Flock