Results 1 to 4 of 4

Thread: pulseaudio won't connect to remote server

  1. #1
    Join Date
    Sep 2006
    Beans
    Hidden!

    pulseaudio won't connect to remote server

    I have pulseaudio set up on my Ubuntu machine, which I want to use as the client, and a Suse box, which I want to use as the server.

    I've tried numerous ways to get pulseaudio on Ubuntu to connect to the other box, but nothing is working. There aren't any errors generated, it simply connects to the local server, apparently without even trying the remote server.

    I've tried using the GUI to set the default server using the format:
    tcpxx.xxx.xxx.xxx:4712
    (I've also tried port 4713, different sites list different defaults, and I'm not sure how to check)
    I've also tried setting the default in /etc/pulse/client.conf

    No matter what I do, when I load the pulseaudio manager through the GUI, it shows a connection to the local server.

    Any ideas?

  2. #2
    Join Date
    May 2006
    Location
    California
    Beans
    30
    Distro
    Ubuntu Karmic Koala (testing)

    Re: pulseaudio won't connect to remote server

    I, too have been having trouble getting pulseaudio to connect to remote servers... however, if you use padevchooser, setup your remote server like so: http://www.pulseaudio.org/wiki/PerfectSetup and make sure the avahi/zeroconf module is installed... padevchooser should see your remote server (and at least spare you writing out the address by hand). That's where *i* am at the moment, but it still refuses to connect...

  3. #3
    Join Date
    Dec 2007
    Beans
    37

    Re: pulseaudio won't connect to remote server

    Does anyone has make this to work?
    I'm also interested ...

  4. #4
    Join Date
    Apr 2008
    Beans
    1

    Re: pulseaudio won't connect to remote server

    I know it has to do with coping .pulse-cookie from the server to the client so the client has authorization to connect or the server needs to be configured to not require authorization.

    Lets see here:
    .pulse-cookie should be located in /var/run/pulse/.pulse-cookie or ~/.pulse-cookie on the server and then should be copied to ~/.pulse-cookie on the client.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •