Bug 2001680 - sound is again totally broken
Summary: sound is again totally broken
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-06 18:15 UTC by hw
Modified: 2022-06-08 01:10 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-06-08 01:10:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description hw 2021-09-06 18:15:59 UTC
Description of problem:

There is no sound being played through a monitor connected to a display port.

The sound configuration in KDE shows a bunch of HDMI devices and none of them are working.  There are no display port devices in the list.  Sometimes sound is working after a reboot, sometimes it isn't, sometimes I can get it to work by switching between devices.  It's totally random.

If the sound is basically working, when there has been no sound being played for a few seconds and then sound is being played again --- like pausing when watching a movie --- it takes a while before the sound comes back.  Please make it so that the sound doesn't cut out like that.  The sound needs to continue right away when movie is unpaused.  It used to work that way.

I don't understand why you forced pulseaudio upon the users who never wanted it, then took many too many years to get pulseaudio half-way working, and now you have replaced it with this crap called pipewire and start annoying everyone all over again.

Please stay with something that works!


What do you suggest how I get the sound working again?

Comment 1 hw 2021-09-06 20:22:05 UTC
Workaround:

dnf install pulseaudio --allowerasing
dnf remove --setopt protected_packages= pipewire

After that, kill all pipewire processes and start pulseaudio manually as the user who wants audio.  After that, audio works again.

Just don't ask me what the fix is when you want to use gnome --- but that's unusable anyway.

Comment 2 Wim Taymans 2021-09-07 07:18:03 UTC
A better workaround:

sudo dnf swap pipewire-pulse pulseaudio --allowerasing

And then 

sudo dnf remove pipewire-alsa

Then:

systemctl --user restart pipewire
systemctl --user restart pulseaudio

Comment 3 hw 2021-09-10 14:03:08 UTC
Thanks, I used the workaround as far as possible.

Audio not coming back right away after a period of quietness remains.  It's really annoying and also, for example, prevents notification sounds from being heared because the sound has stopped long before audio has re-enabled itself.

Comment 4 Wim Taymans 2021-09-16 14:24:19 UTC
> Audio not coming back right away after a period of quietness remains.  It's really annoying and also, for example, prevents notification sounds from being heared because the sound has stopped long before audio has re-enabled itself.

It is likely a driver bug.

Comment 5 hw 2021-12-31 08:08:04 UTC
As to the driver bug, is there's nothing I could do about it?

As to pipewire not working, it still doesn't work in Fedora 35.  Even worse, after upgrading from 34 to 35, pipewire was automatically reinstalled, and it still doesn't detect any devices.  I had again to switch back to pulse to get sound back.

Comment 6 Ben Cotton 2022-05-12 16:46:13 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Ben Cotton 2022-06-08 01:10:46 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.