Bug 141524 - new gateway plugin from Wildfire Jabber server results in dead user entries in kopete
Summary: new gateway plugin from Wildfire Jabber server results in dead user entries i...
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: Jabber Plugin (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-11 11:51 UTC by Klaus Weidenbach
Modified: 2023-01-19 05:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Klaus Weidenbach 2007-02-11 11:51:22 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Slackware Packages
OS:                Linux

I am using the Wildfire (http://www.igniterealtime.org/) Jabber Server with the new included Plugin Gateway to connect to M$N, ICQ, Yahoo, etc.

The problem that occurs is that when I logout from jabber and then login again, in kopete's user list there keep some dead entries with no account assigned to them anymore. Also all meta contact settings get lost for the users that come from other IM networks trough the gateway plugin.

Since version 1.0.0beta6 of this gateway plugin I guess they have changed the behavior how such other IM contacts are treated in the jabber roster. In the changelog I found this entry: "Upon unregistering from transport, roster items are now removed from roster". I think this is causing problems in kopete. I was working with the py* transports before and there existed not such problems.
Comment 1 Klaus Weidenbach 2007-04-30 23:08:41 UTC
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?
Comment 2 Dominik Tritscher 2008-07-22 11:30:22 UTC
I can't reproduce that bug with kopete from KDE 4.1 RC1.
Comment 3 Klaus Weidenbach 2008-07-23 23:40:44 UTC
I have tested it yesterday quick with the "KDE Four Live" CD (KDE4.1 RC1). It seems to work on the first short view. But this KDE version was far from ready for daily use. Is there any chance this can be backported to KDE3?
Comment 4 Dominik Tritscher 2008-08-18 22:52:29 UTC
Closed that bug, as it seems to work with current stable release 4.1
Comment 5 Klaus Weidenbach 2011-12-26 08:31:31 UTC
This bug reappeared some time back. I use KDE SC 4.7.4 and after every login the entries that come from XMPP gateways have orphan entries with no contacts assigned anymore again and new entries are created.
Comment 6 Andrew Crouthamel 2018-11-06 15:19:21 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-11-18 03:23:00 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Justin Zobel 2022-12-20 07:49:51 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 9 Bug Janitor Service 2023-01-04 05:24:05 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2023-01-19 05:14:33 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!