Date: Wed, 6 May 2020 16:05:00 -0700 From: Oleksandr Tymoshenko <gonzo@bluezbox.com> To: Eric McCorkle <eric@metricspace.net> Cc: Austin Shafer <amshafe2@ncsu.edu>, freebsd-hackers@freebsd.org, multimedia@freebsd.org, "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org> Subject: Re: Working on Zoom port Message-ID: <20200506230500.GA96464@bluezbox.com> In-Reply-To: <66ed62a7-7417-a6ca-ff01-045dc837d41d@metricspace.net> References: <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net> <cfd68f02-c84c-0af6-2d8e-a9f4661de04a@nomadlogic.org> <a1353679c97b39acdd8d32d79efb6d79@waitman.net> <76793d13-c7df-c607-6751-19bf02fde4b8@metricspace.net> <df007ac7-5e81-1589-71fd-65c110faed40@metricspace.net> <5d92730b-dad0-974d-f99e-894dcc17af40@metricspace.net> <m2ftcgimuh.fsf@triplebuff.com> <59438393-6608-1afb-7fcd-dbce5a7503f7@metricspace.net> <m2d07kilx7.fsf@triplebuff.com> <66ed62a7-7417-a6ca-ff01-045dc837d41d@metricspace.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric McCorkle (eric@metricspace.net) wrote: > On 5/3/20 8:27 PM, Austin Shafer wrote: > > Eric McCorkle <eric@metricspace.net> writes: > > > >> On 5/3/20 8:07 PM, Austin Shafer wrote: > >>>> 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 > >>> > >>> A while back I tried to map linux's inotify to kqueue in the linuxlator > >>> to solve this problem for steam. It was not very successful. Although it > >>> could handle monitoring single files, it could not do directories which > >>> is how most people seem to use inotify. I wonder why zoom needs this? > >>> > >>> Unfortunately I can't seem to find the patches. If I do I'll let > >>> you know. > >>> > >> > >> Those are syslog messages. The corresponding application log messages > >> look like it's trying to talk through a socket, probably to DBus > > > > Either way, something is trying to use inotify which the linuxlator does not > > support. > > > > Guess I'm dead in the water, then. Oh well, it was worth a shot. Hi Eric, inotify seems to be optional. I was able to join Zoom meeting from the VirtualBox 12.0-RELEASE system. No camera, no audio though, only remote video stream rendering. When I tried to move stuff to my laptop the app started crashing. I think it's probably related to Xorg DRI/DRM because Linux glxgears also segfaults on the laptop but works in the VirtualBox Non-obvious stuff I had to do to unblock app start-up: start session dbus daemon, I did it using dbus-monitor app: nohup dbus-monitor & I also used zoom.sh wrapper to start Zoom app. Had to modify it by changing shell to /usr/local/bin/bash and removing core file Linux-isms. Hope it unblocks your progress with the port. -- gonzo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200506230500.GA96464>