Sorry that I don’t have a more detailed bug report here, but I’m using this via bitlbee and things will work fine for… some indeterminate time (seems like it’s between 2-5 days generally?) before purple-hangouts will just stop receiving messages. This has been a less frequent problem for a long while (I think it was only once a week or less before), but it used to be I could restart bitlbee and when I reauth’d the “unread” messages that left notifications on my phone would come in, but that stopped happening… I think since bitlbee forced me to start running in forkdaemon mode?
I’m not seeing any error messages in the control channel that tell me anything useful. There are the occasional SSL cert validation things, but I don’t believe those are related at the moment? (And I haven’t had one in since last wednesday, so I think I may have fixed that? I hope?)
bitlbee-3.6
pidgin-2.13.0 (that’s the libpurple version, right?
purple-hangouts-0_p20181202 and git master.
Original report by Wyatt Epp (Bitbucket: Wyatts, GitHub: Wyatts).
Sorry that I don’t have a more detailed bug report here, but I’m using this via bitlbee and things will work fine for… some indeterminate time (seems like it’s between 2-5 days generally?) before purple-hangouts will just stop receiving messages. This has been a less frequent problem for a long while (I think it was only once a week or less before), but it used to be I could restart bitlbee and when I reauth’d the “unread” messages that left notifications on my phone would come in, but that stopped happening… I think since bitlbee forced me to start running in forkdaemon mode?
I’m not seeing any error messages in the control channel that tell me anything useful. There are the occasional SSL cert validation things, but I don’t believe those are related at the moment? (And I haven’t had one in since last wednesday, so I think I may have fixed that? I hope?)
bitlbee-3.6
pidgin-2.13.0 (that’s the libpurple version, right?
purple-hangouts-0_p20181202 and git master.