Open zmoore opened 9 years ago
Looks like a conversation is having its timestamp changed to null for some reason. I'm not sure why this would happen consistently after a delay.
Can you enable the debug log (hangups -d
) and send me the last log message (~/.cache/hangups/log/hangups.log
) when it crashes?
It turns out this only happens when a group conversation has a video call going. I didn't realize that there was a video call until I looked at hangouts. Sure enough, every time a video call starts or when hangups starts mid-videocall, there's a few seconds of delay and this error message appears.
Thanks, I reproduced this and added a workaround. The workaround causes the sort order for the conversation to be temporarily incorrect, so I'll leave this issue open to address the root problem.
Why am i getting these errors while running the hangups?
Traceback (most recent call last):
File "/usr/local/bin/hangups", line 9, in
Hangups used to work. Now I get this message about 1 minute after starting up. Don't know what causes it, but it's consistent since the last ubuntu update. I don't need to have a particular chat open for it to crash, as it happens even from the conversations list.