I find the "start" method of org.jitsi.service.libjitsi.Libjitsi
doesn't check whether Libjitsi has been started. So it can lead to
multiple initiation problem.
I'm not clear why Libjitsi does like that, while I suggest to add some
code to fix it.
The patch file has been attached on this mail, it's pretty simple.
What do you think?
School of Electronics Engineering & Computer Science
Peking University, China
libjitsi-start.diff (849 Bytes)