[Gutsy Tribe 5] Konversation: Server sent error 65 and Server sent error 3

Bug #139351 reported by Dax Solomon Umaming
2
Affects Status Importance Assigned to Milestone
kdepim (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: konversation

I haven't launched Konversation for a two weeks now. But when I do, I got 2 errors:
Server sent error 65: Access to restricted port in POST denied
Server sent error 3: Could not start process Unable to create io-slave: klauncher said: Unknown protocol"..
Konversation reports an error in 2 windows. After closing down the 4 error windows, Konversation quits.
I've purged and reinstalled Konversation twice with the same results.
I'm reporting the 2 errors as 1 bug report because they are related.

Revision history for this message
Dax Solomon Umaming (knightlust) wrote :

attaching screenshot

Revision history for this message
Dax Solomon Umaming (knightlust) wrote :

attaching backtrace

Revision history for this message
Dax Solomon Umaming (knightlust) wrote :

Too bad I don't know what's exactly causing the crash:

[Thread debugging using libthread_db enabled]
[New Thread -1233647936 (LWP 1123)]
0xffffe410 in ?? ()
#0 0xffffe410 in ?? ()
#1 0xbfe34518 in ?? ()
#2 0xb7a40ff4 in ?? () from /lib/tls/i686/cmov/libc.so.6
#3 0xbfe34504 in ?? ()
#4 0xb798de70 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#5 0xb798dca7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#6 0xb749bad9 in KCrash::startDrKonqi () from /usr/lib/libkdecore.so.4
#7 0xb74b24de in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4
#8 0xffffe420 in ?? ()
#9 0x0000000b in ?? ()
#10 0x00000033 in ?? ()
#11 0xc0100000 in ?? ()
#12 0x0000007b in ?? ()
#13 0xbfe3007b in ?? ()
#14 0x00000000 in ?? ()

Revision history for this message
Dax Solomon Umaming (knightlust) wrote :

dax@knightlust:~$ konversation
X Error: BadDevice, invalid or uninitialized input device 171
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 171
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
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...

Revision history for this message
Dax Solomon Umaming (knightlust) wrote :

I Googled out this error and got to this page: http://docs.kde.org/stable/en/kdebase/konqueror/portnumbers.html
So I added
OverridenPorts=6667 in my ~/.kde/share/config/kio_httprc and restarted konversation.. im still getting this error.

I've tried adding all the ports listed on the said page but it still won't work.

I've also deleted everything that has to do with konversation on ~/.kde in the hopes that it'll start fresh, still no luck

Revision history for this message
Dax Solomon Umaming (knightlust) wrote :

This bug is now fixed. I used eGroupware before and forgot to remove the address book resource.
After removing the said resource, Konversation runs fine.
Changing Status to Won't Fix

Changed in konversation:
status: New → Won't Fix
affects: konversation (Ubuntu) → kdepim (Ubuntu)
Changed in kdepim (Ubuntu):
status: Won't Fix → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.