> After upgrade my env today, with unstable packages of jitsi-meet,
> dissappeared the "share dekstop" option.
Did you have any changes in interface_config? Other than that
everything in the settings should be fine.
Nothing. I only reinstalled the deb packages and did the common confs, like
certificates and domain.
After some fight, I purged all packages and reinstalled all from scratch.
It returned to life.
So, I tried to roll back the old version, and nothing. After, I purged all
> packages, and restarted the deploy, as explained in quick install,
> success. In this time, The system can't more connect people. I can enter
> a room and see my self, but a second person, can't see me or vice versa.
> Some tip or suggestion?
Check the logs, of the client, jicofo, videobridge.
Curious... In client have 1 error and 1 warning:
Failed to load resource: the server responded with a status of 404 (Not
This error is old. Since begin of year I see this error, but without impact.
DEPRECATED JS - Cookie has been deprecated since 5.8.0 and will be removed
in a future release. Use cookie instead.
at assign (<anonymous>)
About the share screen, need to insert a UID extension to get this resource
in the screen. Is working fine now.
In other hand, I saw that now we can mute all (the eye in the sidebar), but
when I select the language to brazilian portuguese, appears a square.
Changing again to en-US, the icon returns. I believe that is a bug.
In other hand, how I set the defaultLanguage, in config.js for "pt-BR" ?
And, when possible, please, update the pt-BR translation. I finished it
So, this fact bring a question: the last unstable deb package is "stable",
> considering the fact to connect at least two people? Is it working? I
> understand that I'm using a "unstable" package. In other hand, I saw that
> the stable package is a lot old, and I saw too that the testing is less.
> how many time is the build cycle of testing? As I use in a "production"
> (all knows that is a lab env), I can play with this edge versions.
> At last, I saw in other emails that you have jenkins. Have some public
> where we can follow the builds? Is interesting to know when we run a env
So on every commit to jitsi-meet, lib-jitsi-meet, jicofo and jvb there
is a build. There is a mailinglist named cruisecontrol where all mails
from the builds go, you can subscribe to it. There is no public
interface for jenkins.
The builds create debian packages and automatically deploy it to the
unstable repo, from there we update a machine called beta which is
used to test those builds and have uptodate deployment. The tests are
in jitsi-meet-torture repo, if they are successful the mail sent to
cruisecontrol mailinglist says so.
If the initial tests are fine, there are internal performance tests
which are kicked and if they are successful that build goes
automatically to testing.
Builds in testing are kept till we move a build from there to stable,
which for now is a manual step.
Thank you, Damencho, by your explanation.
If I understood correctly, is better to use a testing package (that you
didn't speak about) that the unstable, because it can break in a production
env. Or not?
Testing is a bit more old (is not the latest release), but very more close
to unstable that to stable.
And, more one time, thank you.
2017-05-10 21:53 GMT-03:00 Damian Minkov <firstname.lastname@example.org>:
On Wed, May 10, 2017 at 7:08 PM, Claudio Ferreia Filho > <email@example.com> wrote: