From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 92B1C138350 for ; Sun, 26 Apr 2020 19:28:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 899E9E09B0; Sun, 26 Apr 2020 19:28:43 +0000 (UTC) Received: from mail-qt1-f175.google.com (mail-qt1-f175.google.com [209.85.160.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 27589E089E for ; Sun, 26 Apr 2020 19:28:43 +0000 (UTC) Received: by mail-qt1-f175.google.com with SMTP id 71so12574198qtc.12 for ; Sun, 26 Apr 2020 12:28:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:reply-to:subject:to:cc:mime-version :in-reply-to:message-id:content-disposition :content-transfer-encoding; bh=5hiVoba4OGE/DP6VyGQJ4xjKRiUtzegj7NGDjYjGui8=; b=W3qBOuCiiQTg/AzZL9enLX0uZWSMZpjLDm6UDbtJDxxIyPBlsoDIlNto34SLcUqVRu riTgNK4bL1Cz/kajD07wCqh1kPWwdyAx6jj0OEP/XuhUTZp2oAtRHm22229GlVvFqxNO 0QzsJQkrP5/iGQIGtLKVf+9ft92hK3je0Tl+USDevpyx05S/wEQ30IDyqweXcuT/CVQe qHljM0RHGyx0W8mDomlY/M/Lm4gSSetwBwwGKr7HRXXlAAvyEwNeaEjsYkjv3hNctt9u xZ0gcF4zS0ElFr7jcNS9OpaHYI6oqASIK+fJwIMocrYoaITYE0ijQAvp5suHlkRXvQHh +9PA== X-Gm-Message-State: AGi0PuYbDzaRLnIn6ipcJTE9I3aBkPeV1nU7yLY8MU2c85qYpoCYtYUK b71gFY81XDY6cPLQ9KJB88RESweerJo= X-Google-Smtp-Source: APiQypK2k7VzwpcG/vtSRwaOnJ/HwkgqwcNeBmeCGbgsYa4R1dUfZ36fEuIHzWCu8pQs+xryc0/QXQ== X-Received: by 2002:ac8:4f53:: with SMTP id i19mr19768121qtw.195.1587929322273; Sun, 26 Apr 2020 12:28:42 -0700 (PDT) Received: from ffortso9 (c-76-23-130-96.hsd1.ct.comcast.net. [76.23.130.96]) by smtp.gmail.com with ESMTPSA id c124sm8419654qke.13.2020.04.26.12.28.41 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 26 Apr 2020 12:28:41 -0700 (PDT) Date: Sun, 26 Apr 2020 15:28:40 -0400 From: Jack Subject: problems with slack and zoom: Was: [gentoo-user] ALSA wizard... To: gentoo-user@lists.gentoo.org Cc: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: X-Mailer: Balsa 2.6.0 Message-Id: Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 5289b4c6-dc41-47b3-ad3b-4d64f2746e7b X-Archives-Hash: fb8eb7ed33404e5c97e1d9829e3e7779 On 2020.04.26 15:08, Jorge Almeida wrote: [snip....] > I'll keep searching for some audio chat package that works. mumble =20 > seems promising, but it requires an available server. zoom (which =20 > most people @work use) doesn't emerge. slack does emerge and vomits a =20 > totally unresponsive window (well, not *totally* unresponsive: Ctrl+Q =20 > works :)) >=20 I run a mostly stable amd64 system with selected ~amd64 packages. I =20 use both slack and zoom reasonably often, and have not had any install =20 related problems. (I don't necessarily TRUST either of them, but my =20 use of them is for a project with nothing particularly confidential of =20 private.) I'd say if you care enough to bother - start a separate =20 thread about why those two fail emerge for you. I seem to have =20 recurring problems with audio and/or video, but I'm pretty sure that is =20 hardware and/or system related - not due directly to either slack or =20 zoom. Jack