** Attachment added: alsa-info.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1096789/+attachment/3476010/+files/alsa-info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096789
://bugs.launchpad.net/bugs/1096789
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c | 31 ++-
1 file changed, 30 insertions(+), 1 deletion(-)
I know this is a copy-paste, but I didn't really find a better and more
condensed way
Sorry for the misleading subject in the previous email. There is only
one patch.
On 01/07/2013 10:51 AM, David Henningsson wrote:
The mute LED is in this case connected to the Mic1 VREF.
The machine also exposes the following string in BIOS:
HP_Mute_LED_0_A, so if more machines are coming
Waraqa, you're probably suffering from a different bug. Please file a
new bug with the ubuntu-bug audio command and if time permits, I or
somebody else will look at it. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[removing stable from CC]
On 01/07/2013 11:49 AM, Takashi Iwai wrote:
At Mon, 7 Jan 2013 10:51:29 +0100,
David Henningsson wrote:
The mute LED is in this case connected to the Mic1 VREF.
The machine also exposes the following string in BIOS:
HP_Mute_LED_0_A, so if more machines are coming
://bugs.launchpad.net/bugs/1096789
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_realtek.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 6ee3459..71ae23d
On 01/04/2013 09:19 PM, Clemens Ladisch wrote:
David Henningsson wrote:
this patch resolves the issue for him. It also leaves a message
in the log:
snd-usb-audio: probe of 1-1.1:1.1 failed with error -5
I'd guess this is for an interface not claimed by the driver but
without an explicit
Looking a bit at the snd_usb_fasttrackpro_boot_quirk function, it calls
usb_driver_set_configuration, which has the following comment:
* Device interface drivers are not allowed to change device configurations.
* This is because changing configurations will destroy the interface the
*
** Patch added:
0001-ALSA-usb-fix-race-in-creation-of-MAudio-Fast-track-p.patch
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1095315/+attachment/3473909/+files/0001-ALSA-usb-fix-race-in-creation-of-MAudio-Fast-track-p.patch
--
You received this bug notification because you are
@Raymond, I think your observation in comment #88 is correct, would you
mind writing a patch for that, or do you want me to do it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886975
Title:
@c4pp4:
Still trying to get 1) through upstream...
The following dkms package contains patch for 1) only, on top of git
master. Can you just install it, reboot, and make sure that the 1) click
is gone. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: alsa-hda-dkms_0.1_all.deb
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/886975/+attachment/3473950/+files/alsa-hda-dkms_0.1_all.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@peter weber, I'm not sure what you're referring to is the same bug,
since the controller chips are different.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088957
Title:
[ThinkPad T420]
Public bug reported:
Where: Raring and up
What: both sources and binaries
Why:
- It has been broken since karmic (see bug 378675)
- The person who wrote it (Toby Smithe) says, in the same bug: I recommend
that asoundconf-gtk be removed; it has been broken for a long time now, and its
last
a more elegant solution?
BugLink: https://bugs.launchpad.net/bugs/1095315
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/usb/quirks.c |8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
...oh, and if you end up taking this patch as it is, you should probably
I'm suspecting that ,0,0 records from SPDIF in your case and ,1,0 from
analog. If so we could just try ,1,0 first and then ,0,0, i e the string
becomes hw:%f,1,0 hw:%f,0,0
The question is if it is the other way around for other Fasttrack Pro
devices, so this would regress behaviour for them. It
On 12/19/2012 11:38 AM, Takashi Iwai wrote:
At Wed, 19 Dec 2012 11:34:46 +0100,
David Henningsson wrote:
On 12/19/2012 11:24 AM, Takashi Iwai wrote:
At Wed, 19 Dec 2012 09:44:47 +0100,
David Henningsson wrote:
This reverts commit 697c373e34613609cb5450f98b91fefb6e910588.
The original
Good idea. Bug subscriber now added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1087201
Title:
[MIR] sbc
To manage notifications about this bug go to:
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076840
Title:
[CS4213, Dell Inspiron 3420] Internal speaker does not show up in
Public bug reported:
We're being advised by Intel to include the following patch for the
Quantal kernel, to fix a Haswell/Sharkbay HDMI/DP audio issue. As there
are no sharkbay machines out there yet, and the patch contains a if
codec-vendor_id == 80862807 I assume this will cause no regressions.
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
We're being advised by Intel to include the following patch for the
Quantal kernel, to fix a Haswell/Sharkbay HDMI/DP audio issue. As there
are no sharkbay machines out there yet, and the patch contains a if
codec-vendor_id
I don't have the hardware, so can't give logs.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1095242
Title:
Sharkbay HDMI audio
It looks like now you don't get a dummy device (but the real device),
but the speakers are simply muted. Could you check that if you're using
the speakers, that you have Speakers selected in the sound settings
and that it is not muted?
--
You received this bug notification because you are a
I don't understand why sound is such a tough issue on Linux/Ubuntu.
The number one reason is probably that the hardware is so diverse,
perhaps even more than other areas and components.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ok, back. It is easier to try to examine the clicks one at a time. So in
priority order, is this correct:
1) The biggest clicks are fixed by the patch in comment #71
2) To second click needs these two to fix:
+ snd_hda_codec_set_power_to_all(codec, fg, power_state, false);
when transitioning to
With device-strings = hw:%f,1,0 in my maudio-fasttrack-pro.conf it
works now.
So, first it was hw:%f,0,0, then it became hw:%f,0,0 hw:%f,1,0 and
now you're proposing we change it to just hw:%f,1,0, is that correct?
What I'm afraid of is that there might be more than one model out there,
and
c4pp4, thanks for your work so far. FYI, I'll be back from holiday at
2nd of Jan 2013. (And depending on workload, might be a few days extra
until I'll have time to look at your patches)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This reverts commit 697c373e34613609cb5450f98b91fefb6e910588.
The original patch was meant to remove clicking, but in fact caused even
more clicking instead.
Thanks to c4pp4 for doing most of the work with this bug.
BugLink: https://bugs.launchpad.net/bugs/886975
Signed-off-by: David
On 12/19/2012 11:24 AM, Takashi Iwai wrote:
At Wed, 19 Dec 2012 09:44:47 +0100,
David Henningsson wrote:
This reverts commit 697c373e34613609cb5450f98b91fefb6e910588.
The original patch was meant to remove clicking, but in fact caused even
more clicking instead.
Thanks to c4pp4 for doing
Tim chen, I need you to verify on Precise, with PulseAudio from the
proposed repository.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076840
Title:
[CS4213, Dell Inspiron 3420] Internal speaker
And, if it does not work, please post the output of pacmd ls and an
alsa-info from when you're trying to use the internal speaker and it
doesn't show up. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@c4pp4, thanks for your reply.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886975
Title:
[Thinkpad R61i/T61] Lenovo sound chip Conexant CX20549 Venice doesn't
work correctly.
To manage
Oops, wanted to write something more in that comment:
If you like, you can join the discussion I'm having with upstream (cc:ed
into this bug). All I need is your email address to cc you in and you
can discuss with Takashi (the upstream maintainer) and me directly.
--
You received this bug
Thanks for your assistance. To be honest, I'm a little surprised that it
happened. Did it disappear on both input and output tabs? If it's still
around on the other tab, maybe you can use that tab to work around the
bug and switch profile there.
--
You received this bug notification because you
Here's the commit for reference.
http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=commit;h=54c2a89f60fd71b924d0f848ac892442951401a6
So yes, it should definitiely in 3.5 based kernels. It must be something
different. Could you start output that is broken (i e to both HDMI and
c4pp4, okay, let me know if you find anything. But if reverting the
commit that caused the extra clicks causes no other regressions then we
should probably revert it as a first step, and after that see if you can
find a way to avoid the initial click too?
--
You received this bug notification
On 12/12/2012 06:15 PM, Takashi Iwai wrote:
At Wed, 12 Dec 2012 18:02:04 +0100,
David Henningsson wrote:
The bug reporter reports that setting the speaker pin to
D3 before turning off its pinctl fixes the clicking noise on
powersave for Thinkpad T61.
Thanks to c4pp4 for doing most
@Luis, Tim, both precise and quantal require verification at this point:
* For quantal, the kernel is in proposed
* For precise, pulseaudio is in proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Infinite loop of:
on_control_active_input_update - active_input_update -
gtk_tree_selection_select_iter - signal (changed, on treeview) -
on_input_selection_changed - gvc_mixer_control_change_input -
gvc_mixer_control_set_default_source - signal (ACTIVE_INPUT_UPDATE) -
I want to fix this for 13.04 / Gnome 3.8.
Anyway, should this happen again, it's easier to fix from the
pavucontrol application than tdbtools.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071561
Hi,
I remember fixing a kernel bug that could cause this behavior. Are you running
the latest kernel (3.2.0-34), and if not, could you try it and see if it is
fixed?
** Changed in: gnome-control-center (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you
@luis, this one seems to have come from upstream stable, is verification
really necessary?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/359361
Title:
ALSA SPDIF Digital output clipping / crackling
** Package changed: pulseaudio (Ubuntu) = alsa-driver (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067434
Title:
Sound output device keeps changing when using headphones
To manage
Also, how come this bug is half a year old and it has not even been
assigned to any of the ubuntu developers yet?
Roughly,
1) There are not enough Ubuntu developers to deal with all bugs.
2) There can be many root causes to why an underrun happens. I e, there
might be ten different reasons
Assignee: David Henningsson (diwic)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = David Henningsson (diwic)
** Changed in: linux (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs
Hi Tim,
Could you still test the pulseaudio version in 12.04? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076840
Title:
[CS4213, Dell Inspiron 3420] Internal speaker does not show up in
It's necessary to move the line .reboot_notify = conexant_reboot_notify,
from static const struct hda_codec_ops conexant_patch_ops = {
to static const struct hda_codec_ops cx_auto_patch_ops = {
Good catch! Fixed.
snd_hda_codec_set_power_to_all(codec, codec-afg, AC_PWRST_D3, false);
I think
://bugs.launchpad.net/bugs/886975
Signed-off-by: David Henningsson david.hennings...@canonical.com
---
sound/pci/hda/patch_conexant.c | 36
1 file changed, 32 insertions(+), 4 deletions(-)
Note: c4pp4 pointed out that in his case, only the speaker needed to go to
D3
I'm closing this issue as natty is no longer supported and it does not
seem to occur on later versions. I'm sorry we never had the
time/knowledge to fix it properly.
** Changed in: pulseaudio (Ubuntu Natty)
Status: New = Won't Fix
** Changed in: pulseaudio (Ubuntu)
Status:
Hi Raymond,
Your patch only affects the state of PCM when PulseAudio is muted, so it is
unlikely to fix this particular problem.
On other systems it might prevent proper muting or powersaving, so I believe it
should not be applied.
--
You received this bug notification because you are a
** Summary changed:
- Lenovo sound chip Conexant CX20549 Venice doesn't work correctly.
+ [Thinkpad R61i] Lenovo sound chip Conexant CX20549 Venice doesn't work
correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- [Thinkpad R61i] Lenovo sound chip Conexant CX20549 Venice doesn't work
correctly.
+ [Thinkpad R61i/T61] Lenovo sound chip Conexant CX20549 Venice doesn't work
correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi c4pp4 and first of all, thanks for your endurance with this issue.
To have this fixed once and for all, we need to get this into upstream.
Based on your comments, I'm trying to figure out which pieces make sense
to send to upstream. Your code is based on making a new model which is
a way we're
** Package changed: alsa-driver (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed = 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/1033233
Title:
I've rewritten the part of your patch that fixes the click so that it looks
more like upstream would want it (I believe).
Could you help testing it? If it works, I will send this version to upstream
for inclusion.
It should be applied to the daily DKMS builds. If you like, I can make a
custom
Hi!
This is not one bug; it is many different bugs. The bugs usually need to
be fixed once for every type of machine.
https://wiki.ubuntu.com/Audio/SameHardware
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
fluidsynth suggests an extremely low latency by default; if you just
want to play back a midi file, please use e g -z 4096 as parameter to
fluidsynth.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[ 1653.495497] hda-intel: spurious response 0x40:0x3, last cmd=0x30270503
is definitely a driver bug.
Is this a regression from quantal or did you see the same behaviour in
previous Ubuntu releases?
** Package changed: pulseaudio (Ubuntu) = alsa-driver (Ubuntu)
** Summary changed:
-
@jhoectl, with upstream I mean the vanilla linux kernel maintained by
Linus.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/886975
Title:
[Thinkpad R61i/T61] Lenovo sound chip Conexant CX20549
@Chris, okay, good.
We should first try the latest upstream code according to
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS to see if it's been
already fixed again. If so, it will be fixed with the 3.8 kernels coming
to 13.04 a few weeks from now, so maybe that's okay.
If it is not fixed, or
Sure, I don't deny that there's a bug here. There's also bug 751265 for
the VLC - PulseAudio problems.
** Summary changed:
- [GA-MA770T-UD3P, Realtek ALC888] Distorted crackling noise when using
FluidSynth
+ [GA-MA770T-UD3P, Realtek ALC888] Distorted crackling noise when used with low
latency
Excellent, thanks Joel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/416190
Title:
Pulseaudio produces overdriven audio on mono downmix (e g to
Plantronics DA40 adapter)
To manage notifications
Please try the latest upstream drivers according to
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
before trying something directly from Realtek. We need to know if it's fixed
upstream or if we actually need to try picking something from the Realtek
drivers.
--
You received this bug
Okay, so for those of you who are still suffering from this bug on 12.04 with
all updates installed, there is now another option:
1) Enable proposed as instructed in comment #138
2) Install the latest HDA driver according to
https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS
Reboot and test. I
Public bug reported:
While calling Arun, a gstreamer/pulseaudio hacker, the call fails with
an error message. /usr/lib/empathy/empathy-call shows the errors below.
According to Arun, this is due to empathy linking against gstreamer
0.10, but also against some other library, which in turn links
Public bug reported:
Rationale: This is needed before we can update PulseAudio to 3.0, because sbc
is a new build dependency.
The code used by PulseAudio was previously in PulseAudio, but has been factored
out to a separate library.
Security wise, this is a new package, so there is no
I don't have the actual headset in question, but my USB headset can be
put in a mono mode. I can not reproduce the issue with PulseAudio
1:1.1-0ubuntu15.2. So I think it's fixed, but it would be nice with a
second opinion from Joel, Liz, Thomas or anyone with the DA40/DA45
headset. Could you
** Description changed:
- [SRU Justification (Quantal)]
+ [SRU Justification]
Impact: The internal speaker does not show up in the sound settings,
which causes this to block certification.
Test case: With the affected machines, open sound settings without
headphones plugged in. If
Released
** Changed in: pulseaudio (Ubuntu Precise)
Status: New = In Progress
** Changed in: pulseaudio (Ubuntu Precise)
Assignee: (unassigned) = David Henningsson (diwic)
** Description changed:
[SRU Justification]
Impact: Internal Mic not visible in sound settings
Test case
** Changed in: pulseaudio (Ubuntu Precise)
Status: New = In Progress
** Changed in: pulseaudio (Ubuntu Precise)
Assignee: (unassigned) = David Henningsson (diwic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Also affects: pulseaudio (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu Quantal)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
.
The instructions at https://wiki.ubuntu.com/Core clearly says to add the
local user to the sudo group. This makes no sense if the sudo package is
not part of Ubuntu Core, so either the instructions are broken, or
Ubuntu Core is broken because it should have included the sudo package?
--
David
The same patch should be applied to our quantal tree, but for precise we
need something different. For 12.04, could you please try the following:
Edit /lib/udev/rules.d/90-pulseaudio.rules, and add the following line:
ATTRS{subsystem_vendor}==0x1028, ATTRS{subsystem_device}==0x0553,
** Description changed:
This is due to the Internal Speaker Phantom Jack kctrl not being
created.
the same issue occurs in the following sysyems:
- cid:201202-10591, Dell Inspiron 3420
- cid:201202-10590, Dell Inspiron 3420
- cid:201202-10593, Dell Vostro 2420
+ cid:201202-10591, Dell
Since the fix for 12.04 is quirking, I'll need to know if there are any
more machines with the similar symptoms before trying to fix it in
PulseAudio, so I catch 'em all.
** Description changed:
- This is due to the Internal Speaker Phantom Jack kctrl not being
- created.
+ [SRU Justification]
+
Hi Lonnie,
I'm currently discussing this upstream, and confirmed it is a
regression. Hopefully it'll be fixed in PulseAudio 3.0, which is going
to be used in Ubuntu 13.04.
** Changed in: alsa-driver (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are
= Invalid
** Changed in: pulseaudio (Ubuntu Raring)
Status: New = Invalid
** Changed in: pulseaudio (Ubuntu Precise)
Status: New = In Progress
** Changed in: pulseaudio (Ubuntu Precise)
Assignee: (unassigned) = David Henningsson (diwic)
** Description changed:
[SRU
merged upstream for 3.8.
** 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/1082357
Title:
USB Headset has Speaker volume
I uploaded the SRU for precise at Nov 9th - and this patch is in there -
but it's been sitting in queue since:
https://launchpad.net/ubuntu/precise/+queue?queue_state=1queue_text=pulseaudio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Kambiz,
Next step will be to verify that you're also having a regression from
11.10, like the original poster. Can you boot a live-CD of 11.10, verify
that the headset mic is working there, and attach an alsa-info from when
the mic is working? Thanks.
--
You received this bug notification
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890867
Title:
pulseaudio crashed with SIGABRT in pa_memimport_free()
To manage notifications about
*** This bug is a duplicate of bug 1078543 ***
https://bugs.launchpad.net/bugs/1078543
** This bug has been marked a duplicate of bug 1078543
[raring] Pulse audio fails to start with error 'Failed to open module
module-esound-protocol-unix: file not found'
--
You received this bug
:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770T-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770T-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA770T-UD3P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: David Henningsson (diwic
Public bug reported:
Reason for sync request is that it is a new build dependency for
PulseAudio. It needs to go in main, but I understand the process is to
sync it into universe first, and then to a MIR to promote it to main.
** Affects: ubuntu
Importance: Undecided
Status: New
Thanks for the quick handling Benjamin!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1081967
Title:
Please sync sbc 1.0-2 from Debian Experimental
To manage notifications about this bug go to:
We found a new codec ID 292, and that just a simple quirk would enable
sound output/input on this ALC292 chip.
BugLink: https://bugs.launchpad.net/bugs/1081466
Cc: sta...@vger.kernel.org
Tested-by: Acelan Kao acelan@canonical.com
Signed-off-by: David Henningsson david.hennings
** 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/1081466
Title:
Missing support for Realtek ALC292
To manage notifications
** Summary changed:
- Audio Interface disappears and no audio output
+ [CS4213, Dell Inspiron 3420] Internal speaker does
** Summary changed:
- [CS4213, Dell Inspiron 3420] Internal speaker does
+ [CS4213, Dell Inspiron 3420] Internal speaker does not show up in Sound
settings
** Description
Patch committed upstream in Takashi's tree.
** Changed in: linux (Ubuntu)
Status: Incomplete = 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/1076840
Title:
[CS4213, Dell
If this array is not cleared, the jack related code later might
fail to create Internal Speaker Phantom Jack on Dell Inspiron 3420 and
Dell Vostro 2420.
BugLink: https://bugs.launchpad.net/bugs/1076840
Cc: sta...@vger.kernel.org (3.6+)
Signed-off-by: David Henningsson david.hennings
Nov 21 12:03:40 eldon pulseaudio[3855]: [pulseaudio] card.c: Changed profile of
card 6
alsa_card.usb-Cambridge_Audio_Cambridge_Audio_USB_Audio_1.0_-00-C10 to off
Nov 21 12:03:40 eldon pulseaudio[3855]: [pulseaudio] module-card-restore.c:
Storing profile for card
This is a bug 946232 duplicate essentially. Annoyingly, I recently did a long
overdue PulseAudio SRU upload which is waiting for approval by the SRU team,
but this machine is not in that list...
It is fixed in Quantal,
and will also be fixed in Precise if 1) you have the PulseAudio that's
Public bug reported:
We need a simple quirk to enable it.
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)
Status: New
On 11/07/2012 09:36 AM, Takashi Iwai wrote:
At Wed, 7 Nov 2012 09:22:33 +0100,
David Henningsson wrote:
On some of the PantherPoint HDMI machines we currently enable, we're seeing
trouble with unsol events, i e detecting monitor presence, especially when
on battery and after suspend/resume
I think the problem here is that pulseaudio is declared Multi-Arch:
foreign, where in fact it should not be multi-arch at all (only
libpulse and its dependencies should be multi-arch: same, which they
already are).
I don't know how pulseaudio and pulseaudio-esound-compat end up with
different
@Stefan, make sure you have selected Microphone and not Line In in
the sound settings dialog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078924
Title:
[Latitude E6520, IDT 92HD90BXX, Black Mic,
What jack do you actually plug your subwoofer into? Is it the SPDIF
jack?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1040873
Title:
[N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound
Hi Kambiz,
Something is strange here - according to your hda-jack-sense-test output
there is a Pink Mic and pin 0x12, but according to your alsa-info,
there's nothing at pin 0x12.
Are you sure that
1) these two reports came from the same machine,
2) that is actually is a headset jack, i e, both
I was asked to come up with a hacky workaround, so here it is:
Add a file /usr/bin/unmute-sink, and make sure it's executable, with
this contents:
#!/bin/sh
pactl set-sink-mute 0 0
(You might need to change the first 0 to 1, or use the sink name, if you
have more than one sound card)
Add a
Raring debdiff
** Patch added: raring.debdiff
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad0.10/+bug/973014/+attachment/3434302/+files/raring.debdiff
** Description changed:
+ Sponsors: Please start by uploading raring.debdiff
+
SRU Justification (for both Quantal and
1101 - 1200 of 4813 matches
Mail list logo