Should I move to the latest alsa driver? If so, how do I do this?
Just follow the instructions here:
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
Try that first. If it does not help, here's another workaround you can
try:
Edit the file /etc/modprobe.d/alsa-base.conf and add:
options
Also, you seem to have some strange stuff in ~/.asoundrc and
/etc/asound.conf. Before doing anything else, could you remove these
files (or move them somewhere for backup purposes). It probably won't
solve this issue, but it's just good to have one cause of error removed.
--
You received this
Is this fix just for the specific motherboard or all alc882 chips.
The fix released into Utopic was only for that specific motherboard. If
you have the same problem with other motherboards, please file a new bug
using the ubuntu-bug audio command. But first double-check that
everything is right
Hi!
I believe this is now fixed in Ubuntu 14.10, because the patches were
included in upstream alsa-utils 1.0.28 which is in Utopic since end of
July. Please confirm and reopen the bug if it is not. Thanks!
Reference:
Hi,
It's hard to tell why PulseAudio crashes or does not start. You do have
some worrying messages about read failures from sda (which is usually
your hard drive), but I'm not sure if that's related.
The best would be if you could also produce a PulseAudio log:
strange that only have /dev/snd/hwC0D2
There is only one codec, and it has address 2. This is unusual, but not wrong.
Just supply card and device arguments to hda-jack-sense-test: sudo
hda-jack-sense-test -c 0 -d 2.
That said, hda-jack-sense-test has a tendency to break from time to time, when
Confirmed working on my laptop (which was the one where I also did the
development of the patch).
Also, I ran a random clicking regression test on my desktop computer
(which does not have bluetooth), no regressions found.
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ SRU Justification:
+
+ Requested by OEM-priority.
+
+ [Test case]
Steps to reproduce:
1. On a normal laptop, connect a bluetooth headset with both a2dp and hsp
capabilities
2. Go to output tab, select headset and set to a2dp profile
3. Go to input tab and
First bug upstreamed as
https://bugzilla.gnome.org/show_bug.cgi?id=736943
** Bug watch added: GNOME Bug Tracker #736943
https://bugzilla.gnome.org/show_bug.cgi?id=736943
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1261666 ***
https://bugs.launchpad.net/bugs/1261666
** This bug has been marked a duplicate of bug 1261666
[pulseaudio] module.c: Failed to load module module-echo-cancel (argument:
aec_method=webrtc): initia lization failed.
--
You received this bug
** Changed in: unity-control-center (Ubuntu)
Status: Triaged = In Progress
** Changed in: oem-priority
Status: Triaged = In Progress
** Branch linked: lp:~diwic/unity-control-center/lp1367693
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: oem-priority
Assignee: (unassigned) = David Henningsson (diwic)
** Changed in: unity-control-center (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
** Changed in: oem-priority
Status: New = Triaged
** Changed in: unity-control-center (Ubuntu
Ok, so one finding:
This row (in gvc-mixer-control.c, update_sink and update_source)
control-priv-profile_swapping_device_id =
GVC_MIXER_UI_DEVICE_INVALID;
...needs to move inside this block:
if (gvc_mixer_ui_device_get_stream_id (dev) ==
Ok, and the second finding. If a stream is currently creating,
pa_stream_disconnect fails, and the stream continues to set itself up and
starts to produce samples.
So when the sound applet starts up, this seems to happen due to some race
condition because active_input_update is called twice.
Thanks for the log. Looking at the log, PulseAudio seems to do the right
thing. It first tests input:multichannel, which succeeds, then
output:multichannel, which also succeeds, but when then trying full
duplex, we get an error back from the kernel:
I: [lt-pulseaudio] (alsa-lib)pcm_hw.c:
Public bug reported:
Steps to reproduce:
1. On a normal laptop, connect a bluetooth headset with both a2dp and hsp
capabilities
2. Go to output tab, select headset and set to a2dp profile
3. Go to input tab and select headset.
Now, the headset appears selected, but in fact it is not and
** Attachment added: Screenshot from 2014-09-10 12:57:24.png
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1367693/+attachment/4200491/+files/Screenshot%20from%202014-09-10%2012%3A57%3A24.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
- is Steps to reproduce:
+ Steps to reproduce:
1. On a normal laptop, connect a bluetooth headset with both a2dp and hsp
capabilities
2. Go to output tab, select headset and set to a2dp profile
3. Go to input tab and select headset.
Now, the headset appears
Hi Joe and thanks for testing,
However, the git binary doesn't detect my motherboard's onboard HDA
Intel PCH sound card (like the default pulseaudio in ubuntu does)
This could be because we have removed extra-hdmi.conf. There might still
be a udev rule referencing extra-hdmi.conf as this is
This should be fixed with the multichannel patch in git head. Please
test it and reopen this bug if it isn't fixed. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986817
Title:
UA-101 -
If the radeon driver is the problem and the intel one works, then just
disabling the radeon hdmi card would be a better workaround, i e, in
your case:
options snd-hda-intel enable=1,1,0
Vga-switcheroo cards are quite unusual so I don't have much experience
with those. Does the above work for you
Looking at your data, it looks like skype has a low-latency stream
running. I e, killing skype should also fix the issue.
Unfortunately, skype is closed source software, so not sure how to fix
the root cause.
** Package changed: pulseaudio (Ubuntu) = skype (Ubuntu)
** Changed in: skype (Ubuntu)
@Olof
Sorry, I was a bit too quick in posting that. When adding the line “options
snd-hda-intel model=dell-headset-multi to
/etc/modprobe.d/alsa-base.conf it now seems to work without noise with the
daily drivers! Thanks for the good work!
Actually your first alsa-info shows a line saying
Backport of commit 423044744aa4c250058e976474856a7a41972182.
This makes the mute LED work on a HP 15 touchsmart machine (and
a HP 14 touchsmart machine).
BugLink: https://bugs.launchpad.net/bugs/1334950
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda
On 2014-08-19 16:27, Takashi Iwai wrote:
At Tue, 19 Aug 2014 15:38:44 +0200,
David Henningsson wrote:
Backport of commit 423044744aa4c250058e976474856a7a41972182.
This makes the mute LED work on a HP 15 touchsmart machine (and
a HP 14 touchsmart machine).
BugLink: https
Thanks jaunmanuel for finding the fix and sharing the knowledge about how you
found it.
I'll add redirecting 'aplay' temporarily to a script to my list of debugging
techniques :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
When shall I see the relevant update on my system? Will it be available in
the current Ubuntu release (14.04)?
Or in some other kernel version?
It is fixed in 14.10, or in 14.04 with upgraded hwe stack. Both will
take some time before release, so until then, if you want to try, use
this
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: hwe-next
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248949
** Changed in: hwe-next
Status: Fix Committed = Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253038
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: hwe-next
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248856
** Changed in: hwe-next
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1250377
Title:
Automute broken with Realtek multifunction headset jacks
To manage
** Changed in: alsa-driver (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211920
Title:
Low audio output / missing subwoofer on Vostro 5460/5470
** Package changed: alsa-driver (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319291
Title:
[ABit AA8XE] Ubuntu 14.04 NO audio (internal audio device not
recognized
I am uncertain if HDA retask made permanent changes to the mapping? I chose
boot override and then restarted.
When relaunching hdajackretask i see that none of the overrides are checked.
This sounds like a bug in hdajackretask.
I still do not understand which nodes are for which speakers.
Hi and thanks for reporting and working on this bug!
First thing to know is that different machines have different PCI SSIDs.
For information about this, look at the PCI SSID section of
https://wiki.ubuntu.com/Audio/SameHardware
If you have PCI SSID 1028:05fe or 1028:060a, the fix for the noise
Backport of commit 423044744aa4c250058e976474856a7a41972182.
This makes the mute LED work on a HP 15 touchsmart machine (and
a HP 14 touchsmart machine).
BugLink: https://bugs.launchpad.net/bugs/1334950
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda
On 2014-07-29 16:59, Greg KH wrote:
On Tue, Jul 29, 2014 at 02:36:06PM +0200, David Henningsson wrote:
Backport of commit 423044744aa4c250058e976474856a7a41972182.
That commit is not in Linus's tree, so there's nothing I can do with
this, why send it?
This makes the mute LED work on a HP 15
Applied upstream.
Do you need backport to 3.13 kernel? If so the patch will look
different, so I'll need the alsainfo for the HP 14 touchsmart too.
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Looking at the code, there are a few different ways in which the LED can
be controlled. It's probably one of those and we just need to find the
right one through trial and error.
Let's try the ALC269_FIXUP_HP_MUTE_LED_MIC1 quirk first. I'll prepare a
dkms package shortly.
--
You received this
For reference, this is the patch used in the dkms package.
** Patch added: hp15touchsmart_muteled.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334950/+attachment/4145350/+files/hp15touchsmart_muteled.patch
--
You received this bug notification because you are a member of
** Attachment added: oem-audio-hda-daily-dkms_0.1_all.deb
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1334950/+attachment/4145349/+files/oem-audio-hda-daily-dkms_0.1_all.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please try the dkms on top of the trusty kernel and report the result.
Thanks!
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi a16g, please reassing to hotkey expert. Thanks!
** Changed in: linux (Ubuntu)
Assignee: David Henningsson (diwic) = Anthony Wong (anthonywong)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Here's a debdiff for the compiler warning.
** Patch added: debdiff.patch
https://bugs.launchpad.net/ubuntu/+source/webrtc-audio-processing/+bug/1325859/+attachment/4145504/+files/debdiff.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
- fix Pulseaudio's self-detection so that it works when the first
instance is still initializing
Yes, this is what should happen.
As for running Pulseaudio as a specific user, I wonder what would happen
when multiple users are logging onto a system at the
same time. Would this not
Please increase the importance further,
From what I can tell, we're currently waiting for a security review by
the security team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261666
Title:
Hi cschramm and thanks for looking at this bug!
How do you think we should proceed to release a fix/workaround? Should
we just upload the code that disables the module unload, or do you have
a better suggestion?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@David: If you like I'll push the fix to Debian testing. That's
probably the cleanest way to also get it into Ubuntu, isn't it?
Sounds like a plan, thanks!
Not sure if we sync from Debian unstable or Debian testing these days,
but I assume you upload the fix to both. That will bring it into
It seems to be specific to KDE too. It could be related to KDE having a
login sound which Unity does not have (I assume that's what the aplay
does?), but it could also be something in the way KDE sets up
sessions...?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Another quirk to make the headset mic work on some new Dell machines.
Cc: Hui Wang hui.w...@canonical.com
BugLink: https://bugs.launchpad.net/bugs/1297581
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c | 12
1 file changed, 12
Well, the question is why aplay - alsa pulse plugin - libpulse does not
connect to the existing instance but instead starts a new one.
What about the files in /var/run/user/userid/pulse/ - if there are pid files,
to they point to the new-invalid or old-valid pulse instance?
--
You received
One other thing I noticed is upon startup/load of Ubuntu, at the top
of the screen it says something about snd hda codec module has bad
taint.
This is the alsa daily build module. It is printing an warning message
to inform you that you're running a module that was not compiled with
the rest of
-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index f52f096..229a189 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound
: New = In Progress
** Changed in: alsa-driver (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
** Package changed: alsa-driver (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Assignee: David Henningsson (diwic) = (unassigned)
--
You received this bug notification
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331915
Title:
[XPS 15 9530, Realtek ALC668, Mic, Internal] No autoswitch when
I tried to re-submit the bug report but I am not really sure what the
alsa-base.conf should look like or how to reinstall/overwrite.
These commands will replace your alsa-base.conf with the original one:
sudo mv /etc/modprobe.conf/alsa-base.conf ~/alsa-base.conf.old
sudo apt-get install
You have modified /etc/modprobe.d/alsa-base.conf to include these lines:
options snd-hda-intel model=targa-dig
options snd slots=snd-hda-intel
# u1Nb.u_BNWJ+LvyF:82801I (ICH9 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
Please revert this file to the original configuration (i e
in advance.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331915
Title:
[XPS 15 9530, Realtek ALC668, Mic, Internal] No autoswitch
in the sound settings for the headset microphone.
On Thu, Jun 19, 2014 at 2:06 PM, David Henningsson
david.hennings...@canonical.com wrote:
Hi Kent,
It looks like we're missing a quirk entry for this machine, it's likely one
of those machines where you have to ask the user what (s)he plugged in.
You
So, I guess one could insert a check in the call to
command_create_record_stream (src/pulsecore/protocol-native.c), that would deny
access if trust-store says so.
However, there is still a way around that. Any app that can access the shm file
can potentially look at audio data currently
Sorry: IndentationError: expected an indented block (PulseAudio.py, line
235)
Oops, then I screwed up. Please do not use the package.
This should now be fixed. A new package is currently building in the
ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm a bit surprised there are two pulseaudios with different PIDs
active though. Could that be a problem?
Yes, probably. On hotplugging, they could both try to probe the device
at the same time, and only one of them succeeds. Probably one of the
instances gets the playback and the other one gets
** Summary changed:
- everything is muted when headphones are plugged in
+ [W230SS, VIA1802] no sound from headphones
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1329468
Title:
[W230SS, VIA1802]
So I think the right way to go here is to modify /lib/udev/rules.d/90
-alsa-restore.rules and add a check of /usr/share/alsa and
/var/run/alsa, so the entire file ends up like this (first line changed)
:
-
ACTION==add, SUBSYSTEM==sound, KERNEL==controlC*, KERNELS!=card*,
(or upstart equivalent) will
run later on.
BugLink: https://bugs.launchpad.net/bugs/1289730
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
I'm not really sure of all quirks in the boot process, and I haven't tested the
patch either, hence the RFC above. Do you think it makes sense
On 2014-06-13 10:26, Jaroslav Kysela wrote:
Date 13.6.2014 10:15, David Henningsson wrote:
The 90-alsa-restore.rules udev rule is primarily meant to handle hotplugging,
but sometimes it is also run before /usr is mounted,
and alsactl restore depends on /usr/share/alsa being present.
If /usr
: sta...@vger.kernel.org
BugLink: https://bugs.launchpad.net/bugs/1328587
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index
** Package changed: pulseaudio (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks Sebastian! Based on what was written in the github report, I've
just commented out the module unloading that blueman does, built the
result and put it in a ppa here:
https://launchpad.net/~diwic/+archive/bluemantest
It is possible that blueman messes with more stuff so that just
=alsa_restore_go
GOTO=alsa_restore_end
IMO, it's better to use @mydatadir@ instead of @datadir@ here and...
Oops, sorry about that. Thanks for the review!
Attaching a fixup patch.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
** Patch added: 0001-alsactl-Fixup-test
As of tomorrow or the day after that, it will be available through this
channel: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry: IndentationError: expected an indented block (PulseAudio.py,
line 235)
Oops, then I screwed up. Please do not use the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
For the broader concept of PulseAudio and security, the native protocol
of PulseAudio was not built with security in mind, if you by security
mean that some connected clients should be able to do some things, and
other connected clients should be able to do other things. Right now, as
soon as you
/+source/pulseaudio/+bug/1283003
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth
** Summary changed:
- Ubuntu 14.04 NO audio (internal audio device not recognized Dummy Output)
+ [ABit AA8XE] Ubuntu 14.04 NO audio (internal audio device not recognized
Dummy Output)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reported-by: Stefano Statuti stefano.stat...@hotmail.it
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index d77745a..9c095fa 100644
Error -16 means EBUSY, or that some other application or daemon is
trying to use the device, so PulseAudio can't open it. Could you check
with this command:
sudo fuser -v /dev/snd/*
to see if anything else is trying to grab the mic input?
--
You received this bug notification because you are a
* Needs a team bug subscriber, for whomever will look after this in
Ubuntu
I suggest ubuntu-audio team.
* I'm seeing the following compile warning which seems troubling. Any
comment on that?
Looking at the actual code, it makes sense to rewrite as
for (j = 0; j 2; j++)
for (i = 0; i
And fixed upstream:
https://code.google.com/p/webrtc/source/diff?spec=svn2321r=2321format=sidepath=/trunk/src/modules/audio_processing/agc/analog_agc.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is there an actual problem with the current code or is it an
ignorable warning?
My gut says it's an ignorable warning, but I wouldn't bet on it - I'd
prefer to fix it using the code above. Want me to make a debdiff you can
sponsor?
--
You received this bug notification because you are a
Thanks for the bug report. It will be fixed in kernel 3.16.
** Changed in: alsa-driver (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319291
The rules are this way because the shared memory files are not app specific
and is possible for one app to access
another app's shared memory file.
The pulseaudio server actually uses the same shm file for all outgoing
memory blocks (i e, the common case is recording). So for best app
Oh, and btw, you can also spy on some other app's playback using the
pa_stream_set_monitor_stream command.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224751
Title:
pulseaudio should use
Well, since the Linux kernel and PulseAudio both are in main and officially
supported, but blueman is not, and one of the problems seems to be that blueman
unloads module-bluetooth-discover,
how well do things work *without* blueman?
I e, uninstall blueman and reboot and see how well the
Public bug reported:
Rationale:
This package contains an echo canceller which has a higher quality than the
speex echo canceller. If this package was in main, we could build PulseAudio
with webrtc echo canceller support. People in bug 1261666 are requesting this.
Also, Debian already does this.
Ok, first step is to get the webrtc dependency into main. Waiting for
ubuntu-mir team here: bug 1325859
** Changed in: pulseaudio (Ubuntu)
Status: Triaged = In Progress
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
--
You received this bug
Private bug reported:
Steps to reproduce:
1) start a youtube video and go to youtube fullscreen mode.
2) pause the video
3) wait until screensaver appears
4) input your password to unlock the screen.
5) The screen is now unresponsive. The mouse arrow moves, and Ctrl-Alt-F1
works, but otherwise
Hi,
It seems the bug reporter is not responding and I can't reproduce it
here, so I'm closing the bug. If you're the bug reporter and has the
time to help us resolve the bug together, feel free to reopen the bug.
Thanks!
** Changed in: unity-control-center (Ubuntu)
Status: Incomplete =
Upstream accepted the patch and I've just uploaded a new package to the ppa.
Can you help test it (when it has finished building)?
Thanks!
** Changed in: pulseaudio (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Hello I installed this package already web-audio-processing but when i use
: pactl load-module module-echo-cancel
aec_method=webrtc it return : Failure: Module initalization failed!!
Yes, this is because pulseaudio builds without webrtc support by
default. Just installing the package is not
sorry for the inconvenience, so i have to modify the source code or what,
how to rebuild pulseaudio with libwebrtc-audio-processing-dev?
Here's one of all links that explains how to rebuild a package:
http://www.cyberciti.biz/faq/rebuilding-ubuntu-debian-linux-binary-
package/
Also, before
/etc/init.d/mpd:# Should-Start: autofs $network $named alsa-utils pulseaudio
avahi-daemon
But there is no /etc/init.d/alsa-utils in the Ubuntu package.
Not exactly sure what this means, is this related to the relatively new daemon
functionality of alsactl?
So far we have avoided starting
Sorry, this probably was confusing to everyone except Dimitri and me.
The goal here is merely to make Ubuntu compatible to insserv. In
particular, any declared LSB dependency in our init.d scripts actually
needs to exist. But we don't want to change actual behaviour, i. e. in
this case we
pulseaudio assume surround21 is four channels
For PulseAudio, surround21 is now three channels. It's mapped to four
channels in alsa-lib, exactly which four channels is based on chmap
information from the kernel.
Does it mean that test with 5.1 downmix to surround21 ?
Yes I believe 5.1 would
/etc/init.d/mpd:# Should-Start: autofs $network $named alsa-utils pulseaudio
avahi-daemon
But there is no /etc/init.d/alsa-utils in the Ubuntu package.
Not exactly sure what this means, is this related to the relatively new daemon
functionality of alsactl?
So far we have avoided starting
Sorry, this probably was confusing to everyone except Dimitri and me.
The goal here is merely to make Ubuntu compatible to insserv. In
particular, any declared LSB dependency in our init.d scripts actually
needs to exist. But we don't want to change actual behaviour, i. e. in
this case we
Giuseppe Iuculano, thanks for testing. This patch should fix the device
busy error that Raymond found in your logs:
http://mailman.alsa-project.org/pipermail/alsa-
devel/2014-May/077157.html
I'm currently waiting for upstream review of this patch.
--
You received this bug notification because
Do you have updated packages to try?
Just pushed updated packages, happy testing!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1286021
Title:
2.1 surround support (userspace)
To manage
This is still an issue in Trusty. The PULSE_LATENCY_MSEC=50 workaround is
working.
Why is this set to Fix Released? Please set it back to Confirmed!
We fixed a bug in PulseAudio, and that caused this bug in Skype to
appear. We don't know why, and cannot fix Skype, since it is closed
source.
David: Can you set the Skype package back to Confirmed then?
The PULSE_LATENCY_MSEC=50 workaround is already deployed according to
comment #11, so I think that's fix released enough for me?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
301 - 400 of 4719 matches
Mail list logo
