By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2726

Summary:	Kopete: Slow and high CPU usage when signed in
Product:	TDE	Reporter:	Kristopher <gamrat.kristopher>
Component:	tdenetwork	Assignee:	Timothy Pearson <kb9vqf>
Status:	NEEDINFO ---
Severity:	normal	CC:	bugwatch, michele.calgaro
Priority:	P5
Version:	R14.0.x [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Kristopher 2016-11-11 20:05:27 CST

This is on CentOS 6. Unfortunately, I currently don't have a Debian system to test on.

When logging in to Jabber or attempting to sign in to AIM from Kopete, Kopete will start using a very high percentage of my (very old) CPU. This slows my system to a craw, and Kopete itself will be just shy of responsive, taking anywhere from a few seconds to a few minutes to respond to typing and mouse clicks. This forces me to have to kill Kopete just to return my system to normal.

I don't have an account on any other messaging service that I could test this with.

Comment 1 Michele Calgaro 2018-08-04 09:20:20 CDT

I can't reproduce this and I use Kopete and Jabber almost daily.
Is this bug still valid?