> Is there actually a pulseaudio daemon running?
yup.
> Where?
Not sure what this is supposed to mean.
> Is it managed by systemd?
I dunno how starting it at login is supposed to work.
client.conf:
autospawn = no
Ok this makes absolutely no sense at all. The problem went away when I
took
On Fri, Jan 3, 2020 at 12:16 AM Joshua Hudson wrote:
> > Does `journalctl --user-unit pulseaudio.service` have anything to say?
>
> Says "daemon already running" quite a few times.
>
> > You can set the debug flags on daemon.conf to force it to verbose mode.
>
> Spectacular:
>
> E: [pulseaudio]
> Does `journalctl --user-unit pulseaudio.service` have anything to say?
Says "daemon already running" quite a few times.
> You can set the debug flags on daemon.conf to force it to verbose mode.
Spectacular:
E: [pulseaudio] pid.c: Daemon already running.
E: [pulseaudio] main.c:
Control: tags -1 moreinfo
On Wed, Jan 1, 2020 at 8:39 PM Joshua wrote:
> Package: pulseaudio
> Version: 12.2-4+deb10u1
> Severity: normal
>
> After installing systemd, the following problem appeared in pulseaudio:
>
Please attach the entire client.conf (/etc/pulse and ~/.config/pulse).
>
>
Package: pulseaudio
Version: 12.2-4+deb10u1
Severity: normal
After installing systemd, the following problem appeared in pulseaudio:
The first login after boot launches a non-working pulseaudio. Killing and
restarting pulseaudio results in
a working pulseaudio. It's not a wait for device to
5 matches
Mail list logo