Audio problems (can't stream)

User Support
1

Hi,

It seems that some update a few months ago for Fedora 32 broke my ability to stream audio / video online.

I’ve upgraded to Fedora 33 but the issue remains the same.

I think I’ve covered all of the simple basis: I have the ffmpeg package installed from RPM Fusion, I have told Firefox that its ok to play DRM restricted music, and it used to work!

However, now it doesn’t. I would normally try and stream from open.spotify.com or something like the metopera.org.

It seems to be ffmpeg error from the logs, but I’m not sure what is causing it. I am seeing errors to do with an inability to decode the audio.

Can anyone help? I’ll post in the Firefox terminal errors from open.spotify.com here (my highlights):

Content Security Policy: Ignoring “‘unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “‘unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “‘unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “‘unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “‘unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “‘unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Some cookies are misusing the recommended “SameSite“ attribute 12
Cookie “_schn” has been rejected for invalid domain. scevent.min.js:1:1943
Request to access cookie or storage on “https://sb.scorecardresearch.com/b?c1=2&c2=15654041&ns__t=1615722065948&ns_c=UTF-8&c8=Spotify%20-%20Web%20Player%3A%20Music%20for%20everyone&c7=https%3A%2F%2Fopen.spotify.com%2F&c9=” was blocked because it came from a tracker and content blocking is enabled.
The resource at “https://open.scdn.co/cdn/fonts/CircularSpUIv3T-Book.3466e0ec.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. open.spotify.com
The resource at “https://open.scdn.co/cdn/fonts/CircularSpUIv3T-Bold.8d0a45cc.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. open.spotify.com
The resource at “https://open.scdn.co/cdn/fonts/CircularSpUIv3T-Light.afd9ab26.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. open.spotify.com
Media resource blob:https://open.spotify.com/45c2c24e-7759-460f-88cf-dce769adbcaf could not be decoded. open.spotify.com
This error message will be blank when privacy.resistFingerprinting = true. If it is really necessary, please add it to the whitelist in MediaError::GetMessage: NS_ERROR_DOM_MEDIA_MEDIASINK_ERR (0x806e000b) - OnMediaSinkAudioError vendor~web-player.d7353418.js:1:1288641
Source map error: Error: request failed with status 404
Resource URL: https://open.scdn.co/cdn/build/web-player/vendor~web-player.d7353418.js
Source Map URL: vendor~web-player.d7353418.js.map
Media resource blob:https://open.spotify.com/45c2c24e-7759-460f-88cf-dce769adbcaf could not be decoded, error: Error Code: NS_ERROR_DOM_MEDIA_MEDIASINK_ERR (0x806e000b)
Details: OnMediaSinkAudioError open.spotify.com
Media resource blob:https://open.spotify.com/2c57b46d-c901-41c9-9e0c-fcca282af3b1 could not be decoded. open.spotify.com
This error message will be blank when privacy.resistFingerprinting = true. If it is really necessary, please add it to the whitelist in MediaError::GetMessage: NS_ERROR_DOM_MEDIA_MEDIASINK_ERR (0x806e000b) - OnMediaSinkAudioError vendor~web-player.d7353418.js:1:1288641
Media resource blob:https://open.spotify.com/45c2c24e-7759-460f-88cf-dce769adbcaf could not be decoded, error: Error Code: NS_ERROR_DOM_MEDIA_MEDIASINK_ERR (0x806e000b)
Details: OnMediaSinkAudioError open.spotify.com

Errors from metopera.org are here:

Some cookies are misusing the recommended “SameSite“ attribute 3
Autoplay is only allowed when approved by the user, the site is activated by the user, or media is muted. index.min.js:1:65827
Autoplay is only allowed when approved by the user, the site is activated by the user, or media is muted. index.min.js:1:65827
VIDEOJS: WARN: The Brightcove Chromecast Receiver plugin could not be initialized because the player is not running on a supported version of Google Chrome. index.min.js:1:121987
Request to access cookie or storage on “?” was blocked because it came from a tracker and content blocking is enabled. 9
VIDEOJS: WARN: Calling addRemoteTextTrack without explicitly setting the “manualCleanup” parameter to true is deprecated and default to false in future version of video.js index.min.js:1:121987
Media resource blob:https://metoperafree.brightcove-services.com/519fd91a-e2b0-4330-8ed7-a743de140ea9 could not be decoded. metoperafree.brightcove-services.com
Media resource blob:https://metoperafree.brightcove-services.com/ce9b1bc4-8637-461e-b273-557e15b3f1a5 could not be decoded. metoperafree.brightcove-services.com
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. index.min.js:1:132873

2

One possibility to look for. A while back there was a broken dependency for pulse audio which prevented updates from happening properly. If you provided “–allowerasing” to get around that issue then DNF would delete a few Qubes packages which broke the audio in any AppVM using that template. If you do “rpm -qa | grep qubes” in that template do you see “pulseaudio-qubes” listed? If not, look to see what qubes packages are not listed and take it from there. If you have any AppVMs using a different template check to see if audio is working there.

3

Whoops. I was adding some formatting to your post, but then I noticed there were highlights :sweat_smile:. Sorry. It’s all back to normal now.

Maybe it could be this. But nothing points to this being a qubes-specific issue. Maybe looking for the issue on fedora or in other linux distributions more generally can yield more answers. Something like:

https://forums.linuxmint.com/viewtopic.php?f=48&t=295346&start=20

4

I’m afraid I’ve slightly lost you.

I ran the rpm -qa | grep qubes commaned, and there is no entry for pulseaudio-qubes
Should there be?

DNF tells me that pulseaudio is installed.

Is there a list of entries that I should be seeing, and can compare the output to?

5

I have been searching around Fedora forums, but all of the issues that I can see are getting sound to work, which is usually some variation on enabling ffmpeg and friends.

I can’t see anything where it suddenly stopped working, which would suggest a dodgy update?

I just did the switch to Fedora 33, but as it was a clone and update, the problem seems to have followed me. :frowning:

1 Like
6

| JustAnotherQubesUser
March 15 |

  • | - |

I’m afraid I’ve slightly lost you.

I ran the rpm -qa | grep qubes commaned, and there is no entry for pulseaudio-qubes
Should there be?

DNF tells me that pulseaudio is installed.

Is there a list of entries that I should be seeing, and can compare the output to?

Here is what I get from the stock fedora-33 template:
qubes-usb-proxy-1.0.29-1.fc33.noarch
qubes-libvchan-xen-4.0.8-1.fc33.x86_64
qubes-img-converter-1.2.9-1.fc33.x86_64
qubes-gpg-split-2.0.50-1.fc33.x86_64
qubes-mgmt-salt-vm-connector-4.0.24-1.fc33.noarch
qubes-utils-4.0.31-1.fc33.x86_64
qubes-kernel-vm-support-4.0.31-1.fc33.x86_64
qubes-utils-libs-4.0.31-1.fc33.x86_64
thunderbird-qubes-2.0.5-1.fc33.noarch
python3-qubesimgconverter-4.0.31-1.fc33.x86_64
qubes-pdf-converter-2.1.11-1.fc33.x86_64
qubes-db-libs-4.0.16-1.fc33.x86_64
pulseaudio-qubes-4.0.35-1.fc33.x86_64
qubes-core-agent-qrexec-4.0.61-1.fc33.x86_64
qubes-core-agent-passwordless-root-4.0.61-1.fc33.x86_64
python3-dnf-plugins-qubes-hooks-4.0.61-1.fc33.x86_64
python3-qubesdb-4.0.16-1.fc33.x86_64
xen-qubes-vm-4.8.5-29.fc33.x86_64
qubes-db-4.0.16-1.fc33.x86_64
qubes-db-vm-4.0.16-1.fc33.x86_64
qubes-core-agent-4.0.61-1.fc33.x86_64
qubes-core-agent-dom0-updates-4.0.61-1.fc33.x86_64
qubes-core-agent-nautilus-4.0.61-1.fc33.x86_64
qubes-core-agent-systemd-4.0.61-1.fc33.x86_64
qubes-gui-agent-4.0.35-1.fc33.x86_64
qubes-input-proxy-sender-1.0.23-1.fc33.x86_64
qubes-core-agent-networking-4.0.61-1.fc33.x86_64
qubes-core-agent-network-manager-4.0.61-1.fc33.x86_64
qubes-vm-recommended-4.0.10-1.fc33.noarch
qubes-vm-dependencies-4.0.10-1.fc33.noarch
qubes-menus-4.0.21-1.fc33.noarch
I don’t think I added anything to this template. I keep this one as a backup in case my template gets broken somehow and I need to switch to something to get back up and running.

7

JustAnotherQubesUser, As a suggestion, you could switch your VMs to Debian based templates. I ran into the same problems as you did a number of months back with my fedora based VMs. I tried the --allowerase method and it did seem to remedy the situation temporarily, but broke something else (I forget what.) Then subsequent updates seemed to be the cause of a loss of sound in fedora based VMs again. More head scratching and trial and error. Fortunately I was given the advice a couple of times in this forum, to try using Debian based VMs. All of my day to day VMs (untrusted, personal, work, vpn, etc) are now Debian based and I have had absolutely no sound problems since.

8

I followed your advice.

My browsing related templates, I have moved to Debian and they seem to work well.

1 Like