Bug 139835

Summary:	The times of inbound and outbound Gadu-Gadu messages are out of synchronisation
Product:	[Unmaintained] kopete	Reporter:	Michał ,,KNT'' Gorycki <knt>
Component:	Gadu-Gadu Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	kmm, kontakt, neuro
Priority:	NOR
Version First Reported In:	0.12.3
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Michał ,,KNT'' Gorycki 2007-01-09 23:00:16 UTC

Version:           0.12.3 (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages

A log (the messages are in chronogical order, note the timestamps, the "< * >" are inbound, the messages are just some polish chit-chatter ;):

22:43:00 < * >  ha! wiedziałem że jak odmóżdżanie to Ty:) 
22:41:00 < KNT >  jej bohu! 
22:41:00 < KNT >  skąd!? 
22:41:00 < KNT >  jak?! 
22:41:00 < KNT >  hyyyyyyy 
22:41:00 < KNT >  :) 
22:44:00 < * >  zKrakowa!! 
22:41:00 < KNT >  AJ-WAJ! 
22:41:00 < KNT >  >panika< 
22:42:29 < KNT >  co tam?

My messages times are synced with my system clock.
This happens despite of the contact being offline or online (I was online). Furthermore the messages are then saved in the archive with incorrect times and thus messed up in time.

Comment 1 Grzegorz Jaskiewicz 2007-01-10 13:11:15 UTC

incoming messages are using timestamp that came from peer client. Thus showing time at which the message was sent to one. This is correct behaviour, and the same happends in the original client.
I won't fix it, unless you propose something that makes sense.
As far as I can see, your problem is not the timing of messages you see in chat window, but timestamp used in history.

Comment 2 Jakub Grandys 2007-07-12 23:43:56 UTC

Here it is me quick suggestion:
when message is being saved in history it checks if timestamp is from future if yes, it uses current time as incoming message timestamp, if not nothing changes. As a result if we receive message when offline it is saved with incoming time.
Unfortunately it doesn't help when sender has slower clock, in my opinion only solution is to always set current time in history.
Here is my code:

kopete/plugins/history/historylogger.cpp
Line 272 (in kopete 0.12.5 kde 3.5.7), part of HistoryLogger::appendMessage

msgElem.setAttribute( "time", msg.timestamp().toString("d h:m:s") ;

change to:

        if(QDateTime::currentDateTime()<msg.timestamp())
         {
                msgElem.setAttribute( "time", QDateTime::currentDateTime().toString("d h:m:s");
         } else {
                msgElem.setAttribute( "time", msg.timestamp().toString("d h:m:s") ;
            }
Sorry for my English and code I'm new here and in C++ :)

Comment 3 Michał ,,KNT'' Gorycki 2007-07-13 12:21:23 UTC

Or mabye an idea taken from Kadu: show two time stamps: one from me and one from the other participant. But the time in the archives should be im my time (so all the messages would be in sync).

Comment 4 Pino Toscano 2009-05-13 11:08:42 UTC

*** Bug 172405 has been marked as a duplicate of this bug. ***

Comment 5 km 2009-05-20 12:02:20 UTC

Subscribing. Messages should be logged in history with current local time. The problem also applies to chat window, but it is not that important, as the messages are in a proper order anyway.

Comment 6 Justin Zobel 2021-03-09 22:40:54 UTC

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.

Comment 7 Christoph Cullmann 2024-09-18 18:27:50 UTC

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.