kopete auto connect don't work in gutsy

Yes i have the same problem with gusty updated.
And i thought after feisty, kopete had Network presence detection (with network-manager-kde), isn't it? because now when i start kopete it starts before network-manager-kde i have 2 or 3 notice about in can't conect to my msn account. Maybe it is only in msn accounts...

I also have this issue. When I first start my computer and open kopete, it logs in without difficulty. If, however, I exit kopete and then restart it, it fails to connect to the msn servers. This is true no matter how many times I restart the program until I restart my entire machine. Running through the console, I get the following lines:

kopete (msn): WARNING: [QString MSNNotifySocket::statusToString(const Kopete::OnlineStatus&) const] Unknown status 10!
kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (remote host closed connection)

Note that I am able to connect via Pidgin when kopete will not connect. This problem occurs exactly as I have described EVERY time I test it, so it is certainly not a reoccurring but temporary issue with the msn servers - it is definitely an issue with kopete.

I confirm this bug is still present
+1

I have just modified the connection section for my MSN account, changed it to HTTP method.

Though I ran it from console, I have no other messages than the remote host one.
I just sent a test message to a contact marked as Away, and the following logs were shown in the console...

ection)
KPopupMenu: title() called with non-title id 0.
QObject::connect: No such slot MSNContact::slotWebcamReceive()
QObject::connect: (sender name: 'msnWebcamReceive')
QObject::connect: (receiver name: 'unnamed')
QObject::connect: No such slot MSNContact::slotWebcamSend()
QObject::connect: (sender name: 'msnWebcamSend')
QObject::connect: (receiver name: 'unnamed')
QFont::setPointSize: Point size <= 0 (-1)
QObject::connect: No such signal MSNChatSession::typing(bool)
QObject::connect: (sender name: 'editPart')
QObject::connect: (receiver name: 'unnamed')
libkopete: WARNING: Failed to cast view to QObject *

apart from that, I remained connected, though noone to talk to in order to check this . . .
:)

correction.... when i start chat I get:
 :
  The following message has not been sent correctly  (Connection closed): in kopete
and in the console . . .

kopete: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file jabberchatui.rc
QFont::setPointSize: Point size <= 0 (-1)
QFont::setPointSize: Point size <= 0 (-1)
QObject::connect: No such signal JabberChatSession::typing(bool)
QObject::connect: (sender name: 'editPart')
QObject::connect: (receiver name: 'unnamed')
libkopete: WARNING: Failed to cast view to QObject *
kopete: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file jabberchatui.rc
QFont::setPointSize: Point size <= 0 (-1)
QFont::setPointSize: Point size <= 0 (-1)
QObject::connect: No such signal JabberChatSession::typing(bool)
QObject::connect: (sender name: 'editPart')
QObject::connect: (receiver name: 'unnamed')
libkopete: WARNING: Failed to cast view to QObject *
QFont::setPointSize: Point size <= 0 (-1)
QFont::setPointSize: Point size <= 0 (-1)

i looked how pidgin connects, it overrides the default server settings and specifies the host also used in kopete...

So i ticked the 'override' setting and managed to force a connection. When I send a message I dont get the error saying message not sent.

Thank you for reporting this bug. Due to your comments i mark this bug as confirmed. Can you please try the newer Version of ubuntu /kopete to see if the bug is still there.

ok ill try and let you know.

2008/5/14 mcas <email address hidden>:

> Thank you for reporting this bug. Due to your comments i mark this bug
> as confirmed. Can you please try the newer Version of ubuntu /kopete to
> see if the bug is still there.
>
> ** Changed in: kopete (Ubuntu)
> Status: New => Confirmed
>
> --
> kopete auto connect don't work in gutsy
> https://bugs.launchpad.net/bugs/141005
> You received this bug notification because you are a direct subscriber
> of the bug.
>

still present on 18/05/2007 with all latest updates applied in hardy

I have the same problem.

kopete (msn): WARNING: [QString MSNNotifySocket::statusToString(const Kopete::OnlineStatus&) const] Unknown status 10!
kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (원격 호스트의 접속이 끊겼습니다.)

There is another bug report on the problem: https://bugs.launchpad.net/ubuntu/+source/kopete/+bug/232047

Is this bug still present in Intrepid?

not present any more :)

thanks :)

2009/1/7 Jonathan Thomas <email address hidden>

> Is this bug still present in Intrepid?
>
> ** Changed in: kdenetwork (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> kopete auto connect don't work in gutsy
> https://bugs.launchpad.net/bugs/141005
> You received this bug notification because you are a direct subscriber
> of the bug.
>

You're welcome. Thanks for following up. :)