[Desktop-packages] [Bug 411688]

[Tanu Kaskinen]

(In reply to freedesktop from comment #17)
> Lowering the rate is possibly not a good idea as it results in worse
> quality. The format is by default "s16be" about which I have no idea what a
> different format would help. I do not know if the data can somehow be
> compress further, because this would definitely be an idea, but I dont know
> the procols internal.

The data can certainly be compressed. I don't know if you've ever
compared the sizes of mp3 and wav files. Typical compressed audio, when
using a lossy codec, requires perhaps one tenth of the bandwidth that
uncompressed audio requires, without too much effect on the audio
quality.

> So the only left option is to solve the routing. For my personal setup there
> is no way to fix this on the router side, so the sender pulse module needs
> to take care of it. Using an ip as destination works perfectly and would be
> an option to use (which should be added to paprefs). However I tried that
> the last days and due to dhcp my receiver always gets a new IP and using
> hostnames would be a better idea.
> 
> But the module does not seem to support hostnames. So I am wondering if this
> could be fixed quite simple or needs a whole more work to do.

Changing module-rtp-send to support hostnames doesn't sound terribly
complicated.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/411688

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Arch Linux:
  Unknown
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
  

[Desktop-packages] [Bug 411688]

[Tanu Kaskinen]

To my knowledge RTP can carry pretty much any format. You said on the
mailing list that you want to use Kodi to receive the stream, and I
don't know what Kodi supports, but I would guess that it supports many
formats.

Don't get too excited about compressed audio, though. I'm not
volunteering to implement it, and it's probably pretty complicated to
integrate to PulseAudio.

In case someone is willing to take this task, the current "plan" (if you
can call it a plan - it's all very fuzzy at the moment) is to use
gstreamer to deal with the codecs, but in any case, please bring this
topic up on the mailing list before spending too much time implementing
it, so that there's an agreement about the design.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/411688

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Arch Linux:
  Unknown
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d16 4000 0111 2d66 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f12f 800a ee95
0x0020:  0071 b240 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 

[Desktop-packages] [Bug 411688]

[Tanu Kaskinen]

*** Bug 98649 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/411688

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Arch Linux:
  Unknown
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d16 4000 0111 2d66 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f12f 800a ee95
0x0020:  0071 b240 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d17 4000 0111 2d65 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 efee 800a ee96
0x0020:  0071 b380 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d18 4000 0111 2d64 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 eead 800a 

[Desktop-packages] [Bug 411688]

[Tanu Kaskinen]

Sending a wav file means a TCP connection between two computers. TCP
connections are the most common type of traffic, and the hardware is
optimized accordingly. UDP multicast is different, and apparently
network hardware is not necessarily as efficient with processing that
protocol. Comment #9 seems to suggest that the wifi specification itself
forces multicast to be inefficient, so it's not necessarily just the
hardware's fault.

Starting from PA version 5.0, module-rtp-send should not generate
traffic when nothing is playing (it can still be configured to play
silence, but paprefs doesn't configure the module that way). If you
observe different behaviour, please file a new bug and attach the output
of "pactl list".

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/411688

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Arch Linux:
  Unknown
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d16 4000 0111 2d66 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f12f 800a ee95
0x0020:  0071 b240 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.590645 IP (tos 0x10, ttl 

[Desktop-packages] [Bug 411688]

[Tanu Kaskinen]

I read through the comments, and to me it looks like module-rtp-send
doesn't have any flooding bug. The data rate of PCM audio is what it is,
and the network hardware isn't always able to handle it. Multicast RTP
is not enabled by default. If the user enables it, I don't know what we
could possibly do to not "flood" the network.

Since this is a common problem for people, there is certainly room for
improvement in the UI and documentation so that users don't get so
surprised when things don't work.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/411688

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Arch Linux:
  Unknown
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d16 4000 0111 2d66 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f12f 800a ee95
0x0020:  0071 b240 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d17 4000 0111 2d65 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 

[Desktop-packages] [Bug 411688]

[Tanu Kaskinen]

Adding to my previous comment: it could be argued that the bug is that
we transmit PCM audio instead of compressed audio. Adding support for
compressed audio should help with the network stress. Does anyone
volunteer to implement this?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/411688

Title:
  pulseaudio floods network with multicast packets

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Arch Linux:
  Unknown
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  Since a karmic update last week, when pulseaudio is running it floods
  the network with multicast packets, to the point where the wireless
  interface I'm using is so flooded that no other network traffic can be
  transfered.

  Here is a snippet of tcpdump -i wlan 0 -n:
  ---8<---
  01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d0f 4000 0111 2d6d 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e
0x0020:  0071 a980 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d10 4000 0111 2d6c 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f
0x0020:  0071 aac0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d11 4000 0111 2d6b 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f774 800a ee90
0x0020:  0071 ac00 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d12 4000 0111 2d6a 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f633 800a ee91
0x0020:  0071 ad40 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d13 4000 0111 2d69 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f4f2 800a ee92
0x0020:  0071 ae80 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d14 4000 0111 2d68 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f3b1 800a ee93
0x0020:  0071 afc0 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d15 4000 0111 2d67 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f270 800a ee94
0x0020:  0071 b100 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d16 4000 0111 2d66 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 f12f 800a ee95
0x0020:  0071 b240 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto 
UDP (17), length 1320)
  10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292
0x:  4510 0528 5d17 4000 0111 2d65 0a00 0001
0x0010:  e000 0038 b0b0 b6dc 0514 efee 800a ee96
0x0020:  0071 b380 ed51 a42b    
0x0030:         
0x0040:       
  01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto 
UDP (17), length 

[Desktop-packages] [Bug 1390474]

[Tanu Kaskinen]

The log shows that you're not using module-udev-detect. I don't know if
that's why things stopped working, but that would anyway be the first
thing to fix. Debian changed the packaging so that "pulseaudio-module-
udev" is now a separate package. You have probably disabled automatic
installation of recommended packages, because by default that package
should get installed automatically.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1390474

Title:
  "Volume element PCM has 6 channels. That's too much!" - PA doesn't
  support elements with more than two channels

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error "Volume element PCM has 6 channels. That's too much! I can't handle 
that!"  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1390474/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

(In reply to Eugene Crosser from comment #25)
> It happens when audio control application running and not running likewise,
> but desktop's audio widget in the panel is indeed running (Cinnamon and
> Unity, same manifestations). It is possible that this audio widget is indeed
> the culprit.

It's possible, but I don't think it's likely.

Can you attach a log file that shows what happens when you start with
analog output selected and headphones plugged in, and then unplug them
and plug them back in? Instructions for getting the log:
https://wiki.ubuntu.com/PulseAudio/Log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

Do you happen to have the audio settings application open? If you do, it
can mess up the device selection:
https://bugzilla.gnome.org/show_bug.cgi?id=762932

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

(In reply to flat from comment #40)
> Same issue on xfce4, so it's not budgie.

It certainly was Budgie according to the log. Maybe xfce4 has a similar
bug in its volume control thingy.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

Sorry for the long delay, I have trouble keeping up with all email...

(In reply to flat from comment #39)
> Created attachment 129322 [details]
> pulse audio verbose log with
> 0001-card-log-the-reason-for-profile-changes.patch 10.0
> 
> Sorry it took a couple days for it to happen again. Guess it helps when you
> compile to actually apply the patch... haha. Here's a log from it switching
> between digital and normal, even after I set it to the correct
> configurations it seems to switch. Looking through the log I think it might
> have to do with budgie-panel, but I'm not sure.

Yes, "Budgie Volume Control" changes the profile to digital.

> Also got another crash so
> that's the first log. Second log starts on line 4424

It's not a crash, it's a failure to start the daemon. module-esound-
protocol-unix can't setup itself, because the socket it needs is
reserved by some other process (probably another pulseaudio instance).
I'm not sure why this happens, but you can safely remove module-esound-
protocol-unix from /etc/pulse/default.pa. It's extremely unlikely that
you have any applications that still use esound.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

Created attachment 129226
0001-card-log-the-reason-for-profile-changes.patch (for 10.0)

Here's the updated patch.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

The new log doesn't seem to have the patch applied. Can you try again?
You can check that pulseaudio is running with the patch by searching the
log for messages that contain "XXX" that are printed whenever the card
profile changes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

Created attachment 129175
0001-card-log-the-reason-for-profile-changes.patch

Here's the patch. It's written against the git master branch. If you
need it for some other PulseAudio version, let me know and I'll rebase
it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

The log doesn't match your problem description. The digital profile is
not activated at all. The log shows switching between headphones and
lineout in 2.1 mode. You wanted to use 5.1, so is your problem actually
that you get 2.1 audio instead of 5.1?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

(In reply to flat from comment #34)
> Created attachment 129184 [details]
> pulse verbose log with 0001-card-log-the-reason-for-profile-changes.patch
> 
> So interestingly enough I can't reproduce the issue using git master.

The first log with the crash shows a switch to the digital profile.
Unfortunately, the crash happens before the log message I added is
printed.

The first log shows four "audio-volume-change" sounds being played in
quick succession during the crash. The volume changes are initiated by
gnome-settings-daemon. Did you change the volume manually while
disconnecting the headphones, or is this something that gnome-settings-
daemon does automatically?

> Attached are two logs as one attachment. The second log starts at line 5308
> (Didn't want to spam attachments). The first log shows pulse crashing upon
> disconnecting the headphones. The second log shows pulse switching between
> 5.1-stereo and Analog Stereo working fine. If you rebase the patch on 10.0 I
> can try it again to see what was going on. Version 10.0 is the current
> version from Arch Linux's repos. I assume a commit since then must have
> fixed something either intentionally or unintentionally.

I don't think it's fixed in master, but I can anyway make a patch for
10.0. I'll change it so that the profile change reason is printed in an
earlier phase. I'll also add some logging in an attempt to make it
easier to track down the reason for the crash if it happens again.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

Thanks, the log is interesting. At line 5943 the headphones are plugged
in. Pulseaudio then decides to switch from the 5.1 profile to the analog
stereo profile, as expected. After switching the profile, however,
pulseaudio decides to immediately switch to digital output instead.
Unfortunately the log doesn't show why this happens.

If I write a patch that adds better logging, will you be able to apply
and test it? Here are some instructions for building and installing
pulseaudio from source:
https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/Developer/PulseAudioFromGit/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

*** Bug 96237 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1521987]

[Tanu Kaskinen]

I believe PulseAudio 9.0 will handle your use case well. Please report
back if it doesn't.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1521987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1773167]

[Tanu Kaskinen]

Here's information about submitting alsa bugs:
http://alsa-project.org/main/index.php/Bug_Tracking

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1773167

Title:
  [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100%
  of a single CPU core

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  On a krez ninja 1103 laptop audio is not working; pulseaudio consumes
  100% of a single CPU core. Pulseaudio log atached.

  According to perf, most CPU is consumed at __memset_erms.

  Below is the GDB stacktrace of pulseaudio.

  # gdb -p 1009 -batch -eval-command="thread apply all bt"
  [New LWP 1028]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, 
expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  205   ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.

  Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)):
  #0  0x7fe2ab063339 in _IO_str_init_static_internal 
(sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", 
size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36
  #1  0x7fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", 
maxlen=, flags=1, slen=, format=0x7fe2ac698e8d 
"%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62
  #2  0x7fe2ac6601ca in pa_vsnprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #3  0x7fe2ac660366 in pa_snprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac66bda8 in pa_log_levelv_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #5  0x7fe2ac66b655 in pa_log_level_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #6  0x7fe2a52b36ae in ?? () from 
/usr/lib/pulse-11.1/modules/libalsa-util.so
  #7  0x7fe2ac68c2a8 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #8  0x7fe2abb756db in start_thread (arg=0x7fe2a7458700) at 
pthread_create.c:463
  #9  0x7fe2ab0f488f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)):
  #0  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, 
abstime=0x0, expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  #1  do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at 
sem_waitcommon.c:111
  #2  0x7fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, 
abstime=0x0) at sem_waitcommon.c:181
  #3  0x7fe2ac68c502 in pa_semaphore_wait () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac8cca24 in pa_asyncmsgq_send () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  #5  0x7fe2a6841119 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #6  0x7fe2ac675ee2 in pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #7  0x7fe2a6844695 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #8  0x7fe2ac678bef in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #9  0x7fe2ac67b6ab in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #10 0x7fe2ac67ba49 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #11 0x7fe2ac67c2cf in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #12 0x7fe2ac40e0d8 in pa_mainloop_dispatch () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #13 0x7fe2ac40e4ae in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #14 0x7fe2ac40e530 in pa_mainloop_run () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #15 0x56318d445b82 in main ()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-22-generic.
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   user   1009 F...m pulseaudio
   /dev/snd/controlC0:  user   1009 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Audio'/'Intel HDMI/DP LPE Audio'
 Mixer name : ''
 Components : ''
 Controls  : 15
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  CurrentDesktop: LXDE
  Date: Thu May 24 16:04:13 2018
  InstallationDate: Installed on 2018-05-22 (1 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  

[Desktop-packages] [Bug 1513384] Re: [pulseaudio-discuss] [PATCH] alsa-mixer: Add "Front Headphone" to headset mic path

[Tanu Kaskinen]

On Thu, 2015-11-05 at 09:59 +0100, David Henningsson wrote:
> The combination "Front Headphone" + "Headset Mic Phantom"
> was found on one the machines we enable. Without this patch,
> the headset mic appeared plugged in when nothing was plugged
> into the jack.
> 
> BugLink: https://bugs.launchpad.net/bugs/1513384
> Signed-off-by: David Henningsson 
> ---
>  src/modules/alsa/mixer/paths/analog-input-headset-mic.conf | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/src/modules/alsa/mixer/paths/analog-input-headset-
> mic.conf b/src/modules/alsa/mixer/paths/analog-input-headset-mic.conf
> index a67e1db..b669bc4 100644
> --- a/src/modules/alsa/mixer/paths/analog-input-headset-mic.conf
> +++ b/src/modules/alsa/mixer/paths/analog-input-headset-mic.conf
> @@ -32,6 +32,9 @@ required-any = any
>  [Jack Headphone]
>  state.plugged = unknown
>  
> +[Jack Front Headphone]
> +state.plugged = unknown
> +
>  [Jack Headphone Mic]
>  state.plugged = unknown

Looks good to me.

-- 
Tanu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1513384

Title:
  Missing "Front Headphone" in headset mic path

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Found in the wild on one of the machines we enable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1513384/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1458947]

[Tanu Kaskinen]

Updated the bug title.

The error is harmless, as you found out.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1458947

Title:
  QinHeng Electronics CH345 MIDI adapter triggers error

Status in PulseAudio sound server:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Cheap oriental MIDI adapter starts up with the following error, but
  works as expected.*

  E: [pulseaudio] module.c: Failed to load module module-alsa-card
  (argument: device_id=1 name=usb-1a86_USB2.0-MIDI-00-USB20MIDI
  card_name=alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI
  namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
  deferred_volume=yes use_ucm=yes card_properties=module-udev-
  detect.discovered=1): initialization failed.

  The device:
  1a86:752d QinHeng Electronics CH345 MIDI adapter

  Of course i'm not sure whether this is a PA problem or an ALSA or UDEV
  bug.

  Ubuntu 14.04.2 LTS
  Pulseaudio 1:4.0-0ubuntu11.1

  *  works almost as expected: there is one physical input and one
  output, but in ALSA one input and two outputs appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1458947/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1445358] Re: [pulseaudio-discuss] [PATCH] core-util, pactl: Make one localised and one non-localised version of pa_yes_no

[Tanu Kaskinen]

On Mon, 2015-04-20 at 17:41 +0200, David Henningsson wrote:
 We currently use pa_yes_no to write module arguments, so they can not be
 localised. Instead add a new pa_yes_no_localised function and use it in pactl
 (and thus, revert all other places to use the non-localised version).
 
 BugLink: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1445358
 Signed-off-by: David Henningsson david.hennings...@canonical.com
 ---
  src/pulsecore/core-util.h |  4 
  src/utils/pactl.c | 20 ++--
  2 files changed, 14 insertions(+), 10 deletions(-)

Looks good to me.

-- 
Tanu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1445358

Title:
  Pulseaudio fails to run when system's language is in certain non-
  English locales

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Changing the System Language in Greek resulted in the corruption of
  the sound in the entire system. This happened when the latest updates
  applied and after a reboot.

  I have attempted a new installation in Greek getting the latest ISO
  image and the problem exists there as well.

  If I go back (turn the system) to the English Language and reboot the
  problem disappears.

  I have also tested another Language (Russian Localization) but the
  problem does not occur.

  How to reproduce: 
  Apply the latest updates and install the Greek language packages 
(language-pack-el , language-pack-el-base). 
  Choose Greek as the system's language and reboot. 

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/by-path', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', 
'/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Apr 17 09:48:39 2015
  InstallationDate: Installed on 2015-04-15 (1 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [SVF1532X1EB, Realtek ALC233, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1080DB
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1080DB:bd09/19/2014:svnSonyCorporation:pnSVF1532X1EB:pvrC10KBNMG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVF1532X1EB
  dmi.product.version: C10KBNMG
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1445358/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1390474] Re: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26

[Tanu Kaskinen]

Kindly forwarding this bug, please express your thoughts on Launchpad.

I believe that was a direct request for me. My thoughts: it's
unfortunate that PulseAudio doesn't support mixer elements with more
than 2 volume channels. It would be nice if someone would fix that. Due
to lack of time, I won't be that someone, at least in the short (or even
medium) term.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1390474

Title:
  Volume element PCM has 6 channels. That's too much! with Terratec
  PHASE26

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error Volume element PCM has 6 channels. That's too much! I can't handle 
that!  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1289515] Re: Sound volume resets after making a call

[Tanu Kaskinen]

On Fri, 2014-03-21 at 10:27 +0100, David Henningsson wrote:
 In case a port has not yet been saved, which is e g often the case
 if a sink/source has only one port, reading volume/mute will be done
 without port, whereas writing volume/mute will be done with port.
 
 Work around this by setting a default port before the fixate hook,
 so module-device-restore can read volume/mute for the correct port.
 
 BugLink: https://bugs.launchpad.net/bugs/1289515
 Signed-off-by: David Henningsson david.hennings...@canonical.com

Thanks, this also fixes this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=55262

A couple of comments below.

 ---
  src/pulsecore/sink.c   |   11 +++
  src/pulsecore/source.c |   11 +++
  2 files changed, 22 insertions(+)
 
 diff --git a/src/pulsecore/sink.c b/src/pulsecore/sink.c
 index 08143e9..9c4b0c3 100644
 --- a/src/pulsecore/sink.c
 +++ b/src/pulsecore/sink.c
 @@ -235,6 +235,17 @@ pa_sink* pa_sink_new(
  pa_device_init_icon(data-proplist, true);
  pa_device_init_intended_roles(data-proplist);
  
 +if (!data-active_port  !data-save_port) {

How is data-save_port relevant here? If active_port is NULL, save_port
should always be false (true wouldn't have any meaning).

 +void *state;
 +pa_device_port *p, *p2 = NULL;
 +
 +PA_HASHMAP_FOREACH(p, data-ports, state)
 +if (!p2 || p-priority  p2-priority) {
 +p2 = p;
 +pa_sink_new_data_set_port(data, p2-name);

I'd prefer calling pa_sink_new_data_set_port() only once, i.e. outside
the loop.

 +}
 +}

This partially duplicates the code that is run later:

if (!s-active_port) {
void *state;
pa_device_port *p;

PA_HASHMAP_FOREACH(p, s-ports, state) {
if (p-available == PA_AVAILABLE_NO)
continue;

if (!s-active_port || p-priority  s-active_port-priority)
s-active_port = p;
}
if (!s-active_port) {
PA_HASHMAP_FOREACH(p, s-ports, state)
if (!s-active_port || p-priority  s-active_port-priority)
s-active_port = p;
}
}

I think we should do the fallback port initialization only once, in the
location where you added the new code. We should use the full logic of
the old fallback initialization code.

-- 
Tanu


** Bug watch added: freedesktop.org Bugzilla #55262
   https://bugs.freedesktop.org/show_bug.cgi?id=55262

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1289515

Title:
  Sound volume resets after making a call

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  1. mute your phone
  2. dial a number and ensure the call is picked
  3. end the call

  What happens:
  The sound volume is set to full and the phone unmutes

  What should happen:
  Ending the call should not effect the sound volume setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: telephony-service 0.1+14.04.20140303-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: armhf
  Date: Fri Mar  7 23:26:43 2014
  InstallationDate: Installed on 2014-03-07 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf 
(20140307.2)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1289515/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1256511]

[Tanu Kaskinen]

module-switch-on-port-available should not automatically change the card
profile from analog to hdmi, and when you switch the profile with
pavucontrol, that choice should be remembered... I'd like to see
PulseAudio logs.

Could you do this:

1) Disable autospawning:
echo autospawn = no  ~/.config/pulse/client.conf

2) Stop pulseaudio:
killall pulseaudio

3) Start pulseaudio in a terminal:
pulseaudio -vvv

4) Set the card profile:
pactl set-card-profile alsa_card.pci-_00_1b.0 output:analog-stereo

5) Stop pulseaudio with Ctrl-C and save the log output.

6) Start pulseaudio again:
pulseaudio -vvv

7) Check the active card profile:
pactl list cards

8) Stop pulseaudio with Ctrl-C and save the log output.

9) Attach the logs from steps 5 and 8 and the pactl output from step 7
to this bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1256511

Title:
  Sounds settings lost after reboot

Status in PulseAudio sound server:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since
  then I have no sound when I start my PC, because it's being sent to
  the HDMI output (my TV). I want it to go to the Analogue output (my
  PC) like it used to on 13.04. I can change it using the pulse-audio
  Volume Control program, but my settings are lost after I reboot.

  The pulse-audio Volume Control doesn't have my Analogue Output as a
  valid option in the Output Devices tab; it appears only after I select
  Analogue Stereo within the Configuration tab. I then choose it as my
  fallback device (which I think means default device?), but my
  changes are not saved between reboots.

  After changing the output device to Analogue Stereo using the
  Configuration tab, I then have to change the output of the individual
  program using the Playback tab, since it uses the current default
  (HDMI).

  I've tried setting my default audio device using pacmd, but it hasn't
  helped: my Analogue device does show up as the active sink when I run
  pacmd list-sinks, but it's not the selected device within the Volume
  Control (in the Configuration tab) so I don't get any sound unless I
  manually change it using the GUI.

  Here's the output of some pactl commands after I start my PC - note
  that the Analog Stereo source is missing:

  $ pactl list sources short
  0   alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c  
s16le 1ch 44100Hz   SUSPENDED
  1   alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c  
s16le 2ch 44100Hz   SUSPENDED

  $ pactl list sinks short
  0   alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c  s16le 2ch 
44100Hz   SUSPENDED

  After I open the pulse-audio Volume Control and select the Analog
  Stereo item from the Configuration tab, running the same commands
  again gives:

  $ pactl list sources short
  0   alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c
s16le 1ch 44100Hz IDLE
  1   alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c  
s16le 2ch 44100Hz   IDLE
  2   alsa_output.pci-_00_1b.0.analog-stereo.monitor  module-alsa-card.c  
s16le 2ch 44100Hz   IDLE

  $ pactl list sinks short
  0   alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c  s16le 2ch 
44100Hz   IDLE
  1   alsa_output.pci-_00_1b.0.analog-stereo  module-alsa-card.c  s16le 2ch 
44100Hz   IDLE

  The Analogue Stereo source is present and I can hear sound through my
  PC's speakers. But when I reboot my PC these settings are lost, and I
  have to do this over again. I wouldn't mind so much if I could fix
  this from the command line, but I haven't found a way to do that.

  I'm not 100% certain this is a pulseaudio bug - that's just my best
  guess.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fish   3878 F pulseaudio
   /dev/snd/pcmC0D3p:   fish   3878 F...m pulseaudio
   /dev/snd/controlC1:  fish   3878 F pulseaudio
   /dev/snd/pcmC1D0c:   fish   3878 F...m pulseaudio
  Date: Sat Nov 30 13:59:41 2013
  InstallationDate: Installed on 2013-03-01 (273 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  MarkForUpload: True
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago)
  dmi.bios.date: 08/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  

[Desktop-packages] [Bug 1256511]

[Tanu Kaskinen]

Ok, so module-card-restore claims to be selecting the analog profile
when the card is created, but actually the hdmi profile gets selected.
It might be that module-switch-on-port-available is overriding the
profile choice made by module-card-restore. I believe that's not
supposed to happen, so that's the first bug.

Another very weird bug is that when the analog profile is activated via
pactl, the hdmi sink doesn't get removed. This was actually visible
already in your initial bug description, but I didn't notice that.

I really would like to get these issues fixed by the time 6.0 is
released, so I'll make this a release blocker, but I'm afraid it will
take a while before I have time to properly start working on this bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1256511

Title:
  Sounds settings lost after reboot

Status in PulseAudio sound server:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded from Xubuntu 13.04 to 13:10 (64-bit), and since
  then I have no sound when I start my PC, because it's being sent to
  the HDMI output (my TV). I want it to go to the Analogue output (my
  PC) like it used to on 13.04. I can change it using the pulse-audio
  Volume Control program, but my settings are lost after I reboot.

  The pulse-audio Volume Control doesn't have my Analogue Output as a
  valid option in the Output Devices tab; it appears only after I select
  Analogue Stereo within the Configuration tab. I then choose it as my
  fallback device (which I think means default device?), but my
  changes are not saved between reboots.

  After changing the output device to Analogue Stereo using the
  Configuration tab, I then have to change the output of the individual
  program using the Playback tab, since it uses the current default
  (HDMI).

  I've tried setting my default audio device using pacmd, but it hasn't
  helped: my Analogue device does show up as the active sink when I run
  pacmd list-sinks, but it's not the selected device within the Volume
  Control (in the Configuration tab) so I don't get any sound unless I
  manually change it using the GUI.

  Here's the output of some pactl commands after I start my PC - note
  that the Analog Stereo source is missing:

  $ pactl list sources short
  0   alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c  
s16le 1ch 44100Hz   SUSPENDED
  1   alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c  
s16le 2ch 44100Hz   SUSPENDED

  $ pactl list sinks short
  0   alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c  s16le 2ch 
44100Hz   SUSPENDED

  After I open the pulse-audio Volume Control and select the Analog
  Stereo item from the Configuration tab, running the same commands
  again gives:

  $ pactl list sources short
  0   alsa_input.usb-046d_08b2-01-U0x46d0x8b2.analog-mono module-alsa-card.c
s16le 1ch 44100Hz IDLE
  1   alsa_output.pci-_00_1b.0.hdmi-stereo.monitormodule-alsa-card.c  
s16le 2ch 44100Hz   IDLE
  2   alsa_output.pci-_00_1b.0.analog-stereo.monitor  module-alsa-card.c  
s16le 2ch 44100Hz   IDLE

  $ pactl list sinks short
  0   alsa_output.pci-_00_1b.0.hdmi-stereomodule-alsa-card.c  s16le 2ch 
44100Hz   IDLE
  1   alsa_output.pci-_00_1b.0.analog-stereo  module-alsa-card.c  s16le 2ch 
44100Hz   IDLE

  The Analogue Stereo source is present and I can hear sound through my
  PC's speakers. But when I reboot my PC these settings are lost, and I
  have to do this over again. I wouldn't mind so much if I could fix
  this from the command line, but I haven't found a way to do that.

  I'm not 100% certain this is a pulseaudio bug - that's just my best
  guess.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pulseaudio 1:4.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fish   3878 F pulseaudio
   /dev/snd/pcmC0D3p:   fish   3878 F...m pulseaudio
   /dev/snd/controlC1:  fish   3878 F pulseaudio
   /dev/snd/pcmC1D0c:   fish   3878 F...m pulseaudio
  Date: Sat Nov 30 13:59:41 2013
  InstallationDate: Installed on 2013-03-01 (273 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  MarkForUpload: True
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to saucy on 2013-11-09 (20 days ago)
  dmi.bios.date: 08/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  

[Desktop-packages] [Bug 1236965] Re: [pulseaudio-discuss] [PATCH] alsa-mixer: Add internal surround speaker elements

[Tanu Kaskinen]

On Mon, 2013-10-14 at 16:16 +0200, David Henningsson wrote:
 These kcontrol names have started to show up lately, especially in
 combination with surround internal speakers.
 
 BugLink: https://bugs.launchpad.net/bugs/1236965
 Signed-off-by: David Henningsson david.hennings...@canonical.com
 ---
  .../alsa/mixer/paths/analog-output-speaker.conf|   31 
 
  1 file changed, 31 insertions(+)
 
 diff --git a/src/modules/alsa/mixer/paths/analog-output-speaker.conf 
 b/src/modules/alsa/mixer/paths/analog-output-speaker.conf
 index ccd438f..d79fad1 100644
 --- a/src/modules/alsa/mixer/paths/analog-output-speaker.conf
 +++ b/src/modules/alsa/mixer/paths/analog-output-speaker.conf
 @@ -38,6 +38,11 @@ required-any = any
  state.plugged = unknown
  state.unplugged = unknown
  
 +[Jack Speaker Front Phantom]
 +required-any = any
 +state.plugged = unknown
 +state.unplugged = unknown
 +
  [Element Hardware Master]
  switch = mute
  volume = merge
 @@ -88,6 +93,13 @@ override-map.1 = all-front
  override-map.2 = front-left,front-right
  required-any = any
  
 +[Element Speaker Front]
 +switch = mute
 +volume = merge
 +override-map.1 = all-front
 +override-map.2 = front-left,front-right
 +required-any = any
 +
  [Element Rear]
  switch = mute
  volume = merge
 @@ -107,12 +119,25 @@ override-map.1 = all-rear
  override-map.2 = rear-left,rear-right
  required-any = any
  
 +[Element Speaker Surround]
 +switch = mute
 +volume = merge
 +override-map.1 = all-rear
 +override-map.2 = rear-left,rear-right
 +required-any = any
 +
  [Element Side]
  switch = mute
  volume = merge
  override-map.1 = all-side
  override-map.2 = side-left,side-right
  
 +[Element Speaker Side]
 +switch = mute
 +volume = merge
 +override-map.1 = all-side
 +override-map.2 = side-left,side-right
 +
  [Element Center]
  switch = mute
  volume = merge
 @@ -152,4 +177,10 @@ volume = merge
  override-map.1 = all-center
  override-map.2 = all-center,lfe
  
 +[Element Speaker CLFE]
 +switch = mute
 +volume = merge
 +override-map.1 = all-center
 +override-map.2 = all-center,lfe
 +
  .include analog-output.conf.common

Should these elements be muted in other paths?

-- 
Tanu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1236965

Title:
  pulseaudio does not recognize internal speakers [P180HMx, Realtek
  ALC892, Speaker, Internal] volume slider problem

Status in “linux” package in Ubuntu:
  Fix Committed
Status in “pulseaudio” package in Ubuntu:
  In Progress

Bug description:
  steps to reproduce:  
  1.  acquire a device with the problem, such as Clevo P180HM laptop 
motherboard 
  2.  install ubuntu 12.04  (now updated to 12.04.3 currently) 
  3.  systray  speaker-icon  sound-settings  output tab  
  4.  no entry for speakers built-in audio appears 

  workaround:  
  running the shell script mentioned in this comment helps -- 
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/946232/comments/158 

  however, the workaround is not completely satisfactory, because 
  adjusting the (singular) volume-slider provided by pulseaudio only 
  causes some of the (multiple) volume-sliders known to alsamixer to react. 
  Specifically, turning the pulseaudio volume upwards only changes the 
  'master' and belatedly the 'pcm' volumes inside alsamixer.  This ignores 
  'speaker clfe' + 'speaker front' + 'speaker surround playback volume' 
  plus maybe others.  Effectively, this means audio playback is weak:  instead 
  of spreading typical 2ch audiofiles across all internal speakers, only some 
  are used, and only at whatever volume alsamixer specifies.  (Turning the 
  ignored volumes up in alsamixer causes a different problem:  then it is no 
  longer possible to lower the sound to a relatively-quiet volume.)  

  Here is some information from one of the ubuntu pulseaudio/alsa devs:  
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/946232/comments/159
  David Henningsso​n (946...@bugs.launchpad.net) wrote:  
  ...you have unusual hardware: in addition to normal
  headphones and stereo line out, you have 5.1 internal speakers. This
  leads to unusual alsamixer names (e g Speaker Front) which we do not
  match for in PulseAudio. Fixing that means that we should add those
  names in PulseAudio - but let's discuss that in a new bug instead.

  Let me know if you would like more specifics.  I have run codecgraph,
  alsa-info, etc.

  $ cat /proc/asound/card*/codec#* | grep --before-context=4 --after-context=1 
Subsystem Id 
  Codec: Realtek ALC892
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0892
  Subsystem Id: 0x15588000
  Revision Id: 0x100302
  --
  Codec: ATI R6xx HDMI
  Address: 0
  AFG Function Id: 0x1 (unsol 0)
  Vendor Id: 0x1002aa01
  Subsystem Id: 0x00aa0100
  Revision Id: 0x100200

  $ lspci -vvnn | grep --after-context=1 Audio device
  00:1b.0 Audio device [0403]: Intel Corporation 

[Desktop-packages] [Bug 1159687] Re: [pulseaudio-discuss] [PATCH] alsa-mixer: Add Headset Playback|Capture element

[Tanu Kaskinen]

On Mon, 2013-03-25 at 15:00 +0100, David Henningsson wrote:
 Found on Logitech B530 USB Headset / kernel 3.8. Because we don't
 have different path for headset and headphone today, just add
 Headset to the existing headphone path.

Wouldn't it be better to have a headset path for output too, at least so
that the UI can show a more accurate description of the device? This
might be useful for automatic routing too, if the path configuration
would set the device.form_factor property.

-- 
Tanu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1159687

Title:
  [USB-Audio - Logitech B530 USB Headset, recording] Recording problem

Status in “pulseaudio” package in Ubuntu:
  In Progress

Bug description:
  I upgraded to Raring from Precise (two steps upgrade) and now, when I
  plugged my USB headset a new Analog Output appears correctly in the
  sound control.

  However, the only available input is still the internal one (see
  screenshot) and I can only use the internal microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ara3538 F pulseaudio
   /dev/snd/controlC0:  ara3538 F pulseaudio
   /dev/snd/pcmC0D0c:   ara3538 F...m pulseaudio
  Date: Mon Mar 25 10:45:14 2013
  InstallationDate: Installed on 2011-05-16 (678 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Headset 
successful
  Symptom_Card: Logitech B530 USB Headset - Logitech B530 USB Headset
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Headset successful
  Symptom_Type: Only some of inputs are working
  Title: [USB-Audio - Logitech B530 USB Headset, recording] Recording problem
  UpgradeStatus: Upgraded to raring on 2013-03-24 (0 days ago)
  dmi.bios.date: 07/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8CET54WW (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4171CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8CET54WW(1.34):bd07/11/2012:svnLENOVO:pn4171CTO:pvrThinkPadT420s:rvnLENOVO:rn4171CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4171CTO
  dmi.product.version: ThinkPad T420s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1159687/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1159687] Re: [pulseaudio-discuss] [PATCH] alsa-mixer: Add Headset Playback|Capture element

[Tanu Kaskinen]

On Wed, 2013-03-27 at 11:03 +0100, David Henningsson wrote:
 On 03/27/2013 10:52 AM, Tanu Kaskinen wrote:
  On Mon, 2013-03-25 at 15:00 +0100, David Henningsson wrote:
  Found on Logitech B530 USB Headset / kernel 3.8. Because we don't
  have different path for headset and headphone today, just add
  Headset to the existing headphone path.
 
  Wouldn't it be better to have a headset path for output too, at least so
  that the UI can show a more accurate description of the device? This
  might be useful for automatic routing too, if the path configuration
  would set the device.form_factor property.
 
 In 99% of all cases, a headset has a Headphone control. A Headset 
 control is really the exception. And given the HDA specification that is 
 unlikely to change in the near future.
 
 As such, I think the extra path is not worth the cost.

OK, you have my ack for the patch then.

-- 
Tanu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1159687

Title:
  [USB-Audio - Logitech B530 USB Headset, recording] Recording problem

Status in “pulseaudio” package in Ubuntu:
  In Progress

Bug description:
  I upgraded to Raring from Precise (two steps upgrade) and now, when I
  plugged my USB headset a new Analog Output appears correctly in the
  sound control.

  However, the only available input is still the internal one (see
  screenshot) and I can only use the internal microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ara3538 F pulseaudio
   /dev/snd/controlC0:  ara3538 F pulseaudio
   /dev/snd/pcmC0D0c:   ara3538 F...m pulseaudio
  Date: Mon Mar 25 10:45:14 2013
  InstallationDate: Installed on 2011-05-16 (678 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Headset 
successful
  Symptom_Card: Logitech B530 USB Headset - Logitech B530 USB Headset
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Headset successful
  Symptom_Type: Only some of inputs are working
  Title: [USB-Audio - Logitech B530 USB Headset, recording] Recording problem
  UpgradeStatus: Upgraded to raring on 2013-03-24 (0 days ago)
  dmi.bios.date: 07/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8CET54WW (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4171CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8CET54WW(1.34):bd07/11/2012:svnLENOVO:pn4171CTO:pvrThinkPadT420s:rvnLENOVO:rn4171CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4171CTO
  dmi.product.version: ThinkPad T420s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1159687/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1069232]

[Tanu Kaskinen]

(In reply to comment #7)
 Same here.  Really annoying for VLC user.
 
 I'm not familar with pa so I cannot say whether this patch is has something
 wrong or not.  !!!But this commit broken the userspace!!!   Should
 it be reverted?
 
 It's 7 month after this bug has been reported.  Should the developer say
 something to show that this bug is not totally ignored?

Sure, I can say something. The problematic commit implements a useful
feature, so it probably won't be simply reverted. A better fix is needed
(patches very welcome). There have been fixes related to the sample rate
updating since pulseaudio 2.0, so it's worth retrying with pulseaudio
3.0, but I don't remember that those fixes would have been timing
related, so don't expect too much.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1069232

Title:
  Sound lags when opening video files

Status in PulseAudio sound server:
  Fix Released
Status in VLC media player:
  Invalid
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “vlc” package in Ubuntu:
  Invalid

Bug description:
  When I open any video file from Nautilus or from VLC I see that video
  starts but there is no sound. It takes a few seconds and the sound
  appears, but since the beginning of the audio track. So video and
  sound are out of sync.

  The workaround is to rewind the video at the beginning by using the
  slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: vlc-nox 2.0.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu4
  Architecture: amd64
  Date: Sun Oct 21 01:33:08 2012
  ExecutablePath: /usr/bin/vlc
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121006)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1069232/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1069232]

[Tanu Kaskinen]

(In reply to comment #8)
 (In reply to comment #7)
  Same here.  Really annoying for VLC user.
  
  I'm not familar with pa so I cannot say whether this patch is has something
  wrong or not.  !!!But this commit broken the userspace!!!   Should
  it be reverted?
  
  It's 7 month after this bug has been reported.  Should the developer say
  something to show that this bug is not totally ignored?
 
 Sure, I can say something. The problematic commit implements a useful
 feature, so it probably won't be simply reverted. A better fix is needed
 (patches very welcome). There have been fixes related to the sample rate
 updating since pulseaudio 2.0, so it's worth retrying with pulseaudio 3.0,
 but I don't remember that those fixes would have been timing related, so
 don't expect too much.

Thinking a bit more, reverting the patch (or maybe commenting out the
code would be better) is maybe the right approach after all, if nobody
submits a better fix. Removing the code that was added that patch
shouldn't really break anything, the only effect should be that there's
sometimes unnecessary resampling, which is better than breaking the
timing of applications.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1069232

Title:
  Sound lags when opening video files

Status in PulseAudio sound server:
  Fix Released
Status in VLC media player:
  Invalid
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “vlc” package in Ubuntu:
  Invalid

Bug description:
  When I open any video file from Nautilus or from VLC I see that video
  starts but there is no sound. It takes a few seconds and the sound
  appears, but since the beginning of the audio track. So video and
  sound are out of sync.

  The workaround is to rewind the video at the beginning by using the
  slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: vlc-nox 2.0.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu4
  Architecture: amd64
  Date: Sun Oct 21 01:33:08 2012
  ExecutablePath: /usr/bin/vlc
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121006)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1069232/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1069232]

[Tanu Kaskinen]

Before removing any functionality, this must be reproducible by a
pulseaudio developer, though. Otherwise there's no way to know when it's
safe to add the functionality back. I can't reproduce this with vlc
version 2.0.3 and pulseaudio's current development version. I'll try
installing vlc 2.0.1 and pulseaudio 2.0 later today.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1069232

Title:
  Sound lags when opening video files

Status in PulseAudio sound server:
  Fix Released
Status in VLC media player:
  Invalid
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “vlc” package in Ubuntu:
  Invalid

Bug description:
  When I open any video file from Nautilus or from VLC I see that video
  starts but there is no sound. It takes a few seconds and the sound
  appears, but since the beginning of the audio track. So video and
  sound are out of sync.

  The workaround is to rewind the video at the beginning by using the
  slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: vlc-nox 2.0.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu4
  Architecture: amd64
  Date: Sun Oct 21 01:33:08 2012
  ExecutablePath: /usr/bin/vlc
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121006)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1069232/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1069232]

[Tanu Kaskinen]

Any further hints for reproducing? I have pulseaudio 2.0 installed, and
since vlc version shouldn't matter, I still have vlc 2.0.3, not 2.0.1
that the original reporter used. A/V sync is just fine for me, with both
pulseaudio and alsa (through pulseaudio) backends of vlc.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1069232

Title:
  Sound lags when opening video files

Status in PulseAudio sound server:
  Fix Released
Status in VLC media player:
  Invalid
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “vlc” package in Ubuntu:
  Invalid

Bug description:
  When I open any video file from Nautilus or from VLC I see that video
  starts but there is no sound. It takes a few seconds and the sound
  appears, but since the beginning of the audio track. So video and
  sound are out of sync.

  The workaround is to rewind the video at the beginning by using the
  slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: vlc-nox 2.0.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu4
  Architecture: amd64
  Date: Sun Oct 21 01:33:08 2012
  ExecutablePath: /usr/bin/vlc
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121006)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1069232/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1069232]

[Tanu Kaskinen]

I was now able to reproduce this. For me this doesn't seem to happen
100% of the time (I test by running vlc ~/misc/sync_test.mp4,
observing the A/V sync, closing vlc, waiting for the sink to suspend,
and trying again). The small hardware buffer size that I have (371 ms)
might make noticing the delay harder, if the delay is variable, but if
it's always one full hw buffer size in length, then I should be able to
reliably notice it... I'll build a custom kernel next with a bigger
audio buffer, and see if that changes anything.

Btw, Remi, you said that this affects all VLC versions [...] with
PulseAudio 2.x. Do you mean that this doesn't affect 3.0?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1069232

Title:
  Sound lags when opening video files

Status in PulseAudio sound server:
  Fix Released
Status in VLC media player:
  Invalid
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “vlc” package in Ubuntu:
  Invalid

Bug description:
  When I open any video file from Nautilus or from VLC I see that video
  starts but there is no sound. It takes a few seconds and the sound
  appears, but since the beginning of the audio track. So video and
  sound are out of sync.

  The workaround is to rewind the video at the beginning by using the
  slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: vlc-nox 2.0.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu4
  Architecture: amd64
  Date: Sun Oct 21 01:33:08 2012
  ExecutablePath: /usr/bin/vlc
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121006)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1069232/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1069232]

[Tanu Kaskinen]

With bigger hw buffer I was able to reproduce the problem 100% of time
on pulseaudio 2.0. With the current development version I can't
reproduce the problem. Thus, resolving the bug as fixed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1069232

Title:
  Sound lags when opening video files

Status in PulseAudio sound server:
  Fix Released
Status in VLC media player:
  Invalid
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “vlc” package in Ubuntu:
  Invalid

Bug description:
  When I open any video file from Nautilus or from VLC I see that video
  starts but there is no sound. It takes a few seconds and the sound
  appears, but since the beginning of the audio track. So video and
  sound are out of sync.

  The workaround is to rewind the video at the beginning by using the
  slider.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: vlc-nox 2.0.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu4
  Architecture: amd64
  Date: Sun Oct 21 01:33:08 2012
  ExecutablePath: /usr/bin/vlc
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121006)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1069232/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1058200] Re: [pulseaudio-discuss] [PATCH] stream: Return error in case a client peeks to early

[Tanu Kaskinen]

On Tue, 2012-11-06 at 08:36 +0100, David Henningsson wrote:
 On 11/05/2012 07:13 PM, Tanu Kaskinen wrote:
  On Sun, 2012-11-04 at 23:09 +0100, David Henningsson wrote:
  On 11/04/2012 02:22 PM, Tanu Kaskinen wrote:
  On Sat, 2012-11-03 at 19:51 +0100, David Henningsson wrote:
  Returning NULL seems to be the right thing to do here, even if
  gnome-control-center does not handle that very well IIRC. So we might
  need an additional patch in g-c-c.
  So assuming I commit a patch doing that. If somebody else wants to add
  logic to figure out how large the hole is, that could be discussed
  separately.
  Any objections?
 
  It's not clear what you meant by add logic to figure out how large the
  hole is. Add to where? pa_stream_peek() or gnome-control-center?
 
  I was referring to your earlier comment An addition: the client
  probably wants to know how large the hole is., i e pa_stream_peek.
 
  To me, reporting the hole length in the nbytes parameter of
  pa_stream_peek() seems like the right thing to do, so I hope your patch
  will do this.
 
  It does not: I was just suggesting to discuss that separately.
 
  Ok. Well, I'm suggesting to not make these issues separate, since it's a
  small thing to decide and implement, and doing a separate fix would be
  fixing a fix.
 
 I don't have an issue with step-by-step improvements. I see this as such 
 (if the second step is to be seen as an improvement).
 
  Does someone have an issue with returning the hole size
  in the nbytes argument?
 
 Not if you're volunteering to do the work. All I care about is that PA 
 clients can crash for this reason, and I'd like that to stop happening.

Cool, I certainly volunteer to do the work. It should be trivial, so
I'll probably send a patch today.

 Note: gnome-control-center needs a corresponding fix either way, as it 
 currently checks the length rather than the NULL pointer, IIRC.

Mmm, I guess I should take this task too.

-- 
Tanu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1058200

Title:
  [sound]: gnome-control-center crashed with SIGABRT in
  pa_memblock_acquire()

Status in “pulseaudio” package in Ubuntu:
  Fix Released

Bug description:
  The Sound panel has been extremely crash-prone for the past oh, maybe
  2 weeks.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Sep 26 15:34:20 2012
  ExecutablePath: /usr/bin/gnome-control-center
  ProcCmdline: gnome-control-center --overview
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   pa_memblock_acquire () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-2.1.so
   pa_stream_peek () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   ?? () from /usr/lib/control-center-1/panels/libsound.so
  Title: [sound]: gnome-control-center crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.92-0ubuntu1
   gnome-control-center-signon 0.0.17-0ubuntu1
   indicator-datetime  12.10.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1058200/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1058200] Re: [pulseaudio-discuss] [PATCH] stream: Return error in case a client peeks to early

[Tanu Kaskinen]

On Sun, 2012-11-04 at 23:09 +0100, David Henningsson wrote:
 On 11/04/2012 02:22 PM, Tanu Kaskinen wrote:
  On Sat, 2012-11-03 at 19:51 +0100, David Henningsson wrote:
  Returning NULL seems to be the right thing to do here, even if
  gnome-control-center does not handle that very well IIRC. So we might
  need an additional patch in g-c-c.
  So assuming I commit a patch doing that. If somebody else wants to add
  logic to figure out how large the hole is, that could be discussed
  separately.
  Any objections?
 
  It's not clear what you meant by add logic to figure out how large the
  hole is. Add to where? pa_stream_peek() or gnome-control-center?
 
 I was referring to your earlier comment An addition: the client 
 probably wants to know how large the hole is., i e pa_stream_peek.
 
  To me, reporting the hole length in the nbytes parameter of
  pa_stream_peek() seems like the right thing to do, so I hope your patch
  will do this.
 
 It does not: I was just suggesting to discuss that separately.

Ok. Well, I'm suggesting to not make these issues separate, since it's a
small thing to decide and implement, and doing a separate fix would be
fixing a fix. Does someone have an issue with returning the hole size
in the nbytes argument?

-- 
Tanu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1058200

Title:
  [sound]: gnome-control-center crashed with SIGABRT in
  pa_memblock_acquire()

Status in “pulseaudio” package in Ubuntu:
  Fix Released

Bug description:
  The Sound panel has been extremely crash-prone for the past oh, maybe
  2 weeks.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Sep 26 15:34:20 2012
  ExecutablePath: /usr/bin/gnome-control-center
  ProcCmdline: gnome-control-center --overview
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   pa_memblock_acquire () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-2.1.so
   pa_stream_peek () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   ?? () from /usr/lib/control-center-1/panels/libsound.so
  Title: [sound]: gnome-control-center crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.92-0ubuntu1
   gnome-control-center-signon 0.0.17-0ubuntu1
   indicator-datetime  12.10.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1058200/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1058200] Re: [pulseaudio-discuss] [PATCH] stream: Return error in case a client peeks to early

[Tanu Kaskinen]

On Sat, 2012-11-03 at 19:51 +0100, David Henningsson wrote:
 2012-11-03 17:19, Colin Guthrie skrev:
  'Twas brillig, and Tanu Kaskinen at 05/10/12 13:58 did gyre and gimble:
  On Wed, 2012-10-03 at 08:50 +0200, David Henningsson wrote:
  On 10/02/2012 10:38 PM, Tanu Kaskinen wrote:
  On Mon, 2012-10-01 at 17:06 +0200, David Henningsson wrote:
  If there is no silence memblock and no data, pa_memblockq_peek can
  return NULL. In this case, do not crash on an assertion in
  pa_memblock_acquire, but instead return a proper error to the client.
  If there is no data in the buffer, pa_stream_peek() is supposed to
  return NULL according to the documentation. And it does that: if there's
  no data, pa_memblock_peek() will return a negative value, causing
  pa_stream_peek() to return NULL.
 
  The problem is the case where the buffer does contain data, but not at
  the read index. That is, there is a hole in the buffer. The client
  documentation doesn't have any warnings about holes, so the only safe
  way to handle holes is to return silence. Fixing this should be a simple
  matter of giving a silence memchunk when creating record_memblockq.
  I'm not so sure. Silence, as in all zeroes, might work for S16 audio
  data, but what about other formats? Compressed audio? Peak audio (which
  I think is the case here)? Etc.
  Good point. Regarding PCM, if pa_memchunk_silence() is used, the
  function will take care of filling the memory with appropriate content.
  But that doesn't work with compressed audio.
 
  Also maybe it could also be valuable for the client to distinguish
  between no data available, and valid zero data.
 
  How about returning NULL and adding to the documentation something like:
 
  -If no data is available this will return a NULL pointer.
  +If no data is available (at the current read position), this will
  return a NULL pointer.
  An addition: the client probably wants to know how large the hole is. It
  might be possible to figure that out somehow from the read index, but I
  think it would make sense to return the hole size in the length
  parameter.
  This discussion seemed to stagnate. Is this worth fixing/documenting for
  the 3.0 release?
 
  Col
 
 
 Returning NULL seems to be the right thing to do here, even if 
 gnome-control-center does not handle that very well IIRC. So we might 
 need an additional patch in g-c-c.
 So assuming I commit a patch doing that. If somebody else wants to add 
 logic to figure out how large the hole is, that could be discussed 
 separately.
 Any objections?

It's not clear what you meant by add logic to figure out how large the
hole is. Add to where? pa_stream_peek() or gnome-control-center?

To me, reporting the hole length in the nbytes parameter of
pa_stream_peek() seems like the right thing to do, so I hope your patch
will do this.

-- 
Tanu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1058200

Title:
  [sound]: gnome-control-center crashed with SIGABRT in
  pa_memblock_acquire()

Status in “pulseaudio” package in Ubuntu:
  Fix Released

Bug description:
  The Sound panel has been extremely crash-prone for the past oh, maybe
  2 weeks.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Sep 26 15:34:20 2012
  ExecutablePath: /usr/bin/gnome-control-center
  ProcCmdline: gnome-control-center --overview
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   pa_memblock_acquire () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-2.1.so
   pa_stream_peek () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   ?? () from /usr/lib/control-center-1/panels/libsound.so
  Title: [sound]: gnome-control-center crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.92-0ubuntu1
   gnome-control-center-signon 0.0.17-0ubuntu1
   indicator-datetime  12.10.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1058200/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 689915] Re: [pulseaudio-discuss] [RFC PATCH] bluetooth: Fix assertion failure (decoded == a2dp-frame_length)

[Tanu Kaskinen]

On Wed, 2012-10-10 at 09:17 +0200, David Henningsson wrote:
 According to the patch author, Karl Hegbloom:
 The assertion is incorrectly testing for '==' when logically it
 should test for '='.
 
 BugLink: https://bugs.launchpad.net/bugs/689915
 Signed-off-by: David Henningsson david.hennings...@canonical.com
 ---
 
 This is a patch I found attached to a bug in Ubuntu. I don't know
 much about bluetooth, and the error was reported against something
 around 0.9.22. But I'm sending it here, hoping that one of our
 bluetooth people can review and say whether this is correct or not.
 
  src/modules/bluetooth/module-bluetooth-device.c |4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)
 
 diff --git a/src/modules/bluetooth/module-bluetooth-device.c 
 b/src/modules/bluetooth/module-bluetooth-device.c
 index e3ec6ae..06c783d 100644
 --- a/src/modules/bluetooth/module-bluetooth-device.c
 +++ b/src/modules/bluetooth/module-bluetooth-device.c
 @@ -999,9 +999,9 @@ static int a2dp_process_push(struct userdata *u) {
  a2dp-frame_length = sbc_get_frame_length(a2dp-sbc);
  
  pa_assert_fp((size_t) decoded = to_decode);
 -pa_assert_fp((size_t) decoded == a2dp-frame_length);
 +pa_assert_fp((size_t) decoded = a2dp-frame_length);
  
 -pa_assert_fp((size_t) written == a2dp-codesize);
 +pa_assert_fp((size_t) written = a2dp-codesize);
  
  p = (const uint8_t*) p + decoded;
  to_decode -= decoded;

I'm no SBC expert either, but I had a look at sbc_decode()
implementation, and to me it looks like at least decoded ==
a2dp-frame_length should hold. Extrapolating from that, written ==
a2dp-codesize probably should hold too. And it makes sense:
sbc_decode() is supposed to decode one frame, and I think one frame will
always have encoded size of a2dp-frame_length and decoded size of
a2dp-codesize.

-- 
Tanu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/689915

Title:
  pulseaudio aborts with assertion decoded == a2dp-frame_length in
  function a2dp_process_push()

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  Binary package hint: pulseaudio

  See also ticket: http://pulseaudio.org/ticket/636

  Steps to reproduce:
  1. start pulseaudio daemon
  2. issue a bluez AudioSource?.Connect() dbus call, or use blueman to connect 
the laptop as audio source
  3. daemon aborts with 
  Assertion '(size_t) decoded == a2dp-frame_length' failed at 
modules/bluetooth/module-bluetooth-device.c:1361, function a2dp_process_push(). 
Aborting.

  I have the problem with as source OSX Snow Leopard, and target Ubuntu
  Linux Lucid

  
  Source bitpool settings: 40 
  Pulseaudio version: pulseaudio 0.9.21-63-gd3efa-dirty 

  
  My first suggestion would be to update the bluetooth module, from git.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/689915/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1058200] Re: [pulseaudio-discuss] [PATCH] stream: Return error in case a client peeks to early

[Tanu Kaskinen]

On Wed, 2012-10-03 at 08:50 +0200, David Henningsson wrote:
 On 10/02/2012 10:38 PM, Tanu Kaskinen wrote:
  On Mon, 2012-10-01 at 17:06 +0200, David Henningsson wrote:
  If there is no silence memblock and no data, pa_memblockq_peek can
  return NULL. In this case, do not crash on an assertion in
  pa_memblock_acquire, but instead return a proper error to the client.
 
  If there is no data in the buffer, pa_stream_peek() is supposed to
  return NULL according to the documentation. And it does that: if there's
  no data, pa_memblock_peek() will return a negative value, causing
  pa_stream_peek() to return NULL.
 
  The problem is the case where the buffer does contain data, but not at
  the read index. That is, there is a hole in the buffer. The client
  documentation doesn't have any warnings about holes, so the only safe
  way to handle holes is to return silence. Fixing this should be a simple
  matter of giving a silence memchunk when creating record_memblockq.
 
 I'm not so sure. Silence, as in all zeroes, might work for S16 audio 
 data, but what about other formats? Compressed audio? Peak audio (which 
 I think is the case here)? Etc.

Good point. Regarding PCM, if pa_memchunk_silence() is used, the
function will take care of filling the memory with appropriate content.
But that doesn't work with compressed audio.

 Also maybe it could also be valuable for the client to distinguish 
 between no data available, and valid zero data.
 
 How about returning NULL and adding to the documentation something like:
 
 -If no data is available this will return a NULL pointer.
 +If no data is available (at the current read position), this will 
 return a NULL pointer.

An addition: the client probably wants to know how large the hole is. It
might be possible to figure that out somehow from the read index, but I
think it would make sense to return the hole size in the length
parameter.

-- 
Tanu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1058200

Title:
  [sound]: gnome-control-center crashed with SIGABRT in
  pa_memblock_acquire()

Status in “pulseaudio” package in Ubuntu:
  Fix Released

Bug description:
  The Sound panel has been extremely crash-prone for the past oh, maybe
  2 weeks.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Sep 26 15:34:20 2012
  ExecutablePath: /usr/bin/gnome-control-center
  ProcCmdline: gnome-control-center --overview
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   pa_memblock_acquire () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-2.1.so
   pa_stream_peek () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   ?? () from /usr/lib/control-center-1/panels/libsound.so
  Title: [sound]: gnome-control-center crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.92-0ubuntu1
   gnome-control-center-signon 0.0.17-0ubuntu1
   indicator-datetime  12.10.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1058200/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1058200] Re: [pulseaudio-discuss] [PATCH] stream: Return error in case a client peeks to early

[Tanu Kaskinen]

On Mon, 2012-10-01 at 17:06 +0200, David Henningsson wrote:
 If there is no silence memblock and no data, pa_memblockq_peek can
 return NULL. In this case, do not crash on an assertion in
 pa_memblock_acquire, but instead return a proper error to the client.

If there is no data in the buffer, pa_stream_peek() is supposed to
return NULL according to the documentation. And it does that: if there's
no data, pa_memblock_peek() will return a negative value, causing
pa_stream_peek() to return NULL.

The problem is the case where the buffer does contain data, but not at
the read index. That is, there is a hole in the buffer. The client
documentation doesn't have any warnings about holes, so the only safe
way to handle holes is to return silence. Fixing this should be a simple
matter of giving a silence memchunk when creating record_memblockq.

-- 
Tanu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1058200

Title:
  [sound]: gnome-control-center crashed with SIGABRT in
  pa_memblock_acquire()

Status in “pulseaudio” package in Ubuntu:
  In Progress

Bug description:
  The Sound panel has been extremely crash-prone for the past oh, maybe
  2 weeks.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu15
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Sep 26 15:34:20 2012
  ExecutablePath: /usr/bin/gnome-control-center
  ProcCmdline: gnome-control-center --overview
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   pa_memblock_acquire () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-2.1.so
   pa_stream_peek () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   ?? () from /usr/lib/control-center-1/panels/libsound.so
  Title: [sound]: gnome-control-center crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup23.92-0ubuntu1
   gnome-control-center-signon 0.0.17-0ubuntu1
   indicator-datetime  12.10.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1058200/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp