On Fri, 2022-09-16 at 08:00 -0700, stan via users wrote: Thanks for the tips. I tried to reboot to previous kernel, that didn't change anything. The list of updated software packages are at the end. lspci gave two lines with Audio device 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 0a) 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller aplay -l gave the following **** List of PLAYBACK Hardware Devices **** card 1: HDMI [HDA Intel HDMI], device 3: HDMI 0 [DELL U3415W] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: HDMI [HDA Intel HDMI], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: PCH [HDA Intel PCH], device 3: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 I tried to test aplay -D, but I couldn't figure out the matching device name. Any advice? List of updated software today linux-firmware-whence libreoffice-data samba-common samba-client-libs libwbclient samba-common-libs samba-libs samba-dc-libs libsmbclient python3-samba-dc samba python3-samba samba-common-tools vim-data libgs ImageMagick-libs ghostscript-tools-fonts ghostscript-tools-printing ghostscript java-11-openjdk-headless java-11-openjdk amd-gpu-firmware intel-gpu-firmware iwlax2xx-firmware iwl7260-firmware nvidia-gpu-firmware vim-filesystem vim-common system-config-printer-libs python3-regex open-vm-tools libreoffice-ure-common libreoffice-opensymbol-fonts dnf-data python3-dnf dnf python3-dnf-plugins-core python3-dnf-plugins-extras-common autocorr-en libreoffice-help-en libreoffice-gtk3 libreoffice-ure libreoffice-x11 libreoffice-core libreoffice-langpack-en libreoffice-pyuno libreoffice-pdfimport libreoffice-graphicfilter libreoffice-calc libreoffice-writer libreoffice-ogltrans libreoffice-impress libreoffice-xsltfilter libreoffice-filters libreoffice-emailmerge libreoffice-base libreoffice-draw libreoffice-math python3-dnf-plugin-system-upgrade linux-firmware-whence libreoffice-data samba-common samba-client-libs libwbclient samba-common-libs samba-libs samba-dc-libs libsmbclient python3-samba-dc samba python3-samba samba-common-tools vim-data libgs ImageMagick-libs ghostscript-tools-fonts ghostscript-tools-printing ghostscript java-11-openjdk-headless java-11-openjdk amd-gpu-firmware intel-gpu-firmware iwlax2xx-firmware iwl7260-firmware nvidia-gpu-firmware vim-filesystem vim-common system-config-printer-libs python3-regex open-vm-tools libreoffice-ure-common libreoffice-opensymbol-fonts dnf-data python3-dnf dnf python3-dnf-plugins-core python3-dnf-plugins-extras-common autocorr-en libreoffice-help-en libreoffice-gtk3 libreoffice-ure libreoffice-x11 libreoffice-core libreoffice-langpack-en libreoffice-pyuno libreoffice-pdfimport libreoffice-graphicfilter libreoffice-calc libreoffice-writer libreoffice-ogltrans libreoffice-impress libreoffice-xsltfilter libreoffice-filters libreoffice-emailmerge libreoffice-base libreoffice-draw libreoffice-math python3-dnf-plugin-system-upgrade

On Sat, 2022-09-17 at 12:03 +0100, ja wrote: Alright, thanks

xgemxa/f36_no_hdmi_audio/ I have just done a full update and all now seems OK Tested on brave & vlc. I have a feeling that the output devices my be different than before but that may just be a bad memory! I did read somewhere that this may help dnf install pipewire-pulseaudio-0.3.29-1.fc36 reboot ie downgrade from pipewire-pulseaudio-0.3.58-1.fc36.x86_64 Might be worth a try. John

On Mon, 2022-09-19 at 12:40 +0200, andreas.fournier(a)runbox.com wrote: oops ! The suggestion I was referring to was https://www.ericsbinaryworld.com/2022/09/10/warning-bug-in-latest-pipewir... Where it clearly says dnf install pipewire-pulseaudio-0.3.49-1.fc36 NOT 0.3.29-1 - sorry As I have my own local repo the rpm and dependencies were picked up from there. dnf recognised it as a downgrade and just did it. Downgrading: pipewire x86_64 0.3.49-1.fc36 local-36-update 39 k pipewire-alsa x86_64 0.3.49-1.fc36 local-36-update 62 k pipewire-gstreamer x86_64 0.3.49-1.fc36 local-36-update 61 k pipewire-libs x86_64 0.3.49-1.fc36 local-36-update 1.6 M pipewire-pulseaudio x86_64 0.3.49-1.fc36 local-36-update 28 k pipewire-utils x86_64 0.3.49-1.fc36 local-36-update 327 k I repeat that in my case this was not needed, with kernel 5.19.9-200.fc36.x86_64 and pipewire-0.3.58-1.fc36.x86_64 all is well. John

Don't you need to start pipewire as the normal user? i.e. [host@non-root-user]$ systemctl restart pipewire-pulse.service --user suomi On 20/09/2022 09.01, andreas.fournier(a)runbox.com wrote: > On Mon, 2022-09-19 at 14:44 +0100, ja wrote: >> The suggestion I was referring to was >> https://www.ericsbinaryworld.com/2022/09/10/warning-bug-in-latest-pipewir... >> > Thanks for the link. What I now tried was to first update everything to > latest version from repo. Then as root I did a > 'dnf install pipewire-pulseaudio-0.3.49-1.fc36' > that went fine. Then I did 'systemctl restart pipewire-pulse.service' > that gave the following error > 'Failed to restart pipewire-pulse.service: Unit pipewire-pulse.service > not found.' > > I started to look through the log and found following red error > produced at the same time I did the commands > > systemd: pam_systemd(login:session): Failed to release session: Access > denied > > and following yellow errors > > dbus-broker: Peer :1.286 is being disconnected as it sent a message > with an invalid header. > dbus-broker: A security policy denied :1.751 to send method call > /org/freedesktop/login1:org.freedesktop.login1.Manager.ReleaseSession > to org.freedesktop.login1. > > _______________________________________________ > users mailing list -- users(a)lists.fedoraproject.org > To unsubscribe send an email to users-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

On Tue, 20 Sep 2022 11:00:13 +0200 andreas.fournier(a)runbox.com wrote: This should have worked, if you have a speaker connected to the out port on the on board sound device (the green one). Headphones will also work. To pursue this further, start pavucontrol-pulseaudio, go to the third tab, output devices, and run the above command again. Do you see sound being sent to the device? Do you hear it? If you do, your sound is working, but you have a configuration issue If you don't, go to the last tab of pavucontrol-pulseaudio, and turn off the built in audio. Run the above command again. Is there sound? Yes? The problem is in pipewire. No, maybe the volume isn't high enough. Run alsamixer -c 2 and raise the volume on the first bars until they are just in the red. Then, run the above command again. Is there sound? Yes? Sound is working but somehow the volumes were too low. No? I'm out of ideas. Given the data you showed, the built in audio should be producing sound if everything is configured properly (as I've described). You can set up and try a new user, but be sure that you have logged out your current user before you try with the new user. The first user to log in gains total control over pipewire / pulseaudio unless it is being run as a server, which is not the default.

On Thu, 22 Sep 2022 15:35:05 -0700 Samuel Sieb <samuel(a)sieb.net&gt; wrote: Well, your direct experience trumps my doc reading. But, how does that work? Unless the device has parallel paths, how can two people use the same device at the same time? And what about the speakers? I remember that it was a security issue when it was first implemented, to ensure that sound was not shared. At the time, if a sound played, everyone heard it. Perhaps, pulesaudio / pipewire have become more sophisticated and now tag sound and segregate it by user. Or maybe sound cards can process interleaved streams if they are tagged properly. Or, could it be tied to the screen visibility? Not questioning your experience, but wondering how it is implemented.

On Fri, 23 Sep 2022 15:24:03 -0700 Samuel Sieb <samuel(a)sieb.net&gt; wrote: That makes sense, a reasonable compromise. Because they have no way of controlling which audio output devices belong to which user, they have the audio switch with the visual, and let the user worry about who can hear their audio output.

On Fri, 23 Sep 2022 08:46:51 +0200 andreas.fournier(a)runbox.com wrote: Good news! Unless alsa has gone squirrely, the below is not your monitor. This is a sound device built into your MB, and should have ports on the case. The audio devices in monitors never have analog output, or at least I've never seen that. The ALC892 is a realtek chip installed on MBs to provide sound support. I guess it depends on what MB you are running, but I don't think any x86_64 MBs come without built in sound support. Maybe it is disabled / turned off? card 2: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: PCH [HDA Intel PCH], device 3: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0

On Fri, 16 Sep 2022 20:32:29 +0200 andreas.fournier(a)runbox.com wrote: I see from the other answer that there was a regression that caused this to happen to you, but I'll give a few answers. This is the device you want to be default if you want to use analog audio. It is strange that there is no card 0. That is usually the slot that the default audio takes. aplay -D plughw:2,0 [some wav file] will play analog output on the second card. [snipped] The only things I see in here that might affect sound are the firmware updates. And if this is a kernel issue, how is it that it didn't take a kernel update to cause it? It was working before the update with the same kernel, why would it stop? Strange.

On Fri, Sep 16, 2022 at 11:01 AM stan via users <users(a)lists.fedoraproject.org&gt; wrote: I am that someone, I think. Apologies for not following up. This is a work-weekday machine and I just got back to the office and today's updates to 5.19.9-100.fc35.x64_64 made no difference. I also tried a Live USB from the F33 days and still no sound. I suspect my issues are dead hardware and not relevant to the other issues going on.