Version: 0.60.2 (using 4.1.2 (KDE 4.1.2), Kubuntu packages) Compiler: cc OS: Linux (i686) release 2.6.27-7-generic When receiving a message from a person that I'm not already in a conversation with, a popup notification appears, as it should. However, when the popup is visible, kopete is using 100% CPU, which it really shouldn't be.
Doesn't seem to happen all the time. Possibly happens when: - Kopete is minimized to tray - There are multiple messages in the queue - The popup(s) are left open for some time
I can't reproduce this with ICQ. Does the popup disappears after while? Which protocol do you use? How much is some time? :)
- The popups don't disappear, they stay until I click either View or Ignore. - Using Jabber, logged into GTalk. - Good question. I've only noticed it when I've left Kopete running overnight, and come back to messages in the morning. Also, I'm fairly certain Kopete has to be minimized to the tray. I noticed the other day that it didn't happen when the Kopete window was only minimized to the task bar. I'll leave it running overnight, and see if it still occurs.
Yep, still occurs if I leave it running overnight. They were spam messages received on MSN, people not on my contact list. If you're unable to reproduce it, is there any information I can send through to help track it down?
an approximate number of messages that need to be recieved in order to trigger the 100% cpu would be good information to have. Also, if you're available for testing, it would be interesting to see if this is a time bound thing (i.e. you have to be away for X number of minutes/hours in order to see the bug)
Hi, I have the exact same bug, using Jabber protocol only. I didn't see a contact in my contact list (surprisingly, because he was connected), but saw him on a jabber chatroom. Then, I've tried to send him a message by right-clicking on him in the chatroom and (kopete + dbus-daemon) started using 100% of my CPU (50% each approximately). It appeared right away (no need to be away for a number of minutes) and a single message was enough. Also something useful : my .xsession-errors is cluttered with messages like this (I have thousands of those !) : kopete(630)/kopete (jabber) JabberContact::manager: called, canCreate: 0
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!
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? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version? If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
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!
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!