[Linux] Regarding Nvidia+Xwayland/Wayland | Community
Skip to main content
Newcomer
August 23, 2022
Question

[Linux] Regarding Nvidia+Xwayland/Wayland

  • August 23, 2022
  • 6 replies
  • 0 views

Hello,

 

I have opened a ticket regarding an issue I had with Zoom crashing on Nvidia when using Wayland session (and also at the same time filing a bug to Nvidia https://github.com/NVIDIA/egl-wayland/issues/63 in which I discovered it is an issue on Zoom's end). The reason I am trying to use on Wayland is because Xwayland is showing a blank window when opened (which turns out is an issue on Zoom's end as well).

 

The support representative I talked to in the ticket was helpful and tried to get a response from the engineering team (which never came) regarding the response I received from Nvidia in the github issue I linked here.

 

Direct link to the response I received from Nvidia: https://github.com/NVIDIA/egl-wayland/issues/63#issuecomment-1204312146

 

So I am raising it here as well just in case it can lead to a more helpful response. I am not expecting an ETA of course but just acknowledgement that it is being worked on.

    6 replies

    Newcomer
    August 23, 2022

    I'm experiencing this issue as well. Zoom needs to upgrade its version of Qt from 5.12 to 5.13. As is, they're shipping an old buggy version of this library to users, which might have other issues besides this one.

    Newcomer
    August 23, 2022

    Another thread where people have reported this same issue:

    https://community.zoom.com/t5/Meetings/The-latest-Zoom-client-not-start-on-Linux/m-p/70035

     

    Newcomer
    September 8, 2022

    Fellow "video application used by millions of people" OBS recently upgraded to Qt version 6: https://github.com/obsproject/obs-studio/discussions/6481

     

    Seems good to not be stuck on a deprecated version of a GUI library. I hope this is in the works at Zoom.

    Newcomer
    September 8, 2022

    Yeah I know about that.

    OBS were always up to date regarding the Qt version I believe.

    I will be surprised if Zoom makes the jump from 5.12 to version 6 but it is required to get everything to work unless they backport some of the changes to the version they use.

    Newcomer
    November 18, 2022

    I've been having an issue with Zoom crashing and I finally landed on this thread to find the root cause. This is disappointing. Seems like nvidia users on wayland are out of luck if we want to use Zoom.

     

    lolsniperftw - let me know if you ever found a workaround

    Newcomer
    December 5, 2022

    Is there any work-around that will help a Linux+Wayland+Nvidia user to work with Zoom at this time?

    Newcomer
    December 5, 2022

    Nope.
    Right now you can either switch to X11 or use Zoom on the browser (Firefox should work fine afaik).

    Newcomer
    December 5, 2022

    Thanks for the info. I'll try the browser. There are good reasons to begin switching over to Wayland. Zoom is the only application that is giving me any problems, so I can't justify not switching anymore.

    Newcomer
    February 13, 2023

    The latest update to Zoom seems to not instantly crash, which is an improvement from earlier. Was there some sort of update that addressed the Qt issue?

     

    Unfortunately for me, the application is unbearably slow to respond, so something odd is still going on. 

    Newcomer
    February 19, 2023

    Yeah there was an update to Zoom that fixed both Zoom crashing on native Wayland and blank window in Xwayland. The application is also very slow to respond here in native Wayland and in Xwayland it is sometimes crashing when joining a meeting.

    Newcomer
    March 24, 2023

    I'm on a desktop, using a gtx 1080.

     

    Zoom works for now, but it is very slow, and weirdly the window only visually updates while my mouse is moving over it. Super odd.

    Newcomer
    March 24, 2023

    That is  because you probably launched it in Wayland mode instead of Xwayland(which is the default).

    Newcomer
    March 27, 2023

    Did it work now?


    Unfortunately no... it still seems to launch in Wayland mode even after commenting out those lines in my startup script.