Version: (using KDE Devel) Installed from: Compiled sources If you click the Back arrow (<-) in the chat window to browse back in history, then later click the next arrow (->) to return to the current point in time, any Internal messages received along the way are lost. This plugin seems to overwrite the chat window with only it's internal data as you move back and forth with these buttons. I don't think that should be so with the "now" page. When you are looking at the "now" page, and you hit "back", the messages that currently exist in the chat window should be stored in a buffer. Also, as you receive new messages, and are on a page before "now", they are appended to that buffer. Once you return to the "now" page, you can flush and clear the buffer into the current chat view, thus restoring the exact window contents. Then you don't need to worry about special cases the history plugin doesn't log, like internal messages (although - this could be another bug. The internal messages are sometimes very useful, there should be an option to log them). This solution would also fix bug #76733, which I don't think should have been closed.
I can confirm that this still can happen on kopete from KDE 4.0.99. To reproduce: 1) start a chat with someone and have a conversation with more than 7 sentences (which is the default number of sentences to show from history in the new chat windows) 2) close the chat and reopen it, you should only see the last 7 sentences now. 3) click back, you now see the previous sentences 4) have a talk with more than 7 sentences (but without clicking next after back!) 5) now, click next and the messages are gone. However, if you close and reopen the chat window, all the messages are there and in the right order.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
Dear user, unfortunately Kopete is no longer maintained. Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.