Mageia forum

According to Mageia Wiki, I installed zoom. Than I try to run it from CLI. It started and ended without any error info.
Below what I found in ~/.zoom/logs:

Code: Select all

[maciek@Piotr logs]$ cat zoom_stdout_stderr.log
ZoomLauncher started.
Zoom path is: /opt/zoom
cmd line:
CreateReportChannel bp_server_fd=4
$HOME = /home/maciek
export SSB_HOME=/home/maciek/.zoom; export QSG_INFO=1; export LD_LIBRARY_PATH=/opt/zoom; export BREAKPAD_CLIENT_FD=3; /opt/zoom/zoom ""
zoom started.
[CZPClientLogMgr::LogClientEnvironment] [MacAddr: D8:CB:8A:9A:3C:C6][client: Linux][OS: Mageia 7][Hardware: CPU Core:12 Frenquency:3 G Memory size:32015MB CPU Brand:Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz GPU Brand:][Req ID: ]
Linux Client Version is 5.4.2 (53391.1108)
QSG_RENDER_LOOP is
XDG_CURRENT_DESKTOP = KDE;   GDMSESSION =
Graphics Card Info:: 03:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)
Zoom package arch is 64bit, runing OS arch is x86_64
ZoomLauncher: new dump generated from pid 24643, path: /home/maciek/.zoom/logs/5d79f070-78ba-444a-da1748aa-1177917a.dmp
$HOME = /home/maciek
sh: linia 1: 24643 Naruszenie ochrony pamięci   (zrzut pamięci) /opt/zoom/zoom "" ## TRANSLATION - Memory protection violation (memory dump)
success to create child process,status is 35584.
zoom exited normally.
Something went wrong while running zoom,exit code is 139.
ZoomLauncher exit.
[maciek@Piotr logs]$ pwd
/home/maciek/.zoom/logs

Attached file contain more crash info but I dont know how to interpret one.
Any idea what to do?

Did you also read the hint on that wiki page?

NB Update as of November 2020: an incompatibilty issue with the handling of Qt in the Fedora version of Zoom and the Mageia environment requires a special step to launch zoom. This is detailed below.

https://wiki.mageia.org/en/Using_Zoom_c ... 2020_11_14

So I use such command running from CLI:

(unset QT_PLUGIN_PATH; /usr/bin/zoom %U)

But it hang during login via Google account...

And there's no output at all if you run it like that?

Code: Select all

unset QT_PLUGIN_PATH; /usr/bin/zoom

Seems to be an issue with the embedded browser, as mentioned e.g. in https://github.com/NixOS/nixpkgs/issues/73532
If it still hangs during login, I'd say you should contact zoom support.

doktor5000 wrote:And there's no output at all if you run it like that?

The initial window with login options appears always using this syntax. In my case I use Google account for authentication. Just simple click to Google login option, shows next window with "Connecting to Google" info and rotating circle. Thats all.
But maybe 2 or 3 times it was possible to fully login to Zoom account via Google. Strange...

Don't know if it helps, I hope it does. I've downloaded zoom tar.gz, do not use its rpm.
The application does not work if I launch it from a Desktop icon much as described in this topic. To overcome this I've created a icon that launches zoom via a xterm:
$ xterm -e zoom

As an additional information, since I use zoom binaries, I also export LD_LIBRARY_PATH so as to include zoom directory libraries.

OK, I downloaded tar version and place the content (after un-tar) in user home dir.
I try many syntax`s with/without "unset" and/or "xterm" and/or "zoom" and/or "zoom.sh" or so.
The only fully working is the syntax as below, running from CLI.
But it always query about potential relocation of crash dump file. Is any workaround?

Code: Select all

[maciek@Piotr ~]$ unset QT_PLUGIN_PATH; ~/zoom/zoom.sh
=============================================================================================
This is debug mode of zoom client. Once crash, zoom will generate core dump under this mode.
=============================================================================================
Instead of writing the core dump to disk, your system is configured to send it to the "|/bin/false" instead.
Do you want to modify the default core dump file name?
 (yes) or (no):no
current user role:
maciek
/home/maciek/zoom
zoom started.
Client: Breakpad is using Single Client Mode! client fd = -1
[CZPClientLogMgr::LogClientEnvironment] [MacAddr: D8:CB:8A:9A:3C:C6][client: Linux][OS: Mageia 7][Hardware: CPU Core:12 Frenquency:3 G Memory size:32015MB CPU Brand:Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz GPU Brand:][Req ID: ]
Linux Client Version is 5.4.54779.1115
QSG_RENDER_LOOP is
XDG_CURRENT_DESKTOP = KDE;   GDMSESSION =
Graphics Card Info:: 03:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)
Zoom package arch is 64bit, runing OS arch is x86_64
AppIconMgr::systemDesktopName log Desktop Name: /usr/share/xsessions/01plasma
qt.svg: :/images/wechat.svg:10:6: Could not resolve property: #pattern0

Ok. I'm not an expert on this then I'll tell exactly what I do and works with no complains. I've created an executable in my home/bin directory called ZOOM.sh that contains:
#/bin/bash
cd /path_to_directory_where_zoom_was_untarred
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:zoom
cd zoom
./zoom

Then, for simplicity, I've created an icon for launching zoom with the following command:
xterm -e ZOOM.sh

I'm uploading a picture with the windows that pops up then.

I got memory fault using script above:

Code: Select all

[maciek@Piotr zoom]$ ~/Pobrane/ZOOM
zoom started.
Client: Breakpad is using Single Client Mode! client fd = -1
[CZPClientLogMgr::LogClientEnvironment] [MacAddr: D8:CB:8A:9A:3C:C6][client: Linux][OS: Mageia 7][Hardware: CPU Core:12 Frenquency:3 G Memory size:32015MB CPU Brand:Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz GPU Brand:][Req ID: ]
Linux Client Version is 5.4.54779.1115
QSG_RENDER_LOOP is
XDG_CURRENT_DESKTOP = KDE;   GDMSESSION =
Graphics Card Info:: 03:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2)
Zoom package arch is 64bit, runing OS arch is x86_64
AppIconMgr::systemDesktopName log Desktop Name: /usr/share/xsessions/01plasma
/home/maciek/Pobrane/ZOOM: linia 5: 28526 Naruszenie ochrony pamięci   (zrzut pamięci) ./zoom ## TRANSLATION - Memory protection violation

(memory dump)

I can't help. Don't know why this memory protection violation ocurred...
Sorry