Bug 66249

I was about to report the same bug when I found this existing report.  I have always been annoyed with MSN and the like that would only allow one client logged in at a time.  I think that the way jabber handles multiple logins to the same account using different resource names is very useful and would like to see it handled well in kopete.

When I am logged in with kopete and then login from my WinXP machine with Exodus it shows me a category called "My resources" with kopete listed as a resource.  However, the exodus resource does not appear in kopete.  I am able to send a message to kopete from exodus but then if I try to reply from kopete the message is sent to the kopete client.  It never makes it to the exodus client.

I think this is a useful feature in jabber that should be handled properly in the Kopete Jabber plugin.  Feel free to contact me with questions.  Keep up the great work.

*** This bug has been confirmed by popular vote. ***

I agree fully, and add to that we need a way to make kopete understand that the contact I set as "personal contact data" in my addressbook should contain the userpicture of myself :)

Em Segunda, 28 de Março de 2005 12:28, o Jonas Lihnell escreveu:
> I agree fully, and add to that we need a way to make kopete understand that
> the contact I set as "personal contact data" in my addressbook should
> contain the userpicture of myself :)



this should not use the picture from a global myself metacontact in 
addressbook.

what if i want to have a diferent pic for every account ?!?

the pic should come from the account settings.

if jabber ever supports avatars , the pic should come from there

in msn , the pic should come from the one set in the account properties. that 
will make it work , with ppl that have 2 msn accounts , with diferent pics on 
each one

then I have a better solution, for every account you have you should be able to set "has addressbook entry" and associate it with a contact.

that way themes such as mine (Clean) could be more consistent.

Also, just as a side-note, we really need more and better documentation of the available variables to use in our styles, userPhoto refers not to the msn photo exported by the contact if the metacontact is associated with an addressbook entry.

Either way we have no loss in being able to use _self contact_ (for all protocols, all instances) as the last resource for getting information.

I'd like this too.
a while ago, I was logged into psi at work while my bf was using my home computer. I was able to send messages to my own account at home to chat with him :) but if he had closed the chatwindow, he would not have had any way of contacting me until I sent him another message. after that I spent a while sending myself reminders via my jabber account. it really would be useful to have a self-contact thingy in kopete (especially since I might be able to go back to gentoo at work, and then I won't be using psi any more).

We now nearly have KDE 4.2 and still I can find no self contact in Kopete...

Still no change with 4.3…

Kopete currently (0.80.2) actually misbehaves completely when logging in a second client to the same account. Instead of just ignoring the second resource, it will pop up an error message:

"Connection problem with Jabber server <servername>
There was an error in the protocol stream: There was a conflict in the information received.
Disconnected."

and disconnect from the server.

This issue has passed from being an inconvenience to being an outright bug. Maybe a change of severity is in order.

using 4.6.2 - kopete still does not have a self contact. I don't get disconnected from the server either though.

Dear user, unfortunately Kopete is no longer maintained.

Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.