#785: No or only random connections to PulseAudio server after `pulseaudio -k`.
--------------------------+-------------------------------------------------
Reporter: PaulePanter | Owner: lennart
Type: defect | Status: closed
Milestone: | Component: daemon
Resolution: invalid | Keywords:
--------------------------+-------------------------------------------------
Comment(by coling):
Great. Glad it was ultimately a config problem :)
For your piece of mind (and your/mine/everyones sanity!) I think running
pulseaudio --start will now verify if a default-server is specified (e.g.
via any config mechanism) and if so, it will not start a local PA. This
would not have solved your problem but it would have stopped a local PA
being started at all and thus you would have continually received
connection refused errors from the get go rather than only after killing
and running manually which would probably have been easier to configure.
I'll probably write a little tool that dumps the client credentials so
that we can ask people to run it when they encounter similar problems.
As for the pax11publish, yes I think that warrants a bug report. I just
tested it here:
1. Fresh login, PULSE_SERVER prop is nicely verbose and contains local,
tcp4 and tcp6 connection strings
2. pax11publish -r
3. pax11publish -e
4. Now the PULSE_SERVER prop just says my hostname. Ugg.
--
Ticket URL: <http://pulseaudio.org/ticket/785#comment:5>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server
_______________________________________________
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets
