Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#775714: pavucontrol: Connection to PulseAudio failed. Automatic retry in 5s
136 views
Skip to first unread message
David Christensen
Jan 19, 2015, 12:20:02 AM1/19/15
to
Package: pavucontrol
Version: 1.0-1
Severity: important
Dear Maintainer,
I just installed pavucontrol. Using Xfce and choosing rodent ->
Multimedia -> PulseAudio Volume Control, I get a pop-up:
Volume Control
Connection to PulseAudio failed. Automatic retry in 5s
In this case this is likely because PULSE_SERVER in the Environment/X11 Root Windows Properties
or default-server in client.conf is misconfigured.
This situation can also arrise when PulseAudio crashed and left stale details in the X11 Root Window.
If this is the case, then PulseAudio should autospawn again, or if this not configured you should
run start-pulseaudio-x11 manually.
I have not modified /etc/pulse/client.conf:
# egrep -v '^(#|$)' /etc/pulse/client.conf
; default-sink =
; default-source =
; default-server =
; default-dbus-server =
; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog
; cookie-file =
; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB
; auto-connect-localhost = no
; auto-connect-display = no
I am unable to locate start-pulseaudio-x11:
# /etc/cron.daily/mlocate
# locate start-pulseaudio-x11
Please advise.
TIA,
David
-- System Information:
Debian Release: 7.8
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages pavucontrol depends on:
ii libatk1.0-0 2.4.0-2
ii libatkmm-1.6-1 2.22.6-1
ii libc6 2.13-38+deb7u6
ii libcairo-gobject2 1.12.2-3
ii libcairo2 1.12.2-3
ii libcairomm-1.0-1 1.10.0-1
ii libcanberra-gtk3-0 0.28-6
ii libcanberra0 0.28-6
ii libgcc1 1:4.7.2-5
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.33.12+really2.32.4-5
ii libglibmm-2.4-1c2a 2.32.1-1
ii libgtk-3-0 3.4.2-7
ii libgtkmm-3.0-1 3.4.2-1
ii libpango1.0-0 1.30.0-1
ii libpangomm-1.4-1 2.28.4-1
ii libpulse-mainloop-glib0 2.0-6.1
ii libpulse0 2.0-6.1
ii libsigc++-2.0-0c2a 2.2.10-0.2
ii libstdc++6 4.7.2-5
pavucontrol recommends no packages.
pavucontrol suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Version: 1.0-1
Severity: important
Dear Maintainer,
I just installed pavucontrol. Using Xfce and choosing rodent ->
Multimedia -> PulseAudio Volume Control, I get a pop-up:
Volume Control
Connection to PulseAudio failed. Automatic retry in 5s
In this case this is likely because PULSE_SERVER in the Environment/X11 Root Windows Properties
or default-server in client.conf is misconfigured.
This situation can also arrise when PulseAudio crashed and left stale details in the X11 Root Window.
If this is the case, then PulseAudio should autospawn again, or if this not configured you should
run start-pulseaudio-x11 manually.
I have not modified /etc/pulse/client.conf:
# egrep -v '^(#|$)' /etc/pulse/client.conf
; default-sink =
; default-source =
; default-server =
; default-dbus-server =
; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog
; cookie-file =
; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB
; auto-connect-localhost = no
; auto-connect-display = no
I am unable to locate start-pulseaudio-x11:
# /etc/cron.daily/mlocate
# locate start-pulseaudio-x11
Please advise.
TIA,
David
-- System Information:
Debian Release: 7.8
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages pavucontrol depends on:
ii libatk1.0-0 2.4.0-2
ii libatkmm-1.6-1 2.22.6-1
ii libc6 2.13-38+deb7u6
ii libcairo-gobject2 1.12.2-3
ii libcairo2 1.12.2-3
ii libcairomm-1.0-1 1.10.0-1
ii libcanberra-gtk3-0 0.28-6
ii libcanberra0 0.28-6
ii libgcc1 1:4.7.2-5
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.33.12+really2.32.4-5
ii libglibmm-2.4-1c2a 2.32.1-1
ii libgtk-3-0 3.4.2-7
ii libgtkmm-3.0-1 3.4.2-1
ii libpango1.0-0 1.30.0-1
ii libpangomm-1.4-1 2.28.4-1
ii libpulse-mainloop-glib0 2.0-6.1
ii libpulse0 2.0-6.1
ii libsigc++-2.0-0c2a 2.2.10-0.2
ii libstdc++6 4.7.2-5
pavucontrol recommends no packages.
pavucontrol suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
David Christensen
Jan 19, 2015, 2:30:03 PM1/19/15
to
On 01/19/2015 05:21 AM, Debian Bug Tracking System wrote:
> The problem is that you do not have pulseaudio installed. Pavucontrol
> in Wheezy is missing the Recommends on pulseaudio, which is why you
> did not get it installed automatically (this has been fixed since in
> the testing distribution).
>
> Please install pulseaudio and then pavucontrol should work.
Thanks for the reply. I installed pulseaudio:
The following extra packages will be installed:
libasound2-plugins libsystemd-daemon0 libwebrtc-audio-processing-0
Suggested packages:
pulseaudio-utils pavumeter paman paprefs
Recommended packages:
pulseaudio-module-x11 gstreamer0.10-pulseaudio rtkit
The following NEW packages will be installed:
libasound2-plugins libsystemd-daemon0 libwebrtc-audio-processing-0
pulseaudio
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 1094 kB of archives.
After this operation, 5096 kB of additional disk space will be used.
Get:1 http://approx/debian/ wheezy/main libasound2-plugins amd64
1.0.25-2 [91.4 kB]
Get:2 http://approx/debian/ wheezy/main libsystemd-daemon0 amd64
44-11+deb7u4 [14.9 kB]
Get:3 http://approx/debian/ wheezy/main libwebrtc-audio-processing-0
amd64 0.1-2 [119 kB]
Get:4 http://approx/debian/ wheezy/main pulseaudio amd64 2.0-6.1 [868 kB]
Fetched 1094 kB in 10s (109 kB/s)
Selecting previously unselected package libasound2-plugins:amd64.
(Reading database ... 134259 files and directories currently installed.)
Unpacking libasound2-plugins:amd64 (from
.../libasound2-plugins_1.0.25-2_amd64.deb) ...
Selecting previously unselected package libsystemd-daemon0:amd64.
Unpacking libsystemd-daemon0:amd64 (from
.../libsystemd-daemon0_44-11+deb7u4_amd64.deb) ...
Selecting previously unselected package libwebrtc-audio-processing-0:amd64.
Unpacking libwebrtc-audio-processing-0:amd64 (from
.../libwebrtc-audio-processing-0_0.1-2_amd64.deb) ...
Selecting previously unselected package pulseaudio.
Unpacking pulseaudio (from .../pulseaudio_2.0-6.1_amd64.deb) ...
Processing triggers for man-db ...
Setting up libasound2-plugins:amd64 (1.0.25-2) ...
Setting up libsystemd-daemon0:amd64 (44-11+deb7u4) ...
Setting up libwebrtc-audio-processing-0:amd64 (0.1-2) ...
Setting up pulseaudio (2.0-6.1) ...
Adding user pulse to group audio
[warn] PulseAudio configured for per-user sessions ... (warning).
Pulse Audio Volume Control now works. :-)
A while back, I wanted to build a real-time kernel for audio work.
apt-get was pulling in ~700 MB of files -- a huge tree of documentation
and documentation processors. Then I learned about the
--no-install-recommends option, and the download became orders of
magnitude smaller. I consider it a bug that apt-get installs
recommended packages by default, and almost always use
--no-install-recommends.
In addition to "recommends" and "suggests", Apt appears to have the
concept of "requires" (for example, pulseaudio seems to require
libasound2-plugins, libsystemd-daemon0, and
libwebrtc-audio-processing-0, as demonstrated above). So, pavucontrol
should require pulseaudio. The bug tracking system indicates that the
problem is fixed in Testing (Jessie). Will it be fixed in Stable (Wheezy)?
David
> The problem is that you do not have pulseaudio installed. Pavucontrol
> in Wheezy is missing the Recommends on pulseaudio, which is why you
> did not get it installed automatically (this has been fixed since in
> the testing distribution).
>
> Please install pulseaudio and then pavucontrol should work.
Thanks for the reply. I installed pulseaudio:
The following extra packages will be installed:
libasound2-plugins libsystemd-daemon0 libwebrtc-audio-processing-0
Suggested packages:
pulseaudio-utils pavumeter paman paprefs
Recommended packages:
pulseaudio-module-x11 gstreamer0.10-pulseaudio rtkit
The following NEW packages will be installed:
libasound2-plugins libsystemd-daemon0 libwebrtc-audio-processing-0
pulseaudio
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 1094 kB of archives.
After this operation, 5096 kB of additional disk space will be used.
Get:1 http://approx/debian/ wheezy/main libasound2-plugins amd64
1.0.25-2 [91.4 kB]
Get:2 http://approx/debian/ wheezy/main libsystemd-daemon0 amd64
44-11+deb7u4 [14.9 kB]
Get:3 http://approx/debian/ wheezy/main libwebrtc-audio-processing-0
amd64 0.1-2 [119 kB]
Get:4 http://approx/debian/ wheezy/main pulseaudio amd64 2.0-6.1 [868 kB]
Fetched 1094 kB in 10s (109 kB/s)
Selecting previously unselected package libasound2-plugins:amd64.
(Reading database ... 134259 files and directories currently installed.)
Unpacking libasound2-plugins:amd64 (from
.../libasound2-plugins_1.0.25-2_amd64.deb) ...
Selecting previously unselected package libsystemd-daemon0:amd64.
Unpacking libsystemd-daemon0:amd64 (from
.../libsystemd-daemon0_44-11+deb7u4_amd64.deb) ...
Selecting previously unselected package libwebrtc-audio-processing-0:amd64.
Unpacking libwebrtc-audio-processing-0:amd64 (from
.../libwebrtc-audio-processing-0_0.1-2_amd64.deb) ...
Selecting previously unselected package pulseaudio.
Unpacking pulseaudio (from .../pulseaudio_2.0-6.1_amd64.deb) ...
Processing triggers for man-db ...
Setting up libasound2-plugins:amd64 (1.0.25-2) ...
Setting up libsystemd-daemon0:amd64 (44-11+deb7u4) ...
Setting up libwebrtc-audio-processing-0:amd64 (0.1-2) ...
Setting up pulseaudio (2.0-6.1) ...
Adding user pulse to group audio
[warn] PulseAudio configured for per-user sessions ... (warning).
Pulse Audio Volume Control now works. :-)
A while back, I wanted to build a real-time kernel for audio work.
apt-get was pulling in ~700 MB of files -- a huge tree of documentation
and documentation processors. Then I learned about the
--no-install-recommends option, and the download became orders of
magnitude smaller. I consider it a bug that apt-get installs
recommended packages by default, and almost always use
--no-install-recommends.
In addition to "recommends" and "suggests", Apt appears to have the
concept of "requires" (for example, pulseaudio seems to require
libasound2-plugins, libsystemd-daemon0, and
libwebrtc-audio-processing-0, as demonstrated above). So, pavucontrol
should require pulseaudio. The bug tracking system indicates that the
problem is fixed in Testing (Jessie). Will it be fixed in Stable (Wheezy)?
David
Felipe Sateler
Jan 20, 2015, 1:10:02 PM1/20/15
to
>
> A while back, I wanted to build a real-time kernel for audio work. apt-get
> was pulling in ~700 MB of files -- a huge tree of documentation and
> documentation processors. Then I learned about the --no-install-recommends
> option, and the download became orders of magnitude smaller. I consider it
> a bug that apt-get installs recommended packages by default, and almost
> always use --no-install-recommends.
>
always, installed together. Not installing them may leave your system
not working as intended.
If some Recommends is unwarranted, please file bugs against the
respective packages.
>
> In addition to "recommends" and "suggests", Apt appears to have the concept
> of "requires" (for example, pulseaudio seems to require libasound2-plugins,
> libsystemd-daemon0, and libwebrtc-audio-processing-0, as demonstrated
> above). So, pavucontrol should require pulseaudio.
more than willing to work with a remote server if so instructed, so a
hard dependency is not required or necessary.
> The bug tracking system
> indicates that the problem is fixed in Testing (Jessie). Will it be fixed
> in Stable (Wheezy)?
Currently Jessie is in freeze, and should be released soon (for some
values of soon).
--
Saludos,
Felipe Sateler
0 new messages