Hi,
@Raymond, the jacks are not created as phantom because VT1708 uses jack
polling instead of unsol events. See function vt1708_build_controls in
patch_via.c
@Emil, are you having problems with both headphones and speaker, or is
one of them working okay?
--
You received this bug notification
Very interesting. However, I think you should first try doing a stereo
recording (e g with audacity) to verify that this is actually the case.
If there is phase inversion, you should be able to see large values at
the highest gain, and you should be able to listen to one channel at a
time and
@bfiller, something is wrong on the Android side, inside the proprietary
blob somehow. rsalveti to investigate further.
** Also affects: touch-preview-images
Importance: Undecided
Status: New
** Changed in: touch-preview-images
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
Should be fixed in 13.10, because with 1.0.27 this file is now in a
separate all-architecture package instead (libasound2-data).
** Changed in: alsa-lib (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Should be fixed in 13.10, because with 1.0.27 this file is now in a
separate all-architecture package instead (libasound2-data).
** Changed in: alsa-lib (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Should be fixed in 13.10, because with alsa-lib 1.0.27 this file is now
in a separate all-architecture package instead (libasound2-data).
** Changed in: alsa-lib (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
In 13.10 since a while back, enjoy!
** Changed in: alsa-lib (Ubuntu)
Status: Confirmed = 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/1178808
Title:
Update to 1.0.27
To
Should be fixed in 13.10, because with alsa-lib 1.0.27 this file is now
in a separate all-architecture package instead (libasound2-data).
** Changed in: alsa-lib (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Should be fixed in 13.10, because with alsa-lib 1.0.27 this file is now
in a separate all-architecture package instead (libasound2-data).
** Changed in: alsa-lib (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Should be fixed in 13.10, because with alsa-lib 1.0.27 this file is now
in a separate all-architecture package instead (libasound2-data).
** Changed in: alsa-lib (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Martin,
from where did you get libasound2:armel ? I don't think that's supported
by Ubuntu at all?
** Changed in: alsa-lib (Ubuntu)
Status: Confirmed = Incomplete
** Summary changed:
- package libasound2 1.0.25-1ubuntu10.1 failed to install/upgrade:
libasound2:amd64
I can confirm this error. It looks like there is some iterator running, and
when snd_config_search_definition runs, it changes the config tree, because
there is some hook that does this.
So the iterator's pointing to already freed memory.
The iterator is probably the one in the add_card
Sometimes a hook manipulates the config tree, which makes currently
running iterators point to freed memory. As a workaround, make two
copies, one for the iterators and another for the hooks.
BugLink: https://bugs.launchpad.net/bugs/1008600
Signed-off-by: David Henningsson david.hennings
There is already possibilities for indicator-sound to get notification
when a recording starts/stops.
** Changed in: pulseaudio (Ubuntu Saucy)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Should be fixed in 13.10, because with alsa-lib 1.0.27 these files are now
in a separate all-architecture package instead (libasound2-data).
** Changed in: alsa-lib (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Closing this bug because it is likely the result of installing
unofficial packages, home-built alsa library, or similar.
(And yes, I personally strongly recommend to avoid that page. But not
everyone shares my opinion on that.)
** Changed in: alsa-lib (Ubuntu)
Status: New = Invalid
--
Should be fixed in 13.10, because with alsa-lib 1.0.27 this file is now
in a separate all-architecture package instead (libasound2-data).
** Changed in: alsa-lib (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Closing as invalid due to the lack of responses to the last comment.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974963
This should now be fixed on Mako (Nexus 4) - you can use the sound
indicator to change the volume while you're on a call. Anybody wants to
verify?
Still not working on Maguro (Galaxy Nexus), I don't know why. It looks
like the relevant call to Android is working as expected.
** Changed in:
I'm closing this bug as invalid because I think it is a hardware error with one
machine:
1) We have two T430s in the lab and one of them has a working internal
microphone.
2) I installed the OEM pre-install image on the T430s that was not working,
and it didn't work there either.
I can also
@Joseph,
I was running 3.10.10 yesterday and didn't experience the bug, so I
*think* it's safe. Btw, do you have any script or documentation on how
to do a git bisect (in combination with Ubuntu packaging)? If so I can
probably do the bisect myself.
--
You received this bug notification because
That's a little weird - I have tested Nexus 4 today (with an image from a few
days ago), and I think the call volume is quite ok.
(But it's difficult to verify when you're calling yourself for the testing.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think there are two bugs here. The current code sets the voice volume
to maximum.
I'm currently looking into how to change that volume from PulseAudio.
However, if your problem is that it's difficult to hear the receiver,
it sounds like the volume needs to be higher than it is today. Can you
Sorry, turns out 3.11-rc3 and 3.11-rc5 are buggy as well, it's just more
difficult to reproduce than expected, because it does not happen every
time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And also found the bug on 3.11-rc1 now, although it took a while to
reproduce.
** Tags removed: needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218753
Title:
[HP 4520S, 3.11
diwic tvoss, kgunn anyway, my quick question was does it make any sense for
me to write a volume key up/down reader in PulseAudio directly and the answer
is no,
diwic because you want it to be kernel - mir - sound indicator -
pulseaudio instead
diwic right?
tvoss diwic, yup
--
You received
If you just set pin 0x15 to 0xc5 (OUT + HP), chances are that you can
have working headphone output by retasking pin 0x15 as a headphone - but
as raymond says, not easy to know without alsa-info (
https://wiki.ubuntu.com/Audio/AlsaInfo )
--
You received this bug notification because you are a
Side note: There might actually a better solution in newer kernels: if
you install the daily DKMS package (
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS ) you will get this
too.
Then edit /etc/modprobe.d/alsa-base.conf and add this line:
options snd-hda-intel jackpoll_ms=250
..then reboot
Change /usr/share/pulseaudio/alsa-mixer/paths/analog-output-
headphones.conf from:
[Jack Front Headphone]
required-any = any
[Jack Headphone]
required-any = any
to :
# [Jack Front Headphone]
# required-any = any
# [Jack Headphone]
# required-any = any
...restart pulseaudio (or the computer)
*** This bug is a duplicate of bug 1204434 ***
https://bugs.launchpad.net/bugs/1204434
** This bug has been marked a duplicate of bug 1204434
Volume up/down doesnt work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Mainline kernels tested so far:
3.10.10 - not buggy
3.11-rc1 - not buggy
3.11-rc7 - buggy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218753
Title:
[HP 4520S, 3.11 regression] Keyboard stops
** This bug is no longer a duplicate of bug 1204434
Volume up/down doesnt work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219057
Title:
volume up/down key is not working anymore with the new
3.11-rc3 - not buggy
3.11-rc4 - not buggy
3.11-rc5 - not buggy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218753
Title:
[HP 4520S, 3.11 regression] Keyboard stops working after S3
To manage
Public bug reported:
After S3 on this laptop, the keyboard is completely non-responsive. (E
g, Ctrl-Alt-F1 does not work) The trackpad is still working though.
I believe this is a kernel problem because
1) It started happening recently, i e, it was not a problem when running with
a 3.10
I believe Jason's confirmation in comment #10, in combination with
Mengdong's comment #8 - that there is a fixed mapping between pin nodes
and physical outputs - is enough to say that it's verification-done at
this point.
** Tags removed: verification-needed-raring
** Tags added:
** Summary changed:
- [dailer app] During a live call, there's no volume adjustment available
+ [dialer app] During a live call, there's no volume adjustment available
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After talking to YK, I'm closing this due to lack of responses. Feel
free to reopen if you would like to take this up again, and also have
the time to run kernel bisects etc.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because
A year later; Tanu is working on this upstream (from time to time) as
part of a bigger routing system change, but it's a complicated story and
progress is slow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
So far there have been no responses to comment #30. If anybody wants to
work with me - and have the time necessary to run tests etc - feel free
to start there. If not, I'm closing this bug, because there isn't more I
can do at this point.
Thanks.
** Summary changed:
- [soundnua]: hdmi
The higher mic boosts (on internal mic) are so noisy they're unusable
in practice.
BugLink: https://bugs.launchpad.net/bugs/1213820
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
Public bug reported:
Please don't triage this bug. It's for tracking purposes.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Tags: blocks
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210083
Title:
volume control does not work on Galaxy S2 and pulseaudio misbehaves
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/843587
Title:
Default sink/source is not always preserved
Hi, I'm closing this bug now, because nobody ever showed any screenshot
or similar (of the sound settings GUI) where IEC958 was showing. Feel
free to reopen if you provide such screenshot, preferrably under the
latest release of Ubuntu.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete
The higher mic boosts (on internal mic) are so noisy they're unusable
in practice.
BugLink: https://bugs.launchpad.net/bugs/1213820
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c |5 +
1 file changed, 5 insertions(+)
diff --git a/sound
** Summary changed:
- Another Thinkpad needs mic boost limit
+ A few more Thinkpads need mic boost limit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213820
Title:
A few more Thinkpads need mic
Public bug reported:
When running this tool under saucy, on my laptop:
$ laptop-detect
/dev/mem: Operation not permitted
$ echo $?
1
On 12.04, the /dev/mem: Operation not permitted error does not appear.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: laptop-detect 0.13.7ubuntu2
** 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/1213820
Title:
A few more Thinkpads need mic boost limit
To manage
This is from strace laptop-test under precise:
faccessat(AT_FDCWD, /dev/mem, R_OK) = -1 EACCES (Permission denied)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213922
Title:
/dev/mem:
This is from strace laptop-test under saucy:
faccessat(AT_FDCWD, /dev/mem, R_OK) = 0
geteuid() = 1000
faccessat(AT_FDCWD, /usr/sbin/dmidecode, X_OK) = 0
pipe([3, 4])= 0
clone(child_stack=0,
Sure, on root this is not an issue.
It's actually the other way around for /dev/mem, on precise it's
crw-r-- and on saucy it's crw-rw+ .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213922
Public bug reported:
This bug is for tracking purposes. Please do not triage.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic
The internal mic boost is so noisy on boosts 2 and 3 so they are
unusable in practice.
BugLink: https://bugs.launchpad.net/bugs/1213055
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c |3 +++
1 file changed, 3 insertions(+)
diff --git
This just cleans up the table, no functional changes.
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda
** 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/1213055
Title:
Limit mic boost on three Thinkpad machines
To manage
Hi Aditya2204,
The audio customisation done on this platform (on the preload install)
is to add a daily DKMS package - see
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS for how to do the same.
I can also confirm that we never enabled the subwoofer on Ubuntu for
this machine. Whether this is
@Adam, yeah, I noticed a while ago and reported it to operators at
Canonical, but it seems to be down still.
http://voices.canonical.com/user/128/ seems to be up though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Okay, how does PulseAudio determine if a client is confined or not?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211380
Title:
pulseaudio socket needs confined app restrictions
To manage
But the first one is probably relatively easy - libandroid-audiosystem-
asound2 (or some other package) already changes /etc/pulse/default.pa I
believe, so we should probably comment out the load-module module-udev-
detect line on all images that use audioflinger.
--
You received this bug
The question is if this is worth spending time on right now, given that
we're trying to get rid of audioflinger, and then all this logic will
change anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Jono,
I can't reproduce the failure here, using skype from the partner repo.
Did you try that version, and if so, what was the result?
** Changed in: pulseaudio (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Looking at the latest logs, I think we actually have two different bugs
to deal with.
One being the long system delays, which might or might not be related to
the graphics driver.
The other one being the audio driver. The regular underruns at 194 ms,
and the high interrupt count, both seem to
Public bug reported:
Looking at PulseAudio logs, it seems speech-dispatcher requests a total latency
of 1 ms, which in turn gives sub-ms latency inside the PulseAudio engine.
This causes unnecessary CPU consumption, or underruns. I understand that you
would want immediate feedback, but wouldn't
Hi Luke,
Could you test this patch and sponsor/upstream it if you find it not
causing any regression on your side?
** Patch added: debdiff.patch
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1208826/+attachment/3762472/+files/debdiff.patch
--
You received this bug
** Summary changed:
- Skype audio in Saucy broken
+ [Thinkpad T520] Skype audio in Saucy broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208485
Title:
[Thinkpad T520] Skype audio in Saucy
It's a separate issue. This issue is fixed since long ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/445849
Title:
Highpitched rattling like sound with 5.1 surround configuration
To manage
I did a small test on two machines I have here, one ALC888 + front mic
and one IDT92xx + internal mic. I tested recording with Capture at +30
dB and Mic Boost at 0 dB, then I tested recording with Capture at 0 dB
and Mic Boost at +30 dB.
For both machines, there was no significant difference in
potentially regress quality on those machines. Hopefully those are fewer, so
this is what we should default to.)
BugLink: https://bugs.launchpad.net/1085402
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
.../alsa/mixer/paths/analog-input-dock-mic.conf| 12 ++--
.../alsa
On 08/02/2013 03:34 PM, Arun Raghavan wrote:
On Fri, 2013-08-02 at 15:19 +0200, David Henningsson wrote:
Some HD-audio codecs (at least ALC269VB and ALC283) become quite noisy on
high Mic Boost levels. So e g, if there is a Mic Boost and a Capture
control, both ranging from 0 dB to +30 dB, you
@Andrew, hi, the skype developers are working on it, and provided the
below workaround. Start skype from a terminal, like this:
PULSE_LATENCY_MSEC=50 skype
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm, actually, if you use the latest version from the partner archive,
4.2.0.11-0ubuntu0.12.04.2, that now includes the workaround above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173073
Title:
Pushed upstream:
http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=e6051cdf8db554c0bbd4257959c37a7ecc9c10c5
** Changed in: pulseaudio (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So it's started correctly as my user but the directory has the wrong
permissions. Could this be a bug in lightdm?
At least it can't be a bug in PulseAudio, because PulseAudio shouldn't
have the permission to create that directory with those permissions,
right?
--
You received this bug
This patch set went into PulseAudio 4.0, which is now in Saucy.
** Changed in: pulseaudio (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/1076947
This bug fix went into PulseAudio 4.0, which is now released into Saucy.
** Changed in: pulseaudio (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [SRU Justification]
+ Several new hardware has either headset jacks or headphone-or-mic jacks,
where the system cannot detect what has been plugged in. E g, for such a
headset jack you can either plug in a headphone or a headset, but since the
system cannot tell which
SRU uploaded to precise-proposed, waiting for ubuntu-sru approval.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169143
Title:
Headset support on some Dell machines
To manage notifications about
Also happened in Saucy on a daily dist-upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098197
Title:
apport-gtk crashed with struct.error in read32(): unpack requires a
bytes object of
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
** Changed in: pulseaudio (Ubuntu Precise)
Assignee: (unassigned) = David Henningsson (diwic)
** Changed in: pulseaudio (Ubuntu Precise)
Status: New = In Progress
--
You received this bug
git describe --contains d240d1dc
v3.10-rc1~14^2~55
** 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/1169138
Title:
Headset
I believe this is fixed in the latest version of Ubuntu (both 13.04 and
13.10). Please reopen the bug if it isn't. Thanks!
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Looking at the latest logs, there are terrible delays, probably for
which we cannot blame the graphics driver.
( 61.711| 0.007) D: [alsa-sink-ALC889 Analog] alsa-sink.c: Expected sleep:
9.27ms, real sleep: 7.91ms (diff -1.36 ms)
( 61.920| 0.204) D: [alsa-sink-ALC889 Analog] alsa-sink.c:
To sum up our IRC discussions, a few things to try are:
- Install precise, verify it's still working correctly
- Upgrade to a raring kernel in precise (install
linux-generic-lts-raring-eol-upgrade and reboot) and see if this causes the
problem to appear
- If not, also upgrade to raring X
dmesg output before reproducing the issue has the following line that looks
suspicious to me:
[13828.248950] hrtimer: interrupt took 15288 ns
It seems a bit suspicious to me too, but 15288 ns = 0.015 ms, which
should not be enough to disturb the overall system latency.
[27622.091908]
While it would be interesting to see if jack detection works differently
if Legacy Front Panel Audio was disabled, it is unrelated to this
issue.
This issue is about when sound suddenly stops to work, and does so for
all output jacks.
--
You received this bug notification because you are a
One thing to check is what's causing the 10 ms system latencies here.
In a root shell, execute this command:
cd /sys/kernel/debug/tracing
echo wakeup_rt current_tracer
echo 1 tracing_on
Run for a minute or two, then
cat trace /tmp/trace.txt
echo 0 tracing on
Then attach /tmp/trace.txt
Hi,
I've made a special build in this PPA:
https://launchpad.net/~diwic/+archive/pulse-timing-test
Once it has finished building, could you try to give me a pulseaudio
verbose log? Try to reproduce the hangout/mumble/skype bug with the
pulseaudio package in this ppa, and the log enabled.
On 07/21/2013 12:45 PM, TEN wrote:
Also affects Ubuntu 12.04 LTS Precise Pangolin
This particular bug does *not* affect 12.04. Any HDMI audio problems
that happen in 12.04 is some other bug.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
--
You received this bug
On 07/21/2013 03:11 PM, TEN wrote:
David Henningsson (diwic) wrote:
This particular bug does *not* affect 12.04. Any HDMI audio problems that
happen in 12.04 is some other bug.
Any particular one, or should I open it?
You're probably best off opening a new bug.
--
David Henningsson
After some debugging on IRC, I'm still not sure what's causing the
problem. We should try a build with DEBUG_TIMING (in module-alsa-sink.c)
on for even more verbose logging in PulseAudio.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It looks like a transient error. Please try running sudo apt-get update
and then try again. Thanks.
** Changed in: pulseaudio (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry for the noise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201743
Title:
Headphone mic support for an Asus device
To manage notifications about this bug go to:
Public bug reported:
This bug is for tracking purposes, please do not triage.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: Invalid
** Tags: blocks-hwcert
: https://bugs.launchpad.net/bugs/1198030
Tested-by: Franz Hsieh franz.hs...@canonical.com
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_conexant.c | 79 +++-
1 file changed, 78 insertions(+), 1 deletion(-)
diff --git
** 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/1198030
Title:
System cannot detect external microphone
To manage
** 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/1195597
Title:
Yet another Dell headset
To manage notifications about this
** 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/1195636
Title:
Headset support on two more Dell machines
To manage
@Onestone, only if it is important enough - see
https://wiki.ubuntu.com/StableReleaseUpdates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171344
Title:
ImportError: No module named apport
To
Public bug reported:
This bug is for tracking purposes only, please do not triage.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New = In Progress
** Changed in: linux
Add two more machines that need quirks for headset mics to work.
Tested-by: Shawn Wang shawn.w...@canonical.com
BugLink: https://bugs.launchpad.net/bugs/1195636
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c |2 ++
1 file changed, 2
701 - 800 of 4719 matches
Mail list logo
