Am Dienstag, 2. August 2022, 01:04:56 CEST schrieb Ramon Fischer:
> Take a look in "/etc/pulse/client.conf".
>
> You can either set "autospawn = yes" or comment it.
>
That did it. For some reason, after the update it was set to no.
Thanks
Alex
Take a look in "/etc/pulse/client.conf".
You can either set "autospawn = yes" or comment it.
"pulseaudio" is automatically started via
"/etc/xdg/autostart/pulseaudio.desktop"; at least in my case.
-Ramon
On 31/07/2022 14:33, Alexander Puchmayr wrote:
Not sure which start script to add it
Same here, pulseaudio daemon is no longer started automatically. Starting it
from a shell (simply call pulseaudio ) and audio works fine again.
Not sure which start script to add it to; .login or .profile are unsuitable
because it would then start it at every login even with ssh).
Alex
Am
On Saturday, 30 July 2022 15:36:35 BST Rich Freeman wrote:
> From:
> https://gitweb.gentoo.org/data/gentoo-news.git/tree/2022-07-29-pipewire-soun
> d-server/2022-07-29-pipewire-sound-server.en.txt
>
> Display-If-Installed: media-video/pipewire
> Display-If-Installed: media-sound/pulseaudio
>
On Sat, Jul 30, 2022 at 10:27 AM Peter Humphrey wrote:
>
> Then I went to my ~amd64 machine and looked for the same news item - and
> there was no sign of anything about either pulse or pipe. This machine has no
> working sound hardware, but even so, how did the news function know not to
> fetch
Hello list,
My amd64 workstation received a news item about pulseaudio and pipewire
today. I did what it recommended to keep pulseaudio because plasma-meta
requires that.
Then I went to my ~amd64 machine and looked for the same news item - and
there was no sign of anything about either pulse
6 matches
Mail list logo
