flathub / us.zoom.Zoom

https://flathub.org/apps/details/us.zoom.Zoom
35 stars 44 forks source link

Zoom refuses to start after latest update #437

Closed 0unknwn closed 6 months ago

0unknwn commented 6 months ago

After the latest update (a7c23401) Zoom refuses to start on my

machine.

I was able to make it work again by reverting to the commit before (6241302e) with:

flatpak update --commit=786cd52f8219276edd0184f3c6fa0ca7041c3814369fe378dc068a0864b049a9 us.zoom.Zoom

To prevent it from getting updated automatically I also run:

flatpak mask us.zoom.Zoom

Then you have to run the following command to update it again, after this is fixed:

flatpak mask --remove us.zoom.Zoom
theflu commented 6 months ago

I am having the same issue on Ubuntu 22.04

$ flatpak info us.zoom.Zoom 

Zoom - Video Conferencing, Web Conferencing, Webinars, Screen Sharing

          ID: us.zoom.Zoom
         Ref: app/us.zoom.Zoom/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 5.17.1.1840
     License: LicenseRef-proprietary
      Origin: flathub
  Collection: org.flathub.Stable
Installation: user
   Installed: 6.9 MB
     Runtime: org.freedesktop.Platform/x86_64/23.08
         Sdk: org.freedesktop.Sdk/x86_64/23.08

      Commit: 6706c80cba4a13af60d269900ab4c7f56568bcc6ce4bc4493bd6ec2f123f3be1
      Parent: 786cd52f8219276edd0184f3c6fa0ca7041c3814369fe378dc068a0864b049a9
     Subject: Update zoom.tar.xz to 5.17.1.1840 (a7c23401)
        Date: 2024-01-11 07:31:32 +0000
$ flatpak run --command=sh us.zoom.Zoom
[📦 us.zoom.Zoom /]$ zoom
(process:9934): GLib-CRITICAL **: 09:22:15.014: Failed to set scheduler settings: Operation not permitted
muelli commented 6 months ago

@abachm it looks like the newer version should be rolled back. Can you have a look?

fightingtexasaggie commented 6 months ago

I can confirm the same thing this morning on Fedora 39.

fta@localhost:~$ cat /etc/redhat-release 
Fedora release 39 (Thirty Nine)

fta@localhost:~$ flatpak info us.zoom.Zoom 

Zoom - Video Conferencing, Web Conferencing, Webinars, Screen Sharing

          ID: us.zoom.Zoom
         Ref: app/us.zoom.Zoom/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 5.17.1.1840
     License: LicenseRef-proprietary
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 6.9 MB
     Runtime: org.freedesktop.Platform/x86_64/23.08
         Sdk: org.freedesktop.Sdk/x86_64/23.08

      Commit: 6706c80cba4a13af60d269900ab4c7f56568bcc6ce4bc4493bd6ec2f123f3be1
      Parent: 786cd52f8219276edd0184f3c6fa0ca7041c3814369fe378dc068a0864b049a9
     Subject: Update zoom.tar.xz to 5.17.1.1840 (a7c23401)
        Date: 2024-01-11 07:31:32 +0000
fta@localhost:~$ flatpak run --command=sh us.zoom.Zoom
[📦 us.zoom.Zoom ~]$ zoom
[📦 us.zoom.Zoom ~]$ 

Although I didn't see the GLIB message, I did see this in dmesg:

traps: zoom.real[21115] trap int3 ip:7fea5a3c1c2c sp:7ffcd067d6a0 error:0 in libcef.so[7fea56545000+9feb000]
fightingtexasaggie commented 6 months ago

The RPM version of Zoom for Fedora seems to run fine. (zoom-5.17.1.1840-1.x86_64)

ghost commented 6 months ago

I am experiencing the same issue on Fedora Silverblue 39. I am unable to join my meetings. Please address this as soon as possible.

0unknwn commented 6 months ago

@PhoenixFossGR, have you tried to run this command?

flatpak update --commit=786cd52f8219276edd0184f3c6fa0ca7041c3814369fe378dc068a0864b049a9 us.zoom.Zoom

matdave commented 6 months ago

For anyone stumbling upon this, don't forget to flatpak mask --remove us.zoom.Zoom after this has been fixed, or you will be locked into an outdated version.

ghost commented 6 months ago

@PhoenixFossGR, have you tried to run this command?

flatpak update --commit=786cd52f8219276edd0184f3c6fa0ca7041c3814369fe378dc068a0864b049a9 us.zoom.Zoom

This worked perfectly, thank you so much!

For anyone stumbling upon this, don't forget to flatpak mask --remove us.zoom.Zoom after this has been fixed, or you will be locked into an outdated version.

I am encountering the following error: Error: No current masked pattern matching us.zoom.Zoom

milliams commented 6 months ago

I am encountering the following error: Error: No current masked pattern matching us.zoom.Zoom

You only need to do the flatpak mask --remove us.zoom.Zoom if you've previously done flatpak mask us.zoom.Zoom. The mask locks the version in place so a flatpak update doesn't go ahead and re-update the version of Zoom before this is fixed. If you've masked it now, you'll need to remember to mask --remove in the future.

stylerw commented 6 months ago

Can confirm the same issue on Fedora Kinoite 39 with this latest version. Flatpak Zoom crashes on launch after latest update. Rolled back to an earlier commit and all is good, but this release is absolutely busted.

droghio commented 6 months ago

Can also confirm error with Rocky 9.1. Loaded ~/.zoom/logs and got the following:

ZoomLauncher started.
Zoom path is: /app/extra/zoom
cmd line: 
Start subprocess: /app/extra/zoom/zoom sucessfully,  process pid: 3 
Can't load/home/droghio/.config/zoomus.conf
sh: line 1: pacmd: command not found
[13 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[13 preload-host-spawn-strategy] Warning: waitpid override ignores groups
[13 preload-host-spawn-strategy] Warning: waitpid override ignores groups
                             Class      App      Lib Possible Culprit Flags
                resip::Connection      656      656 
                      resip::Data       36       36 
                 resip::DnsResult     1080     1080 
                   resip::Headers        1        1 
          resip::MsgHeaderScanner       40       40 
                resip::SipMessage     5224     5224 
         resip::TransportSelector      896      896 
                     resip::Tuple      128      128 
              resip::UdpTransport     1144     1144 
          resip::GenericIPAddress       28       28 

zoom started.
[27 zypak-sandbox] Failed to send spawn request to supervisor: Bad file descriptor (errno 9)
[0112/015235.597259:FATAL:zygote_host_impl_linux.cc(201)] Check failed: . : Operation not permitted (1)

Just ran flatpak update thinking it was originally an outdated Nvidia platform but still no dice.

At first glance may be related to https://github.com/electron/forge/issues/2805 but haven't verified. Confirmed rolling back fixes the issue.

0unknwn commented 6 months ago

I really wonder, why this was merged, as the problems with this build where discussed here: #429.

Maybe there should be a stricter policy with testing in this repo.

muelli commented 6 months ago

Maybe there should be a stricter policy with testing in this repo.

well. I generally agree. And I am very careful when merging Zoom updates because I was eagerly merging to provide the latest and greatest to our users but then got bitten a few times by faulty updates. Now I'm very hesitant which also upsets a few users. Anyway, I guess that @abachm will be a bit more diligent the next time.

Oh, sorry that we broke your setup!

Speaking more broadly, I could imagine an automatic smoke-test to make sense. Apps on Flathub are all expected to spawn a windows that lasts for longer than, say, 10 seconds. I guess one could automate the task of launching an app and testing for the presence of a window.

ghost commented 6 months ago

Is it safe to update now, or should we stick with the old version for a few days? GNOME Software is currently pushing version 5.17.1.1840.

takluyver commented 6 months ago

There's some details on #429 - the summary is that I think we need a newer Zypak to fix compatibility. I asked for a new release, but it doesn't seem to be happening quickly, so we may need to just build it from a commit.

It's really frustrating that the bot will open several PRs for the same release with no warning. #436 was merged after one user said it worked, when it was identical to #429, where two users had already said it crashes. :disappointed:

danielebrox commented 2 months ago

I'm using Fedora 40. Both dnf and flatpak methods crash on launch. The only way to get it to work is to do what is suggested at the beginning of this thread. I have no idea what's going on.