this is the log after resuming, where no audio devices are available
post-resume except the internal SPDIF. so this bug has gotten
significantly worse in the move from 20.04->20.10.
** Attachment added: "2020-10-26-pulseaudio.txt"
Note that I made the changes you recommended in those files and had used
it for a couple weeks, and it seemed to be behaving as expected. However
after the update to 20.10, it seems to have reverted the changes and now
my sound is broken again, experiencing even *worse* problems with
puleaudio
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
"after resume, the active output device is hdmi-stereo-0 (monitor)?" ->
as I've noted before, for some reason after resume, it switches around
the numbering which output is actually which physical connection. this
is could be the root cause of the issue I'm seeing, but given all the
other
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
this is the log entries only post resume. the output is incorrect after
resume, as usual.
** Attachment added: "2020-09-09-pa.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5409287/+files/2020-09-09-pa.log
--
You received this bug notification because you
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
it appears to, yes. i only tested it a couple times, but it consistently
stayed on the same audio output.
--
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/1888598
Title:
pulseaudio
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.
also, I looked for the error you described, and it's not present, but I
do see this:
2539:D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(8) failed:
Invalid argument
2542:D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(8) failed:
Invalid argument
2545:D: [pulseaudio]
the before and after outputs of catting this card are identical
according to diff, so I've just included the before output here.
** Attachment added: "before.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5407463/+files/before.txt
--
You received this bug
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
after pacmd --list, when the system has woken from sleep, and now is on
the wrong sound output. note that it's not going to the internal sound
card at the moment, but the other hdmi device. even though looking at
the diff, it thinks the default sync hasn't changed, it actually is now
going to the
before pacmd --list, with the input correctly selected as 5.1 surround
on HDMI / DisplayPort 2.
** Attachment added: "before.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5406020/+files/before.txt
--
You received this bug notification because you are a
@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
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
and here's another new wrinkle... it looks like after my machine has
been put to sleep and woken up a few times, it now creates a new dummy
audio device each time, until my system is full of dummy audio devices.
seriously what is up with sleep/wake and pulse in ubuntu 20.04??
--
You received
I'm seeing another fun intermittent issue after waking from sleep on my
system. sometimes after resume, the audio is really static-y, until i
turn the volume down one notch and back up again. next time it happens
I'll attach the logs again, just to see if there's anything illuminating
there. it
ok, made that change. it stayed on the correct input after a reboot, and
after sleep/resume. however, sleep/resume still messes up the device
ordering so i still have to change it to the new "correct" dev after
resume. still. headway! :)
--
You received this bug notification because you are a
Looks like this is really a PA's defect.
you could test this workaround temporarily:
edit /etc/pulse/default.pa
do some change like this: load-module module-switch-on-connect
blacklist=""
I will find a physical machine to debug this issue, and try to find a
real solution.
--
You received
alright, here's the pa debug log where I did a fresh boot, set audio
from s/pdif to the hdmi audio output, then put the machine to sleep and
woke it, and then set the audio to the other hdmi output device after
the system switched them around.
** Attachment added: "pa.log.xz"
That is weird, could you please upload the pa.log which contains the log
of switching to hdmi audio and suspend/resume.
--
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/1888598
Title:
alright, I see on boot, it changing the configured default when I switch
to HDMI audio from p/sdif:
4203:I: [pulseaudio] core.c: configured_default_sink: alsa_output.pci-
_01_00.1.hdmi-surround-extra1 -> alsa_output.pci-_01_00.1.hdmi-
surround
and after suspend/resume, there are no new
And if you couldn't find the configured_xxx, you could use pacmd set-
default-sink x to switch to hdmi audio instead of using your normal
way to witch the audio device.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
@Tessa,
could you find "configured_default_sink" instead of "default_sink" from
from the log, configured_default_sink is more important than
default_sink for audio device switching.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
ok, after setting it post-reboot, I see the following setting it as the
default in the logs:
4572:I: [pulseaudio] core.c: default_sink: alsa_output.pci-
_00_1b.0.iec958-stereo -> alsa_output.pci-_01_00.1.hdmi-surround
as well as the following active ports with `pactl list`:
So, let's debug with the pulseaudio log.
Enable the debugging log in the pulsaudio:
edit /usr/lib/systemd/user/pulseaudio.service, comment out the line starting
with ExecStart=..., add a new line "ExecStart=/user/bin/pulseaudio -
--log-target=file:/home/your_user_name/pa.log
reboot
Then
yep, looks like even after sleep and when things are all messed up,
they're still listed as available:
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency
offset 0 usec, available: yes)
properties:
after the resume, you run pacmd list-cards, do the hdmi-output-0 and -1 are
"available: yes" as below?
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency
offset 0 usec, available: yes)
properties:
device.icon_name
Alright, I just ran the test. When I unplug the hdmi cable connected to
the receiver, it switches to s/pdif. I left it for 30s, then plugged it
back in, and it correctly switched back.
Put it to sleep, woke it up, and the audio outputs were all messed up
again. So it's something that's happening
I should also note, I tested this issue in KDE, and saw the same issues.
So it doesn't seem to have anything to do with gnome or the gnome-
control-center.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
I guess when you computer suspends and resumes, the hdmi/dp has a
process like plugging out (suspend) and plugging in (resume), so it
should have the same behaviour of plugging out and replugging in, no
need to run suspend and resume.
And the s/pdif audio will be active after plugging in, this
ok, did a dist upgrade, now I'm on kernel 5.4.0-42-generic and gnome-
control-center 3.36.4-0ubuntu1. bugs still persist. notably, after
sleep/resume:
- defaulted to s/pdif audio
- switched hdmi/dp audio outputs, so i have to use hdmi/dp 2 to get audio out,
but it still sees surroundsound only
I'm also affected by it on a recent pulseaudio version 13.0, kernel 5.7.8
Seems like a revival of
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
Displayport GPU audio device is incorrectly being re-enabled on login by
pulseaudio.
--
You received this bug notification because
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
And you could update the gnome-control-center and redo your test.
sudo apt-get update
sudo apt install gnome-control-center
--
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/1888598
Can you try updating your system to kernel 5.4.0-42-generic
and see if you can reproduce your 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/1888598
Title:
pulseaudio has
37 matches
Mail list logo
