Bug 1963786 - Headphone output not working with pipewire, does work when switched back to pulseaudio
Summary: Headphone output not working with pipewire, does work when switched back to p...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pipewire
Version: 34
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Wim Taymans
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-24 03:53 UTC by Nicholas Bishop
Modified: 2022-06-08 06:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-08 06:32:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
pactl info output (483 bytes, text/plain)
2021-05-24 03:53 UTC, Nicholas Bishop
no flags Details
pactl list output (52.74 KB, text/plain)
2021-05-24 03:53 UTC, Nicholas Bishop
no flags Details

Description Nicholas Bishop 2021-05-24 03:53:13 UTC
Created attachment 1786239 [details]
pactl info output

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. Play sound with pipewire enabled and headphones plugged in


Actual results:
No sound


Expected results:
Sound


Additional info:
This was initially working after upgrading to 34, but stopped working recently. I have run dnf update and rebooted.

Switching back to pulseaudio with "sudo dnf swap --allowerasing pipewire-pulseaudio pulseaudio" fixes it, so not a hardware issue.

I'm not sure what logs I should be attaching, so I attached a couple pactl commands. Please let me know what other info would be helpful :)

Comment 1 Nicholas Bishop 2021-05-24 03:53:32 UTC
Created attachment 1786240 [details]
pactl list output

Comment 2 Wim Taymans 2021-05-24 07:23:11 UTC
It could be related to this: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1206

If that's the case, there is a workaround in the above mentioned issue until we can sync all components.

Comment 3 Fedora Update System 2021-06-03 10:34:30 UTC
FEDORA-2021-4bd6fdd9d3 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4bd6fdd9d3

Comment 4 Fedora Update System 2021-06-04 01:18:40 UTC
FEDORA-2021-4bd6fdd9d3 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4bd6fdd9d3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4bd6fdd9d3

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

Comment 5 Ben Cotton 2022-05-12 16:59:05 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 6 Ben Cotton 2022-06-08 06:32:59 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.