Bug 2057336 - No sound audible on libvirt VM running KDE (F36)
Summary: No sound audible on libvirt VM running KDE (F36)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-desktop
Version: 36
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-23 08:48 UTC by Lukas Ruzicka
Modified: 2023-05-25 16:58 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 16:58:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Journalctl .-e from the affected machine. (134.39 KB, text/plain)
2022-02-23 10:25 UTC, Lukas Ruzicka
no flags Details

Description Lukas Ruzicka 2022-02-23 08:48:26 UTC
Description of problem:

There is no sound audible when running a F36 KDE Desktop in a libvirt based VM on Fedora 36 Workstation.

The sound playing applications do not report any problems and their VU meters and progress bars do normally proceed as if the files were playing just fine. 
I have tried with OGGs and WAVs and various applications - Elise, Dragon Player, Gnome Music (from Flatpak) and the result is still the same -> no audible sound.

When trying this with a F36 Workstation libvirt VM, sound can be played normally without any issues.

Both VMs use the same sound driver -> HDA (ICH9)

Version-Release number of selected component (if applicable):
plasma-desktop-5.24.0-1 (VM)

libvirt-8.0.0-2.fc36.x86_64 (host)

How reproducible:
Always

Steps to Reproduce:
1. Boot KDE Live and install it to the disk.
2. Start the system.
3. Try to play some audio files.

Actual results:

No sound is heard when played on libvirt based KDE VM.

Expected results:

Sound should be heard normally as it is on libvirt based Workstation VM.

Comment 1 Lukas Ruzicka 2022-02-23 09:49:29 UTC
I have also tested on bare metal and there, the sound is ok.

Comment 2 Lukas Ruzicka 2022-02-23 10:25:28 UTC
Created attachment 1862925 [details]
Journalctl .-e from the affected machine.

There are some wireplumber errors in the logs but I am not sure if these affect the behaviour somehow.

Comment 3 Ben Cotton 2023-04-25 16:54:23 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 '36'.

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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 4 Ludek Smid 2023-05-25 16:58:20 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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.