Bug 2019659 - Sound plays once then freezes audio pipeline, all apps that use audio break
Summary: Sound plays once then freezes audio pipeline, all apps that use audio break
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wireplumber
Version: 35
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-03 03:51 UTC by Michael Cronenworth
Modified: 2022-12-13 15:45 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:45:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michael Cronenworth 2021-11-03 03:51:03 UTC
Description of problem:
Upgraded from F34 to F35 today. After logging in I tried adjusting my audio volume using the media keys on my keyboard. The default Gnome "beep" noise sounds one time. Adjusting the volume level again resulted in nothing happening. Trying to start audio apps (Rhythmbox, Totem, mpv) results in the app taking forever to start. No audio plays. Occasionally about every 30 seconds the Gnome overlay for volume level appears.

Rebooting and trying again repeats the same thing.

Downgrading to pipewire-media-session fixes it. Media keys function. Audio plays.

The wireplumber service was running and enabled.


Version-Release number of selected component (if applicable):
wireplumber-0.4.4-2.fc35.x86_64
pipewire-media-session-0.3.39-1.fc35.x86_64
pipewire-0.3.39-1.fc35.x86_64

Comment 1 Fedora Update System 2021-11-19 09:09:43 UTC
FEDORA-2021-057b10a6f5 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-057b10a6f5

Comment 2 Fedora Update System 2021-11-20 02:19:33 UTC
FEDORA-2021-057b10a6f5 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-057b10a6f5`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-057b10a6f5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2021-11-21 01:54:57 UTC
FEDORA-2021-057b10a6f5 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Michael Cronenworth 2021-11-21 02:38:09 UTC
Not fixed with the update.

Comment 5 Ben Cotton 2022-11-29 17:13:21 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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 '35'.

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 35 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 6 Ben Cotton 2022-12-13 15:45:20 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active 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.