Re: Working on Zoom port

Eric McCorkle <[email protected]>
Newsgroups gmane.os.freebsd.devel.x11,gmane.os.freebsd.devel.hackers
Message-ID <[email protected]>
On 5/3/20 5:50 PM, Eric McCorkle wrote:

> Indeed, it seems to be some kind of commercial version of Qt.
> 
> I have, however, gotten it to start all the way.  I added linux-c7-nss
> to the dependency list (provides libsmime3).  After that, you have to
> run the linux ldconfig:
> 
> # /compat/linux/sbin/ldconfig /compat/linux/opt/zoom/
> 
> (I have to run this as root, and the effects don't seem to carry over to
> my standard user account.  Confession: I don't fully understand what
> this is doing, and I imagine there's a "right" way to do this for ports")
> 
> If you do that, then zoom actually tries to start!  Unfortunately, it
> seems to be missing assets or something:
> 
> 
> No PulseAudio daemon running, or not running as session daemon.
> zoom started.
> Client: Breakpad is using Single Client Mode! client fd = -1
> QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
> [CZPClientLogMgr::LogClientEnvironment] [MacAddr: ][client: Linux][OS:
> CentOS Linux 7 (Core)][Hardware: CPU Core:4 Frenquency:3.1 G Memory
> size:32663MB CPU Brand:Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz GPU
> Brand:][Req ID: ]
> Linux Client Version is 3.5.385850.0413
> QSG_RENDER_LOOP is
> XDG_CURRENT_DESKTOP = GNOME;   GDMSESSION = gnome
> Graphics Card Info::
> Zoom package arch is 64bit, runing OS arch is x86_64
> AppIconMgr::systemDesktopName log Desktop Name: gnome
> qt.svg: link image0 hasn't been detected!
> qt.svg: :/images/wechat.svg:10:6: Could not resolve property: pattern0
> ExceptionHandler::SendContinueSignalToChild sys_write
> failed:ExceptionHandler::WaitForContinueSignal sys_read failed:Broken pipe
> ExceptionHandler::GenerateDump waitpid failed:Bad file descriptorBad
> file descriptor

1) Pulseaudio issue was in fact different user IDs.
2) After looking at some issues posted for the linux client, it looks
like the qt.svg messages are just noise.

I also noticed some syslog messages that are probably the root cause:

linux: pid 3906 (QDBusConnection): syscall inotify_init1 not implemented
linux: pid 3906 (QDBusConnection): syscall inotify_init not implemented
linux: pid 3919 (QDBusConnection): syscall inotify_init1 not implemented
linux: pid 3919 (QDBusConnection): syscall inotify_init not implemented
linux: pid 3906 (vcdn_thread): syscall inotify_init not implemented
pid 3906 (ProcessThread), jid 0, uid 1001: exited on signal 11 (core dumped)

I need to look more into what these are.  Posting in case someone knows
anything.
signature.asc (application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQQ9+4mhuzHQx7ikjAs846Nm3BBWrAUCXq9ZXgAKCRA846Nm3BBW
rD7IAP9kBRHDW2jg5uEVWfsvuM+4xR+H2yuNTA0wPv0aE5gSVgEAntsgFSRIu7jX
ht696Fz0hZxPSrUxWn2yw+Bi2eQBeAU=
=BdbV
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.