I'm pretty sure the cause of this bug was again an incorrect python thread state, same as in bug #1195857 and a number of similar cases. The just released Onboard v0.99.0 has fixes for all of them..
I'm pretty sure the cause of this bug was again an incorrect python thread state, same as in bug #1195857 and a number of similar cases. The just released Onboard v0.99.0 has fixes for all of them..