Please run amixer sset 'Capture Source' 'Internal Mic' or 'Headset Mic'
first, make sure the capture source is not headphone mic,
then plug the headset/earphone, choose correct option from the pop-up
dialogue.
thx.
--
You received this bug notification because you are a member of Desktop
Please refer to https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1875249/comments/10
--
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/1873384
Title:
Headphone has no
I just found a Dell laptop and installed the ubuntu 20.04 on it.
After plug the headset, there is a pop-up dialog shows, there are 3
options let users choose: headphones (if users plug a headphone),
headset (if users plug a headset, here headset means headphone + mic,
just like the headset for
So @Douglas,
Your machine also has internal mic, so the Capture source is either
internal mic or headset-mic, so in what situation it is headphone-mic?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Yes, #3 sounds sensible. it is worth having a try.
--
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/1875989
Title:
[276812G, Conexant CX20561 (Hermosa), Speaker, Internal]
The driver looks good:
APLAY
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: CX20561 Analog [CX20561 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: CX20561 Digital [CX20561 Digital]
Subdevices: 1/1
Subdevice #0:
Please try previous kernel like the one in the 18.04, that means old
kernel + 20.04 rootfs, does the noise disappear?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1875828
Title:
It is better now with v2, but the driver fails at the machine driver
initialization stage:
[3.349857] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported
HDAudio/iDisp configuration found
[3.349860] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with
error -22
--
You
Please test v3 kernel:
https://people.canonical.com/~hwang4/25skipi915/v3/
I guess v3 kernel will work successfully, after boot up, you could run
alsa -l to check if there is valid sound card.
and pulseaudio will have an error on your machine, so if the kernel has
no error, please backup
For example, to install mainline kernel 5.2-rc6:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc6/
or mainline kernel 5.0: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065
will fix it in the ubuntu pulseaudio.
** This bug has been marked a duplicate of bug 1876065
After unplug headphones and plug them again no sound can be heard
--
You received this bug notification
[ 14.652221] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0
This message is common on all machine with sof driver, so we could ignore it.
According to dmesg in the #15, the kernel driver already worked. you
could run "aplay -l" to check (sorry, not alsa -l).
So after update
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065
Will fix it in the ubuntu pluseaudio.
** This bug has been marked a duplicate of bug 1876065
After unplug headphones and plug them again no sound can be heard
--
You received this bug notification
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065
will fix it in the ubuntu pulseaudio.
** This bug has been marked a duplicate of bug 1876065
After unplug headphones and plug them again no sound can be heard
--
You received this bug notification
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065
will fix it in the ubuntu pulseaudio.
** This bug has been marked a duplicate of bug 1876065
After unplug headphones and plug them again no sound can be heard
--
You received this bug notification
Looks like the fix of this bug (https://bugs.launchpad.net/oem-
priority/+bug/1869819) introduced this regression.
--
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/1876065
Title:
Please take a look at #1876065, maybe they have the same rootcause. But
you mentioned pulseaudio 1:13.0-1ubuntu1.1, so I didn't duplicate your
bug to that one.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Looks like this SRU introduced a regression in the focal and a couple of
related bugs are filed by ubuntu 20.04 users (at least most of Dell
machines will be affected):
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065
Please remove snd_hda_intel: dmic_detect=0, you must set dmic_detect=0
somewhere.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1874925
Title:
Comet Lake PCH-LP cAVS (Audio,
@Eric,
please run "sudo grep dmic_detect /etc/* -r" to find where set the
dmic_detect=0, then remove it, and install the latest 5.3 kernel
(5.3.0-46 or later), then reboot and upolad the output of dmesg.
thx.
--
You received this bug notification because you are a member of Desktop
Packages,
Is the package timidity installed on your machine? If yes, please remove
it. "sudo apt -r timidity;reboot"
--
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/1879054
Title:
No sound
This is the testing kernel based on the -26 kernel:
https://people.canonical.com/~hwang4/25skipi915/v4/
And don't forget the Hdmi.conf if kernel has no obvious errors or failures on
audio.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Tags added: originate-from-1877247 somerville
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1874698
Title:
[OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
The last resort:
I built a kernel from the Intel audio driver tree, please test it
https://people.canonical.com/~hwang4/25skipi915/v5/, please keep using
the Hdmi.conf from v4.
If that doesn't work, please file a bug against Intel sof kernel:
https://github.com/thesofproject/linux/issues/new,
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065
This is a duplicate bug of this oneļ¼
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065
** This bug has been marked a duplicate of bug 1876065
After unplug headphones and plug them again
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065
Please use the testing ppa in the #1876065 and verify if it could fix
the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
kernel already has a valid sound card, but pulseaudio doesn't have.
Please edit /usr/lib/systemd/user/pulseaudio.service
comment out the existing line starting with ExecStart and add a new one
ExecStart=/usr/bin/pulseaudio - --log-target=file:/tmp/a.txt
reboot
upload the /tmp/a.txt
thx.
5.3.0-43 is in -proposed now, please test -43 kernel.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1868085
Title:
Bug related to the new kernel version 5.3.0-42-generic
Status
@Jesko,
-42 has a regression on sof audio driver, please wait for the coming -43
kernel.
thx.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1867774
Title:
PCI/internal sound
The kernel 5.3.0-43 is in the -proposed, please use this kernel instead
of -42 kernel.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1867474
Title:
[Dell Vostro 5590]
Please manually install alsa-ucm-conf package and reboot.
This package will be put into the 20.04 image soon.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1868330
Title:
5.3.0-42.34-generic has regression, please try with 5.3.0-43 kernel.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1868319
Title:
PCI/internal sound card not detected
Status in
*** This bug is a duplicate of bug 1868319 ***
https://bugs.launchpad.net/bugs/1868319
Please refer to #1868319.
thx.
** This bug has been marked a duplicate of bug 1868319
PCI/internal sound card not detected
--
You received this bug notification because you are a member of Desktop
You could test with the latest mainline kernel, let us see if it is
kernel issue or userspace issue.
thx.
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc6/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Mar 21 18:57:22 user-ThinkPad-X1-Carbon-7th
chromium_chromium.desktop[4806]:
[4806:4806:0321/185722.248501:ERROR:pulse_util.cc(300)] pa_operation is
nullptr.
Maybe the chromium is not compatible with the new pulseaudio (13.99)?
The api is changed in the PA-13.99 while the chromium still uses the
*** This bug is a duplicate of bug 1864061 ***
https://bugs.launchpad.net/bugs/1864061
Please try 5.3.0-43 kernel.
** This bug has been marked a duplicate of bug 1864061
PCI/internal sound card not detected
--
You received this bug notification because you are a member of Desktop
please install a higher version kernel like 5.4.0-28/29 first, boot with
the new kernel, then sudo dpkg -r --force-all linux-image-
unsigned-5.4.0-26-generic, install the v4 testing kernel to do the test.
I installed the v4 testing kernel on my machine, there is no errors:
It is not easy to debug without hardware, so the best way is to report
this issue to https://github.com/thesofproject/linux/issues/new
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
On your machine, there is a internal mic connected to the codec, so
please try with "snd_hda_inte.dmic_detect=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/1879462
Title:
"snd_hda_intel.dmic_detect=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/1879462
Title:
[Dell Inspiron 3790] pulseaudio module-alsa-card failed to find a
working profile
This is a linux kernel bug instead of a pulseaudio bug, there is no
dmic connected to the PCH, so the kernel should uses the legacy hda
driver on this machine.
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Hu
Please uninstall all oem-audio-* packages then reboot.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1879869
Title:
PCI/internal sound card not detected
Status in alsa-driver
When the bluetooth headphone is trying to connect on the 2nd time (will
fail), could you see any error message from syslog?
open a terminal and run 'tail -f /var/log/syslog', then reconnect the
bluetooth headphone.
--
You received this bug notification because you are a member of Desktop
We have a private bug which is similar to 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/1871329
Title:
No "Select Audio Device" panel when plugging headphones, and no sound
We have a private bug which is similar to it. #1875597
--
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/1871329
Title:
No "Select Audio Device" panel when plugging headphones, and
snd_use_case_parse_ctl_elem_id() is defined in the latest libasound2
(>=1.2.1), maybe reinstall the libaousnd2 and pulseaudio could help.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Did the internal mic work before?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1876555
Title:
Apps cannot retrieve internal mic input
Status in alsa-driver package in Ubuntu:
So if you only plug the monitor and don't plug the home theater, and
choose the output to hdmi monitor, suspend and resume, does the output
still on hdmi monitor?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Looks like it is a kernel driver's problem.
Could you install the 18.04's kernel under 20.04 to test?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1887210
Title:
USB DAC/AMP
Please plug in the headphone, then run alsa-info.sh and upload the alsa-
info.txt
BTW, what do you mean "Sound works for a while, then breaks"?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
What I saw is the hdmi-port0 (monitor) is resumed earlier than hdmi-
port1 (home theatre) and hidmi-port0 has higher priority than hdmi-
port1, so the profile of hdmi-port1 will not be active and the sink of
hdmi-port1 will not be created after resume. (not 100% sure)
If you could not switch the
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1894833
Title:
[Dell XPS 15 7590, Realtek ALC3266, Mic, Internal]
When you have time please redo the test of comment #12. But this time,
don't need to run tail -f ~/pa.log that early.
After you choose 5.1-surround from gnome-setting, run tail -f ~/pa.log,
then press "enter" button for a couple of times, this will produce empty
lines on the terminal. Then
Please test this kernel: https://people.canonical.com/~hwang4/hstbtn/
to install the testing kernel: sudo dpkg -i linux-image-xxx.deb
reboot and run sudo evtest, then upload the output log of 'sudo evtest'
to uninstall the testing kernel: sudo dpkg -r linux-image- (5.9-rc3)
reboot
--
You
This depends on the hardware design first, if the audio jack and the
codec supports it or not.
Then it depends on the kernel driver. With the ubuntu 20.04, the
userspace part is OK to support the headset button, since I already
verified it on the Leonvo x1c7.
I will build a testing kernel, let
@JasonSome,
So far, the linux kernel (audio driver) only supports the headset button
on some specific machines like Lenovo X1C7.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
I guess your bug is similar to this one:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598
Could you please do a test:
edit the /usr/share/pulseaudio/alsa-mixer/paths/hdmi-output-0.conf and
hdmi-output-1.conf, change the priority in 0.conf to 58 and change the
priority in 1.conf
Do you mean even did the change of #2, the output device still changes
to internal analog audio after sleep? Before sleep, you select the hdmi-
output-2 manually?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Could you please test this kernel:
https://people.canonical.com/~hwang4/testdetect/
--
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/1893846
Title:
Sound doesn't switch to
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1886626
Title:
after login to gnome with snd_hda_intel
The patch of #17 is reverted from upstream, and the patch is cced to
stable, it will be in the ubuntu kernel sooner or later.
thx.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
And could you please test this kernel:
https://people.canonical.com/~hwang4/testdetect/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1893566
Title:
[MS-7A40, Realtek ALC887-VD,
According to the log of #18, looks like after resuming, the pulseaudio
tried to set the pcm to 5.1 channels on the hdmi-surround-extra1, but
failed:
D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(6) failed: Invalid
argument
D: [pulseaudio] alsa-util.c: Trying hdmi:2,1 without
Weird, even you plug the headphone before booting, the headphone is
still not recognized. I don't know why your headphone could work in this
situation.
this is from #3:
control.11 {
iface MIXER
name 'Headphone Playback Switch'
value.0 false
With the log of #33, after resume, the active output device is hdmi-
stereo-0 (monitor)?
BTW, it looks like you still use the workaround of #19 (load-module
module-switch-on-connect blacklist=""), since this workaround doesn't help,
please drop it.
And after dropping the (load-module
** Changed in: alsa-driver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1899764
Title:
[Realtek ALC257][Lenovo T14 Gen1] Internal mic
Public bug reported:
This bug is for tracking purpose.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: alsa-lib (Ubuntu)
Importance: High
Assignee: Hui Wang (hui.wang)
Status: In Progress
** Affects: alsa-lib (Ubuntu Focal)
Importance
Public bug reported:
This bug is for tracking purpose.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: alsa-utils (Ubuntu)
Importance: High
Assignee: Hui Wang (hui.wang)
Status: In Progress
** Affects: alsa-utils (Ubuntu Focal
This is the debdiff for focal, and since groovy already had the alsa-
utils 1.2.3, there is no SRU for groovy.
thx.
** Description changed:
- This bug is for tracking purpose.
+ This patchset was backported from mainline alsa-utils 1.2.3, and
+ groovy already integrated alsa-utils 1.2.3, there
OK, set it to invalid.
thx.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1899764
Title:
[Realtek
OK, got it. will investigate it and fix it in the future.
thx.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1899745
Title:
[SRU] alsa-utils: let alsactl support _boot section
@YC,
This SRU is not to fix the 3 profiles in the combo list, it is to fix
the issue of "no active profile in the combo list" after plugging the
hdmi/dp monitor.
Without this SRU, after users plug a hdmi/dp monitor, the profile combo
list is empty, need users manually to select profile from 3
According to the log in the #1, the bluetooth sound card is not in the
pulseaudio.
Default Sink: alsa_output.pci-_00_1f.3.analog-stereo
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
We just enabled the mic for this machine under 20.04.
Please run 'sudo apt dist-upgrade' then reboot, please use ubuntu
kernel, if it doesn't work, please upload the log of 'painfo >
painfo.txt'.
--
You received this bug notification because you are a member of Desktop
Packages, which is
It is not a common issue, I tried to reproduce it on many machines, but
so far can't reproduce the problem. It is not easy to debug without a
physical machine to reproduce the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
@Tessa,
Please collect some log:
fresh booting up, and select hdmi audio as output, then run pacmd list >
before.txt
suspend and resume, make sure the output is switched to on-board device,
run pacmd list > after.txt
then upload the before.txt and after.txt.
--
You received this bug
For the gsequencer/3.1.3-1 (s390x):
The last step fails, but it has nothing to do with alsalib, this is the log
without regression reported:
ags-integration-unit-test PASS
ags-integration-functional-test FLAKY non-zero exit status 2
Creating nova instance
using 'pacmd set-card-profile'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1892580
Title:
[HDA-Intel - HDA Intel, playback] No sound at all
Status in alsa-driver package in
please set the active profile to: output:analog-stereo: Analog Stereo
Output (priority 6500, available: unknown)
And make sure the Default sink name: is alsa_output.pci-_00_05.0
.analog-output.
--
You received this bug notification because you are a member of Desktop
Packages, which is
@Chi-Wei,
OK, got it, will investigate this issue.
--
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/1896098
Title:
Lenovo P1G3 - unable to select system speakers when headset
Tested on one Lenovo and one Dell machines, they all use legacy HDA
audio driver. Upgraded the g-c-c to 0buntu2, plug a hdmi/dp monitor, we
could see the hdmi-stereo from the configuration combo list and audio
worked well. Without this SRU, users will see the empty configuration
combo list and
** Summary changed:
- [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list
after plugging a hdmi/dp monitor
+ [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list
after selecting the hdmi/dp audio in the g-c-c
--
You received this bug
Groovy)
Importance: Critical
Assignee: Hui Wang (hui.wang)
Status: New
** Also affects: gnome-control-center (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gnome-control-center (Ubuntu Focal)
Importance: Undecided => Critical
** Changed in: gn
This is the debdiff for groovy.
thx.
** Patch added: "gnome-control-center_3.38.0-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1896919/+attachment/5413825/+files/gnome-control-center_3.38.0-1ubuntu2.debdiff
--
You received this bug notification
Public bug reported:
This is for tracking purpose.
** Affects: gnome-control-center (Ubuntu)
Importance: Critical
Assignee: Hui Wang (hui.wang)
Status: New
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Critical
** Also affects: gnome-control-center (Ubu
@seb,
Done, just added a comment in the MR to request to cherry-pick the patch
to gnome-3-38.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1896919
Title:
[SRU] g-c-c:
I did a test today, plug two monitors to Intel hdmi ports, I chose hdmi2
in the gnome-control-center, suspend and resume, the output device still
on the hdmi2, I didn't reproduce the problem.
When you have time, please collect the log according to
, How does it work under windows?
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Critical
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Hui Wang (hui.wang)
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
If you want the hdmi-output to be selected automatically after plugging,
you need to manually select it as output once, then pulseaudio will
remember uer's preference. Then unplug and replug the monitor, the
system will automatically switch to hdmi-output.
--
You received this bug notification
@cchen50,
After debugging with Realtek (thank Kailiang@Realtek's help), we found 2
issues, the 1st one is about linux, the 2nd one is about the BIOS.
1st issue, we need to disable auto-mute (run alsamixer, find auto-mute,
disable it), after this operation, nearly all machines could work except
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Hui Wang (hui.wang)
** Also affects: alsa-ucm-conf (Ubuntu)
Importance: Und
If there is no log from pulseaudio, it means the pulseaudio does not
join the connection process yet. The pulseaudio needs to receive a Dbus
message (connection request) from bluez first, then it starts to
processing bluetooth connection. So in your case, the connection failed
in the bluez.
Could
Let us see if the HDMI sound card or analogue sound card introduced this
problem, please edit /etc/modprobe.d/alsa-base.conf, add "options snd-
hda-intel enable=0,1", reboot, this will disable the hdmi audio sound
card (please check if the hdmi sound card is disabled successfully by
pacmd
Please test 1:13.99.1-1ubuntu3.3+lp1881659 in the ppa of
ppa:hui.wang/pulseaudio, if it could fix the 1st issue?
https://launchpad.net/~hui.wang/+archive/ubuntu/pulseaudio
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
It is a known issue, just fixed in the pulseaudio, please try latest
pulseaudio ubuntu3.3? If it doesn't work, please talk to Kaiheng, he
knows what exact version will include the fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
According to the log, when autoconnection fails:
Redmi phone sent (Handsfree):
> ACL Data RX: Handle 11 flags 0x02 dlen 17
>
> #37 [hci0] 9.000527
If the handsfree is not a critical service feature, even the laptop
reply that it doesn't support this service, the redmi phone should
inquire other audio services, but it doesn't.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
the first issue of this bug
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881659 is
similar to this one.
--
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/1871329
Title:
The first issue looks like similar to this one:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329
--
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/1881659
Title:
Just for testing, let us see if the hdmi audio part or analog audio part
introduced the issue, then we could make a deeper investigation on that
part.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
301 - 400 of 679 matches
Mail list logo
