1 |
On 2020.04.26 18:22, Jorge Almeida wrote: |
2 |
> On Sun, Apr 26, 2020 at 8:28 PM Jack |
3 |
> <ostroffjh@×××××××××××××××××.net> wrote: |
4 |
> > |
5 |
> > On 2020.04.26 15:08, Jorge Almeida wrote: |
6 |
> > [snip....] |
7 |
> |
8 |
> > I run a mostly stable amd64 system with selected ~amd64 packages. I |
9 |
> > use both slack and zoom reasonably often, and have not had any |
10 |
> install |
11 |
> > related problems. (I don't necessarily TRUST either of them, but my |
12 |
> > use of them is for a project with nothing particularly confidential |
13 |
> of |
14 |
> > private.) I'd say if you care enough to bother - start a separate |
15 |
> > thread about why those two fail emerge for you. I seem to have |
16 |
> > recurring problems with audio and/or video, but I'm pretty sure |
17 |
> that is |
18 |
> > hardware and/or system related - not due directly to either slack or |
19 |
> > zoom. |
20 |
> > |
21 |
> I'll see about pulseaudio first, and if discord doesn't work even so |
22 |
> I'll try that. Meanwhile, the ebuilds may change, or even go stable. |
23 |
> Thanks, |
24 |
> |
25 |
> Jorge |
26 |
The slack ebuild might go stable, but the zoom one seems to change too |
27 |
often to last 30 days before an update, so stable seems unlikely. At |
28 |
least I don't think either of them pulls in many (or even any) other |
29 |
unstable packages. |
30 |
|
31 |
Years ago, pulseaudio seemed to have a bad reputation for being really |
32 |
difficult to deal with, but that is no longer the case, so hopefully |
33 |
you'll make progress in that direction. |
34 |
|
35 |
Jack |