Zoom-Client does not start after Update

rothom

I have installed the Zoom client in the current stable version via Flatpak. I am aware that it is an isolated application, but since the last update (Sync Updates for Week 48.5) the client no longer starts. I have already uninstalled and reinstalled it, but the result remains the same :-(

Cheers!

brent

rothom budgie with flatpak.
Can Confirm.
Double click= launch for 2 seconds then disappear
flatpak run us.zoom.Zoom = launch for 2 seconds then disappear edit/typo

second edit: I update flatpak daily

ReillyBrogan

Run sudo flatpak update

rothom

ReillyBrogan

The following output appears:

`Suche nach Aktualisierungen …

Nichts zu tun.

(flatpak update:20132): libsoup-WARNING **: 19:19:12.362: (../libsoup/soup-session.c:334):soup_session_dispose: runtime check failed: (soup_connection_manager_get_num_conns (priv->conn_manager) == 0)

(flatpak update:20132): libsoup-WARNING **: 19:19:12.363: (../libsoup/soup-connection-manager.c:84):soup_host_free: runtime check failed: (host->conns == NULL)

(flatpak update:20132): libsoup-WARNING **: 19:19:12.363: Disposing connection 0x55b8ecf81c40 while still connected`

ReillyBrogan

rothom Did you restart after that? I'm not able to read that language.

brent

ReillyBrogan edit:

boot up,launch terminal

flatpak update -y && flatpak remove --unused -y
       ID                            Branch           Op       Remote        Download
 1. [✓] org.kde.Platform.Locale       5.15-23.08       u        flathub       18.0 kB / 377.8 MB
 2. [✓] org.kde.Platform              5.15-23.08       u        flathub       15.4 MB / 335.1 MB

Updates complete.

flatpak run us.zoom.Zoom
---no launch, no flicker.

reboot solus, launch terminal
flatpak run us.zoom.Zoom
launches for 2 seconds, disappears

menu doubleclick: same^^

*conclusion, nothing appears to have changed from the kde update.
**hunted about 20 min last night found no issues with this except a 2020 thread that said freedesktop rebuilds were sandbagging zoom so wait for update, etc.

2nd EDIT: Unlike OP, I am getting no terminal output at all.

rothom

ReillyBrogan

The Flatpak packages were all up to date, restart did not bring any changes.

pokmu

I have no evidence to support this claim, but I would assume it's a problem with whatever version of Electron they're using being out of date/broken.

NewUser2020

I have the same problem. Hope next update will fix it.

SOLUSfiddler

Same here:
Updated Flatpak via the terminal, rebooted the laptop, and starting the app does nothing except starting the "start window", but before it's fully visible it crashes and nothing else happens.
(Budgie, Zoom = flatpak)

ReillyBrogan

Well as far as I'm aware the issue here is that Mesa in the Freedesktop SDK needs to be updated to work with the system Mesa 23.3. Some applications are on runtimes such that they have already got that update automatically, others are using older runtimes or manually specified runtimes in such a way that they need to do something manually to update. I'm not really sure the best way to address this honestly, we really want to keep Mesa 23.3 since we want it on the updated ISOs (which we are actively working on) as Mesa 23.3 is required to support upcoming AMD APUs.

brent

ReillyBrogan a dilemma, then.
for work I need Zoom about 4X a month.
but I have a spare OS I can dust off (zoom works in endeavour, I checked). So I can roll with it. Don't want to boot up just for that but I can.
Others in this thread may not have that luxury so I can't speak for them.

----appimage has zoom available. you think the mesa thing would effect the appimage? might download this and check it out.
edit: forgot to say thanks for checking it out

brent

[CAN CONFIRM: appimage does not work in solus budgie. It launches the base window--and stays in sys tray--but when you hit 'open xdg-open' button it flickers and crashes like the flatpak.]

Axios

If I understand flatpak right it uses the most current mesa if its flatpak or system.
So if the flatpak works with there stuff is there a way to start lets say zoom and tell it to use the flatpak mesa?

I may be understanding this all wrong I saw some examples of that somewhat online.
If I am in error ignore.
Interesting (Old info tho)

Just info

ReillyBrogan

Axios I'm almost certain that that is incorrect unfortunately. They're basically their own entire OS with their own packages and everything. Now, some flatpaks might be configured to use Mesa on the host but that's not default behavior by any means. Usually this isn't a problem since breakage like this is Mesa is very rare.

brent

Axios I like the way you are thinking though. if it can be audited (flatpak can) then it could be tinkerable.

Axios

ReillyBrogan Thanks thats why I ask.

Jason5

Can confirm the issue with Stremio from Flatpak

WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed.
Could not bind NETLINK socket: Address already in use (98)
qml: Loading web UI from URL: https://app.strem.
qml: Stremio Shell version: 4.4.164
qml: **** Completed. Loading Autoupdater ***
qml: Auto-updater: skipping, possibly not running an installed app?
Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat:: DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat:: DefaultColorSpace, profile QSurfaceFormat::NoProfile)

ReillyBrogan

I've heard that Zoom may have updated the flatpak again to address this.

rothom

ReillyBrogan

Hm, the update says: Nothing to do, so no updates for Zoom.

brent

ReillyBrogan that's great news. I will be patient.