From: forkosh@panix.com   
      
   John Forkosh  wrote:   
   > John Forkosh  wrote:   
   > <>   
   >>> I hope this helps ... Sylvain Robitaille   
   >>   
   >> Yeah, very helpful, thanks. By the way, I did get the slackbuilds   
   >> zoom-linux source running without a hiccup on my desktop, with a   
   >> slack64-current downloaded on 12/25/20 and not upgraded since   
   >> (it had originally failed on the linux partition of my laptop   
   >> running slack64-current downloaded 9/1/19 and not upgraded since).   
   >> But I hadn't tried that before because my desktop doesn't have   
   >> a camera or microphone, so it's useless for zoom. And maybe it's   
   >> only running because without a camera/mike to connect to, the code   
   >> causing the crash isn't executed. I was considering buying a cheap   
   >> usb camera/mike for the desktop after seeing zoom-linux run on it,   
   >> but then re-considered after seeing it fail so miserably on my   
   >> laptop. (And the desktop has no windows partition.)   
   >   
   > Okay, eliminated one variable: used a spare desktop partition   
   > to install the same slackx64_15.0rc1 that's on the laptop where   
   > zoom-linux crashes (installed using exactly the same usb stick).   
   > And zoom-linux again runs without a hiccup on the desktop.   
   > I even joined a test meeting from my browser, and it "successfully"   
   > said it  Tested 0/0  cameras, but announced that it couldn't find   
   > any microphones. But nothing crashed or even reported any errors.   
   > Indeed, there's a big, long ~/.zoom/logs/zoom_stdout_stderr.log   
   > (36851 bytes) whose first and last few lines are...   
   >    ZoomLauncher started.   
   >    Zoom path is: /opt/zoom-linux   
   >    cmd line:   
   >    Start subprocess: /opt/zoom-linux/zoom sucessfully,  process pid: 30598   
   >    zoom started.   
   >        <>   
   >    zoom exited normally, exit code is 0 .   
   >    ZoomLauncher exit.   
   > What would have happened if there were actually a camera and microphone   
   > connected??? I have no idea. But it's either that or some difference   
   > between my desktop (a whitebox with an Asus mb) and my Teclast f5r laptop.   
   > I couldn't figure out a way to "disable" the camera/mike on the laptop,   
   > so that zoom-linux couldn't detect them, or I'd have run some further   
   > tests and narrowed down the possibilities to one.   
      
   Okay, final followup of myself (I think), good news but a mystery...   
      The good news is that now "everything just works", desktop and laptop,   
      both running x64-15.0rc1 downloaded 8/18/21 (kernel 5.13.11).   
      Note that, like I said previously, the laptop had crashed at first,   
      and its ~.zoom/logs/ directory still has the .dmp file from that.   
      And the mystery is that when I tried running it again, it just worked,   
      camera, speaker, mike tests all worked fine, and I even joined an   
      actual meeting without any problem. But I can't think of a single   
      thing I changed between when it crashed and when it now works.   
      As far as the desktop goes, I got a logitech c930e webcam for it,   
      and that just immediately worked running x64-15.0rc1 (like I said   
      earlier, when running some older x64-current, zoom failed due to   
      missing qt libraries).   
   --   
   John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)