Post by Bill Saunders
I am using the latest Zoom for Ubuntu 16.04. Since I don't own an
external webcam presently, I have been just using the built into my
laptop webcam (Dell Inspiron 1545). When I first tried to start using
Zoom a few weeks ago, there was frequent freezing, either of just my
video, or both my video and video participants. The first step was to
eliminate wireless and plug directly into the router with the cat5
cable. I then retested the other night and, over a three hour period
with three participants, I myself froze twice, but stopping and
restarting my camera solved it. At one point, everyone froze but
stopping and starting again solved it.
I may be using Zoom soon for situations other than for family and I'd
like to get the freezing issues solved. I realize that sometimes native
Win based programs revamped for Linux are left with errors and, if that
is the case, I'll have to live with it, but I wanted to first rule out
any other possibilities first.
Thanks in advance for any help. BTW, I did double the memory in the
laptop from the native 4 GB to 8 and swapped out the traditional hard
drive for a solid state drive... no reduction in freezing.
If you want an unsubstantiated rumor, it's my opinion that
some nitwit has been fooling around with the webcam architecture.
I've had failures where nothing but a reboot would recover
the webcam. Almost as if there was state information being
saved somewhere, between camera runs.
It does not work the way it used to. That's all I can tell you.
A couple of releases ago, everything was fine. (I could use
guvcview and the webcam "features" worked.)
When webcam support was originally moved from userland
to the kernel, the first release, the webcam caused a
kernel panic. That was the low point for webcams.
But something recently, maybe the last year to year and
a half, seems to have changed again, and I doubt someone
went into individual webcam drivers and fouled them up.
It's possible some architectural blocks were moved around,
something added, that sort of thing, but I've not been
able to find any mention of what that might be.
If I had to guess, my first guess is its not a flaw
in the gear you bought. It's something else. It's not
leaving tracks in dmesg either.
The last time I needed to make a "reliable" call, with
the doctor at the hospital, I used Windows 7 (because
there's no way that Windows 10 with its random
frameserve would have worked). And after my random
"quit and stay broken" behavior on Linux, I was kinda
between a rock and a hard place. The only good thing you
can say about Windows 7, is it wasn't receiving any
"updates" to destabilize it.
I was fortunate, that the hospital system allows
"test connections" for two weeks before your
appointment. (It's a kind of loopback test.)
And I could test, test, and retest the crap,
to improve the odds of it working when the appointment
Find the oldest release where the repository is
still available, set it up, and test your camera
again. Presumably the Zoom supports older releases
that are still "officially supported".