Version: 0.10.3 (using KDE KDE 3.4.2) Installed from: SuSE RPMs I have noticed that if I log-in with kopete as 'user@novell.com' I cannot initiate conversations. People and send me messages and I can respond, but if they have not already sent me a message my messages do not go through. If I log-in as just 'user' then everything works fine. Using 'user@novell.com' should either work, or should not be able to log-in at all.
I have had a similar problem with the groupwise plugin. I can not initiate conversations, but if someone messages me then things work fine. When attempting to start a chat session I receive the following error: An error occurred when trying to start a chat: 53560 I am using: Kopete 0.10.3 KDE 3.4.2 Debian
I can login with 'user@domain' but cannot start a chat (same error as Tim - 53560). I'm using: Kopete 0.11 KDE 3.5.0 level "a" SuSE 9.3
I too am having the same problem with a one additional detail. If I log in as .username.context.blah I can not initiate a chat with another user (they are all using the novell client or gaim). It doesn't necessarily matter if they initiate the message with me as long as they have a chat window opened ready to chat with me. If they have a chat window open for me I am capable of chatting with no problem. All works fine if I just log in as 'username' (Just found that out from visiting this bug. ;) Kopete 0.11 KDE 3.5.0 Gentoo ~x86 Thanks!
Using kopete 0.12.4 (KDE 3.5.6) on Kubuntu 6.10 (Edgy), I can't start a conversation when signed in with either my fully qualified user name or my short name. The following message is displayed: "An error occurred when trying to start a chat: 53560" The gaim 2.0.0beta3.1 client works fine to communicate with the same server.
Checking it out.
*** Bug 132457 has been marked as a duplicate of this bug. ***
I have the same problem "An error occurred when trying to start a chat: 53560" Kopete 0.12.7 KDE 3.5.9 Kubuntu Hardy 8.04 This has been broken for as long as I can remember. Would love to have it fixed, it is the one thing preventing me from using Kopete. Thanks!
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
Thankfully I haven't had to use Groupwise in a significant amount of years. Unfortunately I have not used Kopete in years either so I don't know if this bug still exists. I strongly doubt that it does so I am going to close this ticket. Thanks for all the hard work!