| Summary: | Refuses to --start due to "User configured server" | ||
|---|---|---|---|
| Product: | PulseAudio | Reporter: | mk |
| Component: | daemon | Assignee: | pulseaudio-bugs |
| Status: | RESOLVED MOVED | QA Contact: | pulseaudio-bugs |
| Severity: | normal | ||
| Priority: | medium | CC: | lennart |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
I don't see why this is a bug. You've instructed all your clients to talk to a different PA server on the network, so we're basically erroring out if you try to spawn a local server, saying that this is pointless, since clients will connect to your remote server. This is done on --start since that's the way PA is generally started by your desktop environment or whatever is autospawning it. Okay, my misconception. You realize this distinction is not made anywhere in a man page or in the online documentation? Because I have had trouble getting the connection to work, I had not noticed that I did not have to start pulseaudio on the sender side for it to work...but que sera sera I guess. That is true, our documentation can always be improved. Suggestions on where you would look for this first (or a patch, if you're up to it ;) ) are welcome. I'm about to leave on vacation for a week, but I'd be happy to think about a patch for the .conf/.pa man pages. I also think it would make a straightforward FAQ question; I suppose my experience is atypical in that while I'm a long term linux user, up to now I've always removed pulseaudio because it did not serve any purpose for me. I.e., I was starting from a point where it did not exist on the system. You may be interested in this: http://raspberrypi.stackexchange.com/questions/8621/how-to-set-up-a-pulseaudio-sink/8664#8664 (I'm user goldilocks) which summarizes the experience. Do you have anyone specific I can contact WRT the FAQ/man patches? I am on pulseaudio-discuss, but a question regarding this issue was completely ignored there, and the person who later helped me on #pulseaudio irc was confused and did not make the (presumably obvious) connection you did above. So I would rather skip those routes. (In reply to comment #4) > I'm about to leave on vacation for a week, but I'd be happy to think about a > patch for the .conf/.pa man pages. I also think it would make a > straightforward FAQ question; I suppose my experience is atypical in that > while I'm a long term linux user, up to now I've always removed pulseaudio > because it did not serve any purpose for me. I.e., I was starting from a > point where it did not exist on the system. You may be interested in this: > http://raspberrypi.stackexchange.com/questions/8621/how-to-set-up-a- > pulseaudio-sink/8664#8664 (I'm user goldilocks) which summarizes the > experience. Nice. Our idea has been to have the tunnel sink automatically set up for you using avahi for autodiscovery. Guessing that's not set up on the rpi at the moment. We've also got a GSoC project looking at redoing tunnel-sink better, so that's something to look forward to. > Do you have anyone specific I can contact WRT the FAQ/man patches? I am on > pulseaudio-discuss, but a question regarding this issue was completely > ignored there, and the person who later helped me on #pulseaudio irc was > confused and did not make the (presumably obvious) connection you did above. > So I would rather skip those routes. Just post the patches here. We're not always able to spend the time we'd like on lists/irc/bugs, but we do at least try to do a bug triage between releases to get the bug list cleaned up. -- 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/103. |
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.
Eg: > pulseaudio --start -vvvv N: [pulseaudio] main.c: User-configured server at tcp:192.168.2.13:4713, refusing to start/autospawn. And no further information in syslog either. Run in the foreground (i.e., without --start), it works fine. I found a recommendation somewhere, vis. pax11publish -d pax11publish -r Might help, and/or deleting the contents of ~/.pulse, but none of that solves the problem. A normal user in X can't run it as a demon with: default-server = tcp:192.168.2.13.4713 in /etc/client.conf. This is version 1.1 on fedora 17.