| 1 |
On Sun, Apr 26, 2020 at 9:23 PM Mark Knecht <markknecht@×××××.com> wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> |
| 5 |
> On Sun, Apr 26, 2020 at 1:06 PM Jorge Almeida <jjalmeida@×××××.com> wrote: |
| 6 |
> > |
| 7 |
|
| 8 |
> Some reading I did about people having problems similar to yours with discord and zoom suggested that some of these aps are compiled to __only__ support pulseaudio and then they supply it if it's not already on the system. Even though you don't build it using a specific portage entry in your world file doesn't mean it's not on your system if it was buried in the zoom/discord code. |
| 9 |
|
| 10 |
Hummm... But then discord would not complain about not being able to |
| 11 |
initialize audio? |
| 12 |
> |
| 13 |
> 1) Run 'pulseaudio' at the command line to check |
| 14 |
There is no such thing (if it were hidden in some app it would not be |
| 15 |
in the PATH, anyway) |
| 16 |
And I regularly check what's cooking, with "ps axf". |
| 17 |
|
| 18 |
|
| 19 |
> Any 'real' pulseaudio build can be configured to not 'autospawn' via it's config files. That way people who don't want it, or think they don't, can have it on the system but run it only when they need it and shut it down when they don't. I did that for awhile. That sort of setup might be more acceptable for your needs and would allow you to build it and manage it yourself. I don't know. Something to consider. On Gentoo I wouldn't be fearful of building it and trying it out. Not sure what flags you'd want to enable or whether you'll end up in some sort of dependency hell as can happen with this sort of stuff on Gentoo. |
| 20 |
|
| 21 |
Yes, stuff to learn, if possible. (But dependency hell is a definite |
| 22 |
possibility, not because Gentoo but due to the mindset that lurks |
| 23 |
beneath pulseaudio & friends) |
| 24 |
> |
| 25 |
Cheers |
| 26 |
|
| 27 |
Jorge |
Archives