Closed marco44 closed 1 year ago
I can confirm:
[Wed Sep 14 21:00:57 2022] QSGRenderThread[29100]: segfault at 0 ip 00007f002c091843 sp 00007eff60ff9360 error 4 in libwayland-client.so.0.20.0[7f002c090000+7000]
[Wed Sep 14 21:00:57 2022] Code: 0f 29 55 80 0f 29 5d 90 0f 29 65 a0 0f 29 6d b0 0f 29 75 c0 0f 29 7d d0 64 48 8b 04 25 28 00 00 00 48 89 85 28 ff ff ff 31 c0 <49> 8b 14 24 48 8d 45 10 4c 8d b5 80 fe ff ff 48 89 85 70 fe ff ff
[Wed Sep 14 21:02:50 2022] QSGRenderThread[30991]: segfault at 0 ip 00007fd61864e843 sp 00007fd552ffc360 error 4 in libwayland-client.so.0.20.0[7fd61864d000+7000]
[Wed Sep 14 21:02:50 2022] Code: 0f 29 55 80 0f 29 5d 90 0f 29 65 a0 0f 29 6d b0 0f 29 75 c0 0f 29 7d d0 64 48 8b 04 25 28 00 00 00 48 89 85 28 ff ff ff 31 c0 <49> 8b 14 24 48 8d 45 10 4c 8d b5 80 fe ff ff 48 89 85 70 fe ff ff
Fedora 36, KDE, Wayland
I'm also observing the crash when joining a call.
Fedora 36 and 37, KDE, Wayland
I had this issue in Pop! Os 22.04 until I installed xdg-desktop-portal-wlr_0.6.0-1
(as part of an unrelated effort to fix screensharing). This seems to have eliminated the problem for myself though I do not know why.
Same on Fedora 36/37 KDE Wayland
Had to revert to the rpm installation and set noSandbox=true
Otherwise the app systematically crashes when joining a meeting.
Screensharing is not allowed unless running on gnome.
Any information if the developpers are working on fixing this issue? Flatpak is meant to make development distro and DE agnostic after all. @jesse-osiecki can you develop a bit what you got fixed with xdg wlr?
Same here with the rpm zoom-5.12.2.4816-1.x86_64 fedora36/Xorg/cinnamon. The Log ends up with
zoom started.
[CZPClientLogMgr::LogClientEnvironment] [MacAddr: FC:77:74:22:EA:52][client: Linux][OS: Fedora Linux 36 Thirty Six x64][Hardware: CPU Core:6 Frenquency:2.6 G Memory size:31761MB CPU Brand:Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz GPU Brand:][Req ID: ]
Linux Client Version is 5.12.2 (4816)
QSG_RENDER_LOOP is
XDG_CURRENT_DESKTOP = X-Cinnamon; GDMSESSION = cinnamon; XDG_SESSION_TYPE = x11
Graphics Card Info:: 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630]
Zoom package arch is 64bit, runing OS arch is x86_64
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id
qt.network.ssl: QSslSocket: cannot resolve SSL_get_peer_certificate
qt.scenegraph.general: threaded render loop
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
No PulseAudio daemon running, or not running as session daemon.
zoom was exited due to a handled signal: 11
ZoomLauncher exit.
I used to have this problem on Fedora 36 KDE (Wayland) but it seems to have gone away for me with the latest version (5.12.2.4816) or at least it doesn't appear as systematically as it did before.
I'm experiencing a problem where the Zoom flatpak version 5.12.9.367 crashes almost immediately after launching under a Gnome Wayland session in Fedora 37 Workstation. Zoom's windows will freeze up, and then Gnome will say the program isn't responding and I have to force quit Zoom.
Two things stand out in the stderr output: 1) the fact that Zoom is looking for pacmd but can't find it (could the crash be related to Fedora using Pipewire?) and 2) the line that says libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
(possibly an incompatibility with AMDGPU?).
Yeah, I had the same problem with the flatpak version on Manjaro. Downgraded to the aur and now it works again had no effect.
Linux Mint 21.1 Cinnamon edition here, and Cinnamon is gnome-based, I installed Zoom via Software Manager and it grabbed 5.12.9.367 from Flathub. Upon initially loading Zoom, the client crashes and I get asked to send an error report. But then I find zoom is still loaded, but no longer logged into my zoom account. It appears somewhat related to whether or not you logged into your account first or not. If I stay logged out of my zoom account in the client, I can close it and load it and it'll only crash 50% of the time on startup. If I log into my Zoom account and then close Zoom and re-open it, then it's pretty much 100% going to crash on startup.
I am also experiencing problems with Zoom. (Ubuntu 20.04 with KDE.) It was working as recently as last week (Jan. 10). The behavior I experienced today is: Browse to the URL -> Zoom begins to load -> Meeting host lets me in -> I am on the call for a fraction of a second, when it crashes. To the other meeting participants, it appears that I am still there. dmesg reports a segfault: zoom[3369]: segfault at 10000018 ip 00007f5de307e3ce sp 00007fff4a977298 error 4 in libQt5Core.so.5.12.10[7f5de2de0000+589000] When I try a second time, Zoom recognizes that there's an issue. If I try to type this feedback there, however, the feedback window closes when it crashes again. I was able to get into the meeting on my phone.
Have similar problem on Debian 11 (xfce) like @paithan described. Zoom Version: 5.13.5 (431)
Feb 8 10:02:40 acer kernel: [ 2057.838650] zoom[3973]: segfault at 0 ip 0000000000000000 sp 00007ffea804a5c8 error 14 in zoom[55929c200000+8dec000]
Feb 8 10:02:40 acer kernel: [ 2057.838659] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
Feb 8 10:02:58 acer kernel: [ 2075.435237] zoom[4399]: segfault at 30 ip 0000000000000030 sp 00007ffe002a65f8 error 14 in zoom[55ee15c00000+8dec000]
Feb 8 10:02:58 acer kernel: [ 2075.435250] Code: Unable to access opcode bytes at RIP 0x6.
In my (uninformed) opinion, this seems to be more of a zoom issue (something for the zoom developers to fix), rather than a flatpak issue (something we can fix).
My reasoning for this opinion is that when using other flatpaks that perform similar functions to zoom (i.e. opening a zoom meeting in the chromium flatpak), none of these issues seem to exist.
Thanks for the triaging @violetmage !
this issue re-appeared since the latest update
this issue re-appeared since the latest update
+1
I have worked around the issue by clicking the sidebar icon to hide the sidebar before it finishes loading, which causes the crash. This took a few tries - it's very fast.
@hacker1024 for me it loaded (crashed) too quick, however, i was able to use the workaround mentioned here: https://aur.archlinux.org/packages/zoom
I found a workaround for this issue start zoom with QT_QPA_PLATFORM=xcb, and toggle off sidebar. after that you can run zoom with QT_QPA_PLATFORM=wayland and it will not crash untill you toggle the sidebar back 😃
I found a workaround for the sidebar issue. Set disableCef=true in zoomus.conf Works for me, Debian Sid
I found a workaround for the sidebar issue. Set disableCef=true in zoomus.conf Works for me, Debian Sid
Thanks, that gets around the need to find a way to disable the sidebar manually. Doing that was itself a work-around to stop the Zoom app crashing. Some people had found disabling the sidebar fixed the crash. Sadly, without the sidebars (using disableCef), the app still crashes when I join a meeting. It now doesn't close instantly, instead the app freezes with the output from my camera frozen on screen, then shuts a few seconds later.
Reverting to ba3b018bc340be3260c49cd2fd0cb6e7d3a34810135d5818d085574c59ff0408 fixes the issue I'm using latest kde, with wayland, on archlinux
No idea how to get a backtrack on a flatpak package, if there is a walkthrough somewhere, I can provide the result.