Many forms of invalid server specifications provided via --server or PULSE_SERVER envar do not get flagged as syntax errors. Example: $ pactl -s '*()&#$' list Connection failure: Connection refused Flagging the server spec as invalid would help to avoid user footshoot.
these characters are all valid in a path name, i.e. a unix domain socket specifier
I would argue that most mistyped strings (such as the example given above in the ticket) are invalid AF_UNIX socket specifiers, because they do not begin with '/'. This argument seems to be supported by item #2 from http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/ServerStrings/ and is also consistent with the AF_UNIX socket naming convention here http://www.freedesktop.org/software/systemd/man/systemd.socket.html under the "Options" subsection.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/119.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.