Bug 156625

Summary: Kopete's history plugin loads entire history into chat window
Product: [Applications] kopete Reporter: sarah <sarah>
Component: History PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: FreeBSD Ports   
OS: FreeBSD   
Latest Commit: Version Fixed In:

Description sarah 2008-01-25 07:03:49 UTC 
Version:           0.12.7 (using KDE 3.5.7)
Installed from:    FreeBSD Ports
OS:                FreeBSD

Kopete's history plug-in loads entire history into chat window even when 'show chat history in new chat' is disabled. Actually it also happens when the 'show chat history in new chat' is enabled and set to 7 messages.

What happens is that during the course of sending and receiving messages, the entire history from the logs, not just today's but, i suspect, everything from the beginning of the log file for the month is loaded in. And while it's outputting the logs to the window, you are unable to type anything. Sometimes, it stops printing the history to screen after about 10+ (haven't found a pattern here yet) lines, in which case, you are able to start typing again, but the moment you start typing or just sent a message, the logs start printing out to the chat window again.

Also, it happens regardless of whatever chat style theme is used, or whether contact fonts are overridden -- was trying to eliminate possible causes. And this only started happening to me when i shifted to PC-BSD 1.4.1.2 (using FreeBSD 6.3).

Thanks for any help in advance!

Loaded Plug-ins:
==============
History - with the 'show chat history in new chat' dsabled
Now Listening

How to Reproduce:
==============
1 - open kopete and start a new chat with a contact (double click on contact's name)
1a, if 'show chat history' is disabled, you see a blank new chat window. no history is shown.
1b, if 'show chat history' is enabled, you see the x number of messages from the history file in the new chat window.

2 - send a message (or two) 
3 - receive a message (or two)

4 - the entire message history is loaded in. (all at once or in batches)


Expected Behavior:
==============
You should only be able to see the x number of messages you specified in the plugin's options or none at all if you disabled that option.
Comment 1 sarah 2008-01-25 09:17:55 UTC 
i think i've found a pattern. still looking for a way to fix it though. i noticed that while typing in an open chat window whenever i press the backspace button (on the keyboard) that's when it prints out the chat log into the chat window. (which is probably why i was thinking that it waits for me to send/receive a few messages. i didn't notice earlier that it was the backspace triggering it.

is there anyway to find out why? or any conf files i can tweak? looking over kopete's shortcuts, i dont have anything assigned to the backspace, so im not sure where else to look.

hope this helps. thanks again!
Comment 2 Constantin Berzan 2008-07-20 11:19:32 UTC 
I can confirm that the Backspace key triggers this behaviour.
Currently I have to delete all logs (history) every week or so, or else I have to wait 2-3 minutes each time I press Backspace after I start a chat.
Comment 3 Andrew Crouthamel 2018-11-02 04:25:04 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 4 Andrew Crouthamel 2018-11-16 02:46:01 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?

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2022-12-08 00:00:36 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 6 Bug Janitor Service 2022-12-23 05:21:50 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 7 Bug Janitor Service 2023-01-07 05:24:31 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!