Xchat doesn't timestamp event and backlog properly

Bug #205075 reported by Jo-Erlend Schinstad on 2008-03-22
Affects Status Importance Assigned to Milestone
xchat (Ubuntu)

Bug Description

Binary package hint: xchat

Ok, this might not seem like the biggest issue, but it's really annoying for me. I run xchat in an nx session so I can suspend it and move it around, much the same way that the irssi people do with screen. However, today I reconnected to my nx session and everything seemed fine; except that all messages I'd received in all channels within the twelve hours I was disconnected was timestamped with the time when I reconnected to the nx server. That is, it looked like I received several thousand lines at the moment I connected. Someone in #xchat @ freenode suggested it could have something to do with xchat using the timestamp for the time it displays the mesage, instead of the time when the message is received. have no idea whether this is true or not. I have noticed several times when running on the local console with a normal X.org setup, that the timestamp doesn't always match the system clock. Therefore, my guess (but it is only a guess) that X uses its own clock that xchat uses instead of accessing the system time directly.

I am running Hardy, but I'd be very surprised if this didn't also affect earlier versions. I also think this would affect xchat-gnome, though I have no way of knowing for sure.

Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. I reported this issue upstream, you can track the status and make comments here: http://sourceforge.net/support/tracker.php?aid=2118512

Changed in xchat:
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.