[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 141524] new gateway plugin from Wildfire Jabber server results
From: Klaus Weidenbach <Klaus.Weidenbach () gmx ! net>
Date: 2007-04-30 21:08:43
Message-ID: 20070430210843.21158.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=141524
------- Additional Comments From Klaus.Weidenbach gmx net 2007-04-30 23:08 -------
The Gateway Plugin hit stable version 1.0.1 already and my kopete contact list was really messed up with \
dead entries after using 'hide offline contacts' for several weeks. I made following observations now.
When I login to my jabber account the old entries from the gateways disappear and new entries get created \
shortly after that. They have lost the metacontact information or if the contact was not assigned with \
any metacontacts a dead entry remains and a new one is created. If I logout and directly login again, \
everything works fine. No contacts getting removed or dead entries are created in kopete. If I close \
kopete and start it up again and login to jabber everything still keeps fine. If I shut down my computer \
over night and login again in the morning the gateway contacts getting removed and directly new contacts \
getting created like explained before. I don't know how these contacts are recognized, if there exists \
some IDs or just about the user name, but would a short timeout maybe help? I mean it looks like when I \
login into my jabber account kopete thinks the gateway contacts got removed, because the gateways not yet \
logged in themselves to the other IM-networks. When they login they create the new user accounts and then \
they are created again in kopete, too. Maybe a short timeout before removing not existing contacts from \
kopete, so that the gateways can login and create the contacts in the roster list, could fix this bug?
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic