Closed xnandersson closed 8 years ago
I have a very strange observation. When I enabled exhaustive logging, I could connect to the audio even though virbr0 was present. I tried 3 times successfully. (I had GST_DEBUG=5 running)
Could this be some kind of race condition? That the i/o was slowing down the system enough for the setup of the call to be established?
I do have the same i/f, I can join audio, though I still have audio problems (even after the May 23rd patch), maybe related ?
@tmuehlhoff If you can join audio, can you be more specific what your actual 'audio problems' are? Bad sound quality, you can hear the others speaking but they can't hear you, or something else?
@tmuehlhoff Or maybe you're experiencing something like #85?
Behaviour is strange. If I started pidgin normally (without logging), I could connect - no problem. The problem is there if I start Pidgin with logging. BUT if the logging is EXHAUSTIVE, I can AGAIN connect to audio. It is consistent, but strange consistent :-)
I guess the title is not true, but I don't have a better name for it.... :-(
@xnandersson Because the recent larger libnice update may have rendered this issue obsolete, I'm switching its state to 'more information needed'.
Please try to reproduce the bug with up-to-date PPA. Otherwise I'll close the ticket after 14 days, as is my common practice.
@xhaakon Sure thing! I'll get at it :-)
This issue hasn't been reproduced after a libnice update, so closing.
On my computer I have this interface, setup by Virtualbox.
Having this interface blocks me from joining audio. I can see the shared screen though, and the chat.
If I disable the interface with:
...then I can connect just fine.