Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: nidhogg on 2018/06/04, 01:08:32
-
I updated Chromium today to 67.0.3396.62-1Since then, Youtube stopped working corerctly. I can enter the website, view the thumbnail videos when I hover them, but I can't play any of them. I get "An error occurred. Please try again later. (Playback ID: *****************) That happens with every video from any channel.
I checked it's not my computer's or IP's fault, because I can watch videos with Firefox corectly.
The debug info from Youytube says that something's wrong with the audio decoder. I'll keep on searching :
{ "ns": "yt", "el": "detailpage", "cpn": "oRet3ziVOuZUqs7u", "docid": "vbwdEy0m6wI", "ver": 2, "referrer": "https://www.youtube.com/channel/UCcrSw79VCd4sSguy9D2HufQ/videos (https://www.youtube.com/channel/UCcrSw79VCd4sSguy9D2HufQ/videos)", "cmt": "0", "plid": "AAVtxMAxN9PGGktp", "ei": "gHIUW6-ZNpqpxwKMkJegDQ", "fmt": "242", "fs": "0", "rt": "448.176", "of": "VR3AfXmqod4Mjj2bFgIXBw", "euri": "", "lact": 7, "cl": "198379918", "mos": 0, "state": "c9", "vm": "CAEQABgE", "volume": 16, "c": "WEB", "cver": "2.20180525", "cplayer": "UNIPLAYER", "cbr": "Chrome", "cbrver": "67.0.3396.62", "cos": "X11", "hl": "en_US", "cr": "ES", "len": "756.181", "fexp": "23708904,23708906,23708910,23710476,23712544,23717917,23721698,23721752,23721898,23723618,23725261,23726564,23728274,23729689,23733185,23733751,23736483,23736738,23736809,23737531,23737673,23737720,23738445,23738491,23739466,23739764,23739983,23740493,23741227,23741719,23742058,23742655,23742970,23743486,23743669,23744165,23744176,23744392,9405988,9422596,9449243,9463583,9466592,9470250,9471235,9485000", "feature": "c4-videos-u", "afmt": "251", "vct": "0.000", "vd": "NaN", "vpl": "", "vbu": "", "vpa": "1", "vsk": "0", "ven": "0", "vpr": "1", "vrs": "0", "vns": "0", "vec": "null", "vvol": "0.16", "debug_error": { "errorCode": "fmt.unplayable", "errorDetail": "mediaElem.1;msg.DECODER_ERROR_NOT_SUPPORTED: audio decoder initialization failed", "message": "An error occurred. Please try again later.", "messageKey": "YTP_ERROR_GENERIC_WITHOUT_LINK" }, "ismb": 8190000, "relative_loudness": "3.091", "optimal_format": "360p", "user_qual": "auto", "debug_videoId": "vbwdEy0m6wI", "0sz": false, "op": "", "yof": false, "dis": "", "cgr": true, "debug_playbackQuality": "small", "debug_date": "Mon Jun 04 2018 01:05:38 GMT+0200 (Central European Summer Time)" }
-
I am having the same issue. >:(
-
install chrome and be done with
-
:o That is like saying, install Windows and be done with it.
-
Ok, in that case you don't have any problems. Problem solved.
-
Does that fit in with Benjamin Franklin's quotation? (Only joking, I'm a pragmatist at times as well.)
-
Debian Bug #900533 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900533) : chromium 67.0.3396.62-1 youtube video, gif's, html5, and movies no longer work
-
Debian Bug #900533 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900533) : chromium 67.0.3396.62-1 youtube video, gif's, html5, and movies no longer work
OK, thanks a lot for the info on the bug ;) It seems we'll have to wait or revert it to v66.
-
Reverting to 66 fixes it but had to get the packages from Debian Snapshot as Testing had only version 62.
-
how can i revert to version 66?
apt install chromium /testing
Lettura elenco dei pacchetti... Fatto
E: File /testing non supportato passato sulla riga di comando
what command can i use??
thanks
-
You can install SRware Iron (https://www.srware.net/en/software_srware_iron_download.php) and you will have Chrome ver. 66.0.3450.0. (It says 65 on the Linux download page, but it is actually 66.0.3450.0.)
-
Thank you! ;)
-
how can i revert to version 66?
apt install chromium /testing
You can install Chromium 62 (testing)
apt install chromium/testing
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '62.0.3202.89-1' (Debian:testing [amd64]) for 'chromium'
Selected version '62.0.3202.89-1' (Debian:testing [amd64]) for 'chromium-common' because of 'chromium'
https://packages.debian.org/search?keywords=chromium
-
@Camelot: Erm, no, really no, no and no. No way - that would be the nearly dumbest move one can make. Please have a look at the changelog. After that please ask yourself some questions:
1. Wtf is testing 62.x
2. Why do newer versions never made it to testing?
3. Is chromium/unstabe in the current state really a good idea?
I'm not argueing against FOSS - i'm argue against versions of software with many CVEs open. So - never suggest or use testing when chromium breaks - use the latest working versions from snapshots. And check the changelog if even that downgrade could be considered as a really good idea.
# apt changelog chromium
chromium-browser (67.0.3396.62-1) unstable; urgency=medium
* New upstream stable release.
- CVE-2018-6123: Use after free in Blink. Reported by Looben Yang
- CVE-2018-6124: Type confusion in Blink. Reported by Guang Gong
- CVE-2018-6125: Overly permissive policy in WebUSB. Reported by Yubico
- CVE-2018-6126: Heap buffer overflow in Skia. Reported by Ivan Fratric
- CVE-2018-6127: Use after free in indexedDB. Reported by Looben Yang
- CVE-2018-6128: uXSS in Chrome on iOS. Reported by Tomasz Bojarski
- CVE-2018-6129: Out of bounds memory access in WebRTC. Reported by Natalie
Silvanovich
- CVE-2018-6130: Out of bounds memory access in WebRTC. Reported by Natalie
Silvanovich
- CVE-2018-6131: Incorrect mutability protection in WebAssembly. Reported
by Natalie Silvanovich
- CVE-2018-6132: Use of uninitialized memory in WebRTC. Reported by Ronald
E. Crane
- CVE-2018-6133: URL spoof in Omnibox. Reported by Khalil Zhani
- CVE-2018-6134: Referrer Policy bypass in Blink. Reported by Jun Kokatsu
- CVE-2018-6135: UI spoofing in Blink. Reported by Jasper Rebane
- CVE-2018-6136: Out of bounds memory access in V8. Reported by Peter Wong
- CVE-2018-6137: Leak of visited status of page in Blink. Reported by
Michael Smith
- CVE-2018-6138: Overly permissive policy in Extensions. Reported by
François Lajeunesse-Robert
- CVE-2018-6139: Restrictions bypass in the debugger extension API.
Reported by Rob Wu
- CVE-2018-6140: Restrictions bypass in the debugger extension API.
Reported by Rob Wu
- CVE-2018-6141: Heap buffer overflow in Skia. Reported by Yangkang
- CVE-2018-6142: Out of bounds memory access in V8. Reported by Choongwoo
Han
- CVE-2018-6143: Out of bounds memory access in V8. Reported by Guang Gong
- CVE-2018-6144: Out of bounds memory access in PDFium. Reported by pdknsk
- CVE-2018-6145: Incorrect escaping of MathML in Blink. Reported by Masato
Kinugawa
- CVE-2018-6147: Password fields not taking advantage of OS protections in
Views. Reported by Michail Pishchagin
-- Michael Gilbert <mgilbert@debian.org> Wed, 30 May 2018 13:03:02 +0000
-
bringing us back to the original idea/workaround of using google-chrome...
-
The new version of Chromium I installed today (67.0.3396.79-2) seems to do the trick. So far, everything goes OK ;)