[ordinarily I wouldn't bother you guys with something like this, and I'd just send it upstream (because it looks like an upstream problem), but I know the Gaim developers can be ... less than helpful when it comes to Gentoo users. :p]
Sometimes gaim will randomly turn off the "Interface -> Message Text -> Show timestamp on messages" preference. I can't find any apparent cause for this, nor can I find any specific situation which triggers it (or indeed, any pattern to it at all). It seems that every once in a while, timestamps will just be arbitrarily turned off.
It seems to happen once every few days (regardless of whether or not gaim gets restarted in the interim), and it does it completely randomly ... it'll do it at the start of conversations, in the middle of conversations, at the end, if I'm away, if I'm not away, ...
I am using gaim 0.78. For plugins, I am using "Auto Reconnect", "Gaim-Encryption", "History", "Message Notification", "Remote Control", and "System Tray Icon".
Hmmm I have never seen this. Could be possible though. Have you at least searched the upstream for existing bugs?
I have, and I didn't see anything that looked appropriate. I was going to file something upstream, but I already know about gaim developers' predilection for ignoring Gentoo users ... ;p
It happens pretty infrequently, but just enough to be annoying. :)
They don't ignore Gentoo users. Gentoo users seem to have a knack for filing invalid bugs that are usually of their own making due to over-customization. They also tend to not read FAQs or follow directions on how to get useful backtraces, even after I've explicitly instructed them to do so in the ebuild.
I agree that this would not be anything that we can do, so feel free to take it upstream if you'd like. I'll ask around.
Actually are you sure you aren't just hitting the F2 key accidentally? That will disable the preference.
So say the gaim people ... :)
I don't think I am, but I can't actually recall any specific occurrences in enough detail to be sure. So for now I guess I'll assume I'm hitting F2 and we'll see if it happens again.