Bug 172405

Version:           0.60.2 (using 4.1.2 (KDE 4.1.2), Arch Linux)
Compiler:          gcc
OS:                Linux (i686) release 2.6.26-ARCH

The gadu-gadu protocol supports two timestamps for a message: the 'sent timestamp' (according to sender's clock or the gadu-gadu internal time, i don't know) and the 'arrival timestamp' (according to the receiver's clock).

The problem is, that kopete displays the sent timestamp for incomming messages in gadu-gadu chat windows. The order of messages on screen is correct and reflects the order of conversation, but when the difference between clock times of both parties is substantial (>5-10s) it is usual to see something like this:
remote_user: 12:00:50
local_user: 12:00:40
remote_user: 12:00:54
local_user: 12:00:47
As I said, it doesn't hurt that much in the chat window. When it really hurts is in the chat history, where messages are sorted according to times. However, since the times are wrong, the order of conversation is disturbed and it's really hard to follow it.

A simple fix for the issue would be to set a timestamp for the received message upon it's arrival.

However, one must be cautious and double check if this doesn't spoil the timestamps of messages received from the waiting queue when one logs in.