It's probable that everyone who uses pulseaudio as installed by Intrepid will experience this bug. The question is whether or not they'll experience the long hang that helps us notice it -- and that is determined by the networking configuration.
It appears to me that users who once had an IPV4-only system and upgraded will avoid the wait for timeout caused by the bug (the alsa-tools still look for the pulseaudio server, but fails to find it much faster). This is because the upgrade script notices the ipv6 section is missing in /etc/hosts and installs one including the "localhost" name in the ::1 line.
Users who manually add the "localhost" hostname to the ::1 line in /etc/hosts also avoid this wait. My guess is that users who disable IPV6 after installing will also avoid this wait for timeout.
@Dove,
It's probable that everyone who uses pulseaudio as installed by Intrepid will experience this bug. The question is whether or not they'll experience the long hang that helps us notice it -- and that is determined by the networking configuration.
It appears to me that users who once had an IPV4-only system and upgraded will avoid the wait for timeout caused by the bug (the alsa-tools still look for the pulseaudio server, but fails to find it much faster). This is because the upgrade script notices the ipv6 section is missing in /etc/hosts and installs one including the "localhost" name in the ::1 line.
Users who manually add the "localhost" hostname to the ::1 line in /etc/hosts also avoid this wait. My guess is that users who disable IPV6 after installing will also avoid this wait for timeout.
Robb Topolski