From owner-freebsd-multimedia@freebsd.org Wed May 6 23:05:12 2020 Return-Path: Delivered-To: freebsd-multimedia@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EB5B22E2141 for ; Wed, 6 May 2020 23:05:12 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 49HXHX4h1kz4L04 for ; Wed, 6 May 2020 23:05:12 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: by mailman.nyi.freebsd.org (Postfix) id 9E8FE2E213E; Wed, 6 May 2020 23:05:12 +0000 (UTC) Delivered-To: multimedia@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9C0902E213D; Wed, 6 May 2020 23:05:12 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49HXHV1fqmz4L03; Wed, 6 May 2020 23:05:09 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92 (FreeBSD)) (envelope-from ) id 1jWT66-000PCK-AQ; Wed, 06 May 2020 16:05:03 -0700 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id 046N51nP096862; Wed, 6 May 2020 16:05:01 -0700 (PDT) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Wed, 6 May 2020 16:05:00 -0700 From: Oleksandr Tymoshenko To: Eric McCorkle Cc: Austin Shafer , freebsd-hackers@freebsd.org, multimedia@freebsd.org, "freebsd-x11@freebsd.org" Subject: Re: Working on Zoom port Message-ID: <20200506230500.GA96464@bluezbox.com> References: <2119d998-b4a1-d72f-342d-0afc3cf3a480@metricspace.net> <76793d13-c7df-c607-6751-19bf02fde4b8@metricspace.net> <5d92730b-dad0-974d-f99e-894dcc17af40@metricspace.net> <59438393-6608-1afb-7fcd-dbce5a7503f7@metricspace.net> <66ed62a7-7417-a6ca-ff01-045dc837d41d@metricspace.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <66ed62a7-7417-a6ca-ff01-045dc837d41d@metricspace.net> X-Operating-System: FreeBSD/11.2-RELEASE-p10 (amd64) User-Agent: Mutt/1.12.1 (2019-06-15) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Eric McCorkle (eric@metricspace.net) wrote: > On 5/3/20 8:27 PM, Austin Shafer wrote: > > Eric McCorkle writes: > > > >> On 5/3/20 8:07 PM, Austin Shafer wrote: > >>>> linux: pi [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Rspamd-Queue-Id: 49HXHV1fqmz4L03 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of gonzo@bluezbox.com designates 45.55.20.155 as permitted sender) smtp.mailfrom=gonzo@bluezbox.com X-Spamd-Result: default: False [-4.72 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; DMARC_NA(0.00)[bluezbox.com]; RCPT_COUNT_FIVE(0.00)[5]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-2.42)[ip: (-8.85), ipnet: 45.55.0.0/19(-4.35), asn: 14061(1.15), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:45.55.0.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2020 23:05:13 -0000 Eric McCorkle (eric@metricspace.net) wrote: > On 5/3/20 8:27 PM, Austin Shafer wrote: > > Eric McCorkle 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