Results 1 to 9 of 9

Thread: PA Volume Control - Connection Failed, Connection refused

  1. #1

    Default PA Volume Control - Connection Failed, Connection refused

    When I go into Pulse Audio Volume control, It says "Connection Failed, Connection refused"

    What would cause this?

    What tests should I run to tell you all what my system is doing?

    How do I re-establish the connection to Pulse Audio?

    I'm running SuSE 11.4 and hwinfo --sound gives me this:
    Code:
    44: PCI 706.0: 0401 Multimedia audio controller                 
      [Created at pci.318]
      Unique ID: 2+Ni.trsEqNGuZ00
      Parent ID: 37TO.ryKLPOPKUP8
      SysFS ID: /devices/pci0000:00/0000:00:10.0/0000:07:06.0
      SysFS BusID: 0000:07:06.0
      Hardware Class: sound
      Model: "Creative SB0090 Audigy Player"
      Vendor: pci 0x1102 "Creative Labs"
      Device: pci 0x0004 "SB Audigy"
      SubVendor: pci 0x1102 "Creative Labs"
      SubDevice: pci 0x0051 "SB0090 Audigy Player"
      Revision: 0x03
      Driver: "EMU10K1_Audigy"
      Driver Modules: "snd_emu10k1"
      I/O Ports: 0xec00-0xec1f (rw)
      IRQ: 16 (20616 events)
      Module Alias: "pci:v00001102d00000004sv00001102sd00000051bc04sc01i00"
      Driver Info #0:
        Driver Status: snd_emu10k1 is active
        Driver Activation Cmd: "modprobe snd_emu10k1"
      Config Status: cfg=yes, avail=yes, need=no, active=unknown
      Attached to: #36 (PCI bridge)

  2. #2

    Default Re: PA Volume Control - Connection Failed, Connection refused

    P.S. I've just tried
    Code:
    ffmpeg -f alsa -ac 2 -i pulse -f x11grab -r 15 -s 1280x972 -i  :0.0 -acodec pcm_s16le -vcodec libx264 -preset ultrafast -threads  0 soundtesting-wah.avi
    and got this message:
    Code:
    ffmpeg version 0.9.1, Copyright (c) 2000-2012 the FFmpeg developers
      built on Jan  6 2012 11:01:08 with gcc 4.5.1 20101208 [gcc-4_5-branch revision 167585]
      configuration: --shlibdir=/usr/lib64 --prefix=/usr --mandir=/usr/share/man --libdir=/usr/lib64 --enable-shared --disable-static --enable-libmp3lame --enable-libvorbis --enable-libtheora --enable-libspeex --enable-libxvid --enable-postproc --enable-gpl --enable-x11grab --extra-cflags='-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fPIC -I/usr/include/gsm' --enable-debug --disable-stripping --enable-libgsm --enable-libschroedinger --enable-libdirac --enable-avfilter --enable-libvpx --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libx264 --enable-libdc1394 --enable-pthreads --enable-librtmp
      libavutil    51. 32. 0 / 51. 32. 0
      libavcodec   53. 42. 4 / 53. 42. 4
      libavformat  53. 24. 2 / 53. 24. 2
      libavdevice  53.  4. 0 / 53.  4. 0
      libavfilter   2. 53. 0 /  2. 53. 0
      libswscale    2.  1. 0 /  2.  1. 0
      libpostproc  51.  2. 0 / 51.  2. 0
    ALSA lib pulse.c:229:(pulse_connect) PulseAudio: Unable to connect: Connection refused
    
    [alsa @ 0x635a80] cannot open audio device pulse (Connection refused)
    pulse: Input/output error
    What I did find was that I could capture sound using KRecord. But that does not help me with the above problem and I've also found out that Audacious has been affected too. When I try to play music, it gives me the following message: "No suitable mixer element found. snd_pcm-open failed: connection refused"

    When I click on a song to be played from within the Dolphin file manger, I get this message that the Audio playback device (and it names the device) does not work and then it says it is falling back on... and the device named has the exact same name.




    What do I do? Can this be fixed using Yast?

  3. #3
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,490
    Blog Entries
    37

    Default Re: PA Volume Control - Connection Failed, Connection refused

    Is there any chance that an underlying application has crashed ? Is this behaviour still present after a reboot (that re-initializes the applications and underlying processes ? )

  4. #4

    Default Re: PA Volume Control - Connection Failed, Connection refused

    Yes, this is the message that shows whenever I boot up now:


    I answer "No" because I don't know if anything would work at all if I answered "yes".

    And when I go into Manage Devices (Phonon):



    That message, refers to the greyed out driver.

    Could something like simply plugging in a microphone cause a 2nd driver to be loaded?

  5. #5
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,490
    Blog Entries
    37

    Default Re: PA Volume Control - Connection Failed, Connection refused

    Sorry - I don't know whats wrong.

    The first post with 'hwinfo --sound' is meaningless to me in terms of its relevance. Maybe someone who understands the reason for your posting that 'hwinfo --sound' info can reply. I always recommend running the alsa-info script to provide information on the hardware and software configuration of one's audio. Or perhaps you could teach me as to 'hwinfo --sound' relevance ? As I have always scratched my head when looking at it. Note I am not saying it is not useful. I am just saying it has never helped me sort someone's audio problems.

    I see you posted some kde menu's but I have no idea as to the kde version - and that could be important. Myself I am still using openSUSE-12.1 on KDE. Can't say I have ever seen such a problem.

    Reference your ignoring that error message. I note the software assessment is it should be deleted " ... KDE thinks could be removed ... ". Why do you think you will not be able to get sound back after deleting it ?
    Last edited by oldcpu; 28-Oct-2012 at 14:52.

  6. #6
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,490
    Blog Entries
    37

    Default Re: PA Volume Control - Connection Failed, Connection refused

    Have you tried running the script to obtain more information ?
    Code:
    /usr/sbin/alsa-info.sh
    It has a LOT of useful information, from information on the running status of pulse audio, to one's kernel version, openSUSE version, mixer settings, hardware ... etc .... so as to provide a more complete picture. It does not , thou, have desktop related information.

  7. #7

    Default Re: PA Volume Control - Connection Failed, Connection refused

    sorry I could not reply eariler. Hurricane Sandy had other plans for my area.
    I posted the hwinfo --sound because it tells you the sound card brand and driver info.
    well now i can't even get into the computer anymore. when we finally got the power back after 4 1/2 days, I got this code of beeps from the mother board, 1 long and 3 short and my husband looked it up and found that it means that the graphics card is busted. So now, I probably will be forced (by circumstances) to upgrade the system because I probably won't be able to get a driver for a new card for Suse 11.4.

  8. #8
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,490
    Blog Entries
    37

    Default Re: PA Volume Control - Connection Failed, Connection refused

    Sorry to read of the computer damage, but glad to read that you survived Sandy. Take care !

  9. #9

    Default Re: PA Volume Control - Connection Failed, Connection refused

    Quote Originally Posted by gymnart View Post
    well now i can't even get into the computer anymore. when we finally got the power back after 4 1/2 days, I got this code of beeps from the mother board, 1 long and 3 short and my husband looked it up and found that it means that the graphics card is busted. So now, I probably will be forced (by circumstances) to upgrade the system because I probably won't be able to get a driver for a new card for Suse 11.4.
    Was that as a result of an electrical surge?

    One thing you can try though, before going out and getting a new system, is to completely unplug the current one from power for a while and let the capacitance drain ... I don't know, try, 24 hours .... then test it again. Another quick test, if you can do the swap, is to try a different PSU in the system instead.

    Best of luck

Tags for this Thread

Posting Permissions

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