Wise Gurus of KubuntuForums,
If there is a better forum for this item, please tell me where to post it. I don't know if this is a noob topic.
I've already exercised Google AI to investigate this issue but keep running into deeper and deeper rabbit holes in areas of minimal personal experience.
I have an application newly installed via flatpak that requires Wayland.
I've installed Wayland on my 24.04.3 Kubuntu system running the NVIDIA 6.14.0-24-generic kernel and the nvidia-driver-575-open driver (575.64.03).
The application runs, but there is no sound.
I logged out and back in, choosing Wayland on the login screen. No audio.
I rebooted and then logged in, choosing Wayland. No audio.
I logged out and logged back in, choosing X11. There is audio.
When there is no audio, the "speaker icon" on the taskbad is red, and when I click on the red speaker I am informed there is "no device".
When there is audio, the "speaker icon" is white, and even better, I can listen to my tunes and hear audio when using multiple applications.
If you want me to use Wayland and generate the outputs of commands like
Is there a problem in the audio stack when Wayland is used? Or is this an unresolved conflict between X11 and Wayland?
Has anyone here experienced this issue?
If so, I would greatly appreciate advice and/or links to knowledge sources that discuss solutions and provide step-by-step instructions.
Either that, or I delete the application loaded via flatpak and delete Wayland and wait for maturization of the technology within Kubuntu.
Thank you very much in advance.
If there is a better forum for this item, please tell me where to post it. I don't know if this is a noob topic.
I've already exercised Google AI to investigate this issue but keep running into deeper and deeper rabbit holes in areas of minimal personal experience.
I have an application newly installed via flatpak that requires Wayland.
I've installed Wayland on my 24.04.3 Kubuntu system running the NVIDIA 6.14.0-24-generic kernel and the nvidia-driver-575-open driver (575.64.03).
The application runs, but there is no sound.
I logged out and back in, choosing Wayland on the login screen. No audio.
I rebooted and then logged in, choosing Wayland. No audio.
I logged out and logged back in, choosing X11. There is audio.
When there is no audio, the "speaker icon" on the taskbad is red, and when I click on the red speaker I am informed there is "no device".
When there is audio, the "speaker icon" is white, and even better, I can listen to my tunes and hear audio when using multiple applications.
If you want me to use Wayland and generate the outputs of commands like
systemctl --user status pipewire.service
systemctl --user status wireplumber.service
systemctl restart --user pulseaudio.service
systemctl --user status pulseaudio.service
pulseaudio -k
pulseaudio --start
systemctl restart --user pulseaudio.service
journalctl -p 3 -xb | grep -i "pulse\\|audio\\|alsa"
sudo dmesg | grep -i "audio\\|sound\\|pulse\\|alsa"
or other commands, then I will switch back into Wayland, do so, and provide logs. systemctl --user status wireplumber.service
systemctl restart --user pulseaudio.service
systemctl --user status pulseaudio.service
pulseaudio -k
pulseaudio --start
systemctl restart --user pulseaudio.service
journalctl -p 3 -xb | grep -i "pulse\\|audio\\|alsa"
sudo dmesg | grep -i "audio\\|sound\\|pulse\\|alsa"
Is there a problem in the audio stack when Wayland is used? Or is this an unresolved conflict between X11 and Wayland?
Has anyone here experienced this issue?
If so, I would greatly appreciate advice and/or links to knowledge sources that discuss solutions and provide step-by-step instructions.
Either that, or I delete the application loaded via flatpak and delete Wayland and wait for maturization of the technology within Kubuntu.
Thank you very much in advance.
Comment