Some Youtube videos fail to play on Linux/Firefox ESR
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
People
(Reporter: braiamp, Unassigned)
Details
(Whiteboard: [see comment 6])
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0
Steps to reproduce:
Create a new profile on the ESR branch, set up a http proxy and tell firefox to use it for everything.
Try to watch this video on youtube https://www.youtube.com/watch?v=gl6Mgpx6HV4
Other videos do not seem to have that problem
Actual results:
Youtube informs me that "Your browser can't play this video". Standard error reports:
ERROR mp4parse] Found 2 nul bytes in "\u{0}\u{0}"
Console outputs:
WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. base.js:9578:154
LegacyDataMixin will be applied to all legacy elements.
Set `_legacyUndefinedCheck: true` on element class to enable. desktop_polymer.js:9016:9
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://www.gstatic.com/youtube/img/emojis/emojis-svg-9.json desktop_polymer.js:1265:426
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://googleads.g.doubleclick.net/pagead/id desktop_polymer.js:1265:426
Some cookies are misusing the recommended “SameSite“ attribute 6
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://googleads.g.doubleclick.net/pagead/id. (Reason: CORS request did not succeed). Status code: (null).
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://jnn-pa.googleapis.com/$rpc/google.internal.waa.v1.Waa/Create base.js:6847:77
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://static.doubleclick.net/instream/ad_status.js spf.js:36:469
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://www.google.com/pagead/lvz?evtid=ABLloLm6UsDkZMMeb6pYS4yQ9qFoMxHrpmjVWrjjLz_o-1asKlEMI-Ls7B1_X2q3QFD23VgqY_RuwEDbP4htY479yUB3_Fq6tg&req_ts=1666192075&pg=MainAppBootstrap%3AWatch&az=1&sigh=AFmDhKftQ2s_sYWm09q6c_reb16rzHCEdQ desktop_polymer.js:1581
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://www.google.com.do/pagead/lvz?evtid=ABLloLm6UsDkZMMeb6pYS4yQ9qFoMxHrpmjVWrjjLz_o-1asKlEMI-Ls7B1_X2q3QFD23VgqY_RuwEDbP4htY479yUB3_Fq6tg&req_ts=1666192075&pg=MainAppBootstrap%3AWatch&az=1&sigh=AFmDhKftQ2s_sYWm09q6c_reb16rzHCEdQ desktop_polymer.js:1581
Loading failed for the <script> with source “https://static.doubleclick.net/instream/ad_status.js”. watch:1:1
Source map error: Error: request failed with status 404
Resource URL: https://www.youtube.com/watch?v=gl6Mgpx6HV4
Source Map URL: global_styles_sass.css.map
Source map error: Error: request failed with status 404
Resource URL: https://www.youtube.com/watch?v=gl6Mgpx6HV4
Source Map URL: yt-swatch-behavior_custom_style.css.map
Source map error: Error: request failed with status 404
Resource URL: https://www.youtube.com/watch?v=gl6Mgpx6HV4
Source Map URL: kevlar_global_styles_sass.css.map
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://i.ytimg.com/vi/eFVcLYw8Hz4/hqdefault.jpg?sqp=-oaymwEbCKgBEF5IVfKriqkDDggBFQAAiEIYAXABwAEG&rs=AOn4CLAV25c0SK1p_4Ut8Y58pSMeffW8tQ desktop_polymer.js:10904:72
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://yt3.ggpht.com/ytc/AMLnZu_r1AUFNOf9jeNaaL0o4ddER03iRRVZI1ah5nag=s48-c-k-c0x00ffffff-no-rj desktop_polymer.js:10904:72
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://i.ytimg.com/vi/TH-3wnLvItU/hqdefault.jpg?sqp=-oaymwEbCKgBEF5IVfKriqkDDggBFQAAiEIYAXABwAEG&rs=AOn4CLCUMRTkM2lYk5W7IcwXz1TXRpFY_g desktop_polymer.js:10904:72
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://i.ytimg.com/vi/Chu5O4SdpWs/hqdefault.jpg?sqp=-oaymwEbCKgBEF5IVfKriqkDDggBFQAAiEIYAXABwAEG&rs=AOn4CLCronxXhig9-HJTDjrP5HvWPGpSaw desktop_polymer.js:10904:72
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://i.ytimg.com/vi/jk1YZHt3dpM/hqdefault.jpg?sqp=-oaymwEbCKgBEF5IVfKriqkDDggBFQAAiEIYAXABwAEG&rs=AOn4CLCcPKdNtz2sMxkzN2eohJqCcXy_Fg desktop_polymer.js:10904:72
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://i.ytimg.com/vi/FkS9EdJ2I3U/hqdefault.jpg?sqp=-oaymwEbCKgBEF5IVfKriqkDDggBFQAAiEIYAXABwAEG&rs=AOn4CLBsbvmcYQK6Gzznw8sciNAT8UoHNw desktop_polymer.js:10904:72
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://i.ytimg.com/vi/8go_xBWa_EA/hqdefault.jpg?sqp=-oaymwEbCKgBEF5IVfKriqkDDggBFQAAiEIYAXABwAEG&rs=AOn4CLCUUNT0npMrw5eKi_WKRR4WiF9tGA desktop_polymer.js:10904:72
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://i.ytimg.com/vi/KA8czEmq1cM/hqdefault.jpg?sqp=-oaymwEbCKgBEF5IVfKriqkDDggBFQAAiEIYAXABwAEG&rs=AOn4CLCJ-XDBxvS_iscHnQuplK4BlckQyw desktop_polymer.js:10904:72
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://www.google.com/js/th/wjh_uz0vV4kvmBh32RTA-9oL3vnIf1WTq69pxsOy-vU.js spf.js:36:469
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://jnn-pa.googleapis.com/$rpc/google.internal.waa.v1.Waa/GenerateIT base.js:6847:77
MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead. desktop_polymer.js:1642:45
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://www.gstatic.com/inputtools/images/tia.png www-searchbox.js:945:87
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://fonts.googleapis.com/css?family=Roboto:300italic,400italic,500italic,700italic desktop_polymer.js:5629:221
Referrer Policy: Ignoring the less restricted referrer policy “origin-when-cross-origin” for the cross-site request: https://fonts.googleapis.com/css?family=Roboto+Mono:400 desktop_polymer.js:5629:221
The resource at “https://i.ytimg.com/generate_204” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. watch
The resource at “https://r2---sn-ab5sznld.googlevideo.com/generate_204” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. watch
The resource at “https://r2---sn-ab5sznld.googlevideo.com/generate_204?conn2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly.
Expected results:
The video should reproduce as most other videos.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Audio/Video: Playback' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•3 years ago
|
||
The severity field is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Updated•3 years ago
|
Comment 4•3 years ago
|
||
Reopening per note in https://bugzilla.mozilla.org/show_bug.cgi?id=1772085#c20 - playback issues are not caused by the mp4parse error (which is non-fatal), so there will be some other cause.
braiamp, do you see the playback failure without the HTTP proxy in place? Also curious if you see the same issue in current Firefox nightly. Also, running Firefox from a command prompt with some logging enabled (export MOZ_LOG=PlatformDecoderModule:5, then run firefox from the same prompt) may help shed some light on the cause of this.
Comment 5•3 years ago
|
||
Hello.
I've just upgraded Ubuntu from 22.04 to 22.10 some days ago. I'm experimenting some troubles by watching any online video stream and any mp4 videos saved on my PC. Basically they don't flow. To make them flow I should press the play button again and again and again and everytime I press it,only a small portion of the video go on. In addition,no audio output device work on my PC. After having exposed the problem in several places,I've found the reason because a nice reddit user gave to me a suggestion. He says that the cause of the problem is pipewire-media-session and that I should change it with wireplumber. This is what I tried to do. I've got the proof and the counter-proof that his suggestion is good. The commands that I should issue to fix the problems are the following :
$ systemctl --user unmask pulseaudio
$ systemctl --user --now disable pipewire-media-session.service
$ systemctl --user --now disable pipewire pipewire-pulse
$ systemctl --user --now enable pulseaudio.service pulseaudio.socket
sudo apt remove pipewire-audio-client-libraries pipewire
I suppose that those commands enable pulseaudio and remove pipewire. Infact the problems that I've explained above, go away. Instead,when I try to enable pipewire + wireplumber issuing the following commands the problems come back :
$ sudo apt install libldacbt-{abr,enc}2
$ sudo apt install libspa-0.2-bluetooth pipewire-audio-client-libraries pipewire-media-session- wireplumber
$ systemctl --user --now enable wireplumber.service
$ sudo cp /usr/share/doc/pipewire/examples/alsa.conf.d/99-pipewire-default.conf /etc/alsa/conf.d/
$ sudo apt remove pulseaudio-module-bluetooth
Its now clear that some elements of pipewire does not work correctly on Ubuntu 22.10,in some situation. I could still use PulseAudio,but I want to understand how to fix the problems pipewire is affected by. Someone can help me ? I've already asked on the ubuntu forums more times,but no one has been helpful. I've opened two bug tickets,no one replied. It seems that the ubuntu team does not care about this bug.
I've booted ubuntu budgie as virtual machine within bhyve and sound worked. So,my hardware is compatible with pipewire. At this point pipewire could not work in ubuntu 22.10 because some bug. (take in consideration that it works with ubuntu 22.04).
Updated•3 years ago
|
Comment 6•3 years ago
|
||
(In reply to marietto2008 from comment #5)
Its now clear that some elements of pipewire does not work correctly on Ubuntu 22.10,in some situation. I could still use PulseAudio,but I want to understand how to fix the problems pipewire is affected by. Someone can help me ? I've already asked on the ubuntu forums more times,but no one has been helpful. I've opened two bug tickets,no one replied. It seems that the ubuntu team does not care about this bug.
Thanks for the additional information. It sounds like this is an Ubuntu 22.10 upgrade issue or otherwise related to the pipewire version/configuration shipping in 22.10, so there's probably nothing that can be done to fix this from the Firefox side. The latest pipewire package for 22.10 (0.3.58-2ubuntu1, released 2022-10-11) mentions fixes related to audio crackling and real time thread priorities, which could be related - please make sure you're testing against the latest available version if you weren't already.
Comment 7•2 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:jimm, since the bug doesn't have a severity set, could you please set the severity or close the bug?
For more information, please visit BugBot documentation.
Updated•2 years ago
|
Description
•