crash on start in Gnome with Wayland enabled

[ikluft]

On the Zoom flatpak 5.8.6.739 it crashes when starting on Gnome with Wayland.

I recently switched from XFCE to Gnome when I upgraded to Fedora 35. So I don't know if this is a new problem with the Zoom ccntainer. I found a workaround to go into Flatseal and disable the container's access to Wayland.

Here's the Zoom log:

ZoomLauncher started. Zoom path is: /app/extra/zoom cmd line: Start subprocess: /app/extra/zoom/zoom sucessfully, process pid: 4 Can't load/home/--/.config/zoomus.conf Failed to create secure directory (/run/user/--/pulse): Too many levels of symbolic links No PulseAudio daemon running, or not running as session daemon. Class App Lib Possible Culprit Flags resip::Connection 648 648 resip::Data 36 36 resip::DnsResult 1080 1080 resip::Headers 1 1 resip::MsgHeaderScanner 40 40 resip::SipMessage 5208 5208 resip::TransportSelector 866 864 resip::Tuple 128 128 resip::UdpTransport 1112 1112 resip::GenericIPAddress 28 28

zoom started. Client: Breakpad is using Single Client Mode! client fd = -1 Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

zoom was exited due to a handled signal: 11 ZoomLauncher exit.

---

Flatseal screenshot for the workaround - I disabled Wayland and "Fallback to X11" but later testing showed disabling Wayland is enough to fix it. :

[nedrichards]

Yup, we don't have wayland enabled by default since upstream don't recommend it. I'd love for them to do so! Always worth testing with newer updates though.