Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work
219 views
Skip to first unread message
rcm0502
Jun 3, 2018, 10:40:03 AM6/3/18
to
Hi.
I have also been bitten by this bug, resolved by downgrading back to chromium 66.0.3359.181-1 and then watching Youtube videos or using web video chat applications worked again.
Hoping for a resolution soon enough.
Thanks,
R
On Thu, 31 May 2018 18:34:46 -0400 "Justin P." wrote:
> Package: chromium
> Version: 67.0.3396.62-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
> * What led up to the situation?
>
> Can't use video on youtube. Gif's no longer work. And I cannot get media to play. This started after upgrading from 66.0.3359.181-1 to 67.0.3396.62-1
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> Reverting the package was the only solution I could find. It appears the app build may be missing some flags in the build. I found this that had similar errors to my situation https://groups.google.com/a/chromium.org/forum/?nomobile=true#!msg/android-webview-dev/oVjyFhhxOQ8/ns8q9uPrCAAJ
>
> * What was the outcome of this action?
>
> chromium 66.0.3359.181-1 was reinstalled, video is working again.
>
> * What outcome did you expect instead?
>
> chromium 67.0.3396.62-1 video should work after install.
>
> ----Chromium Log while trying to play files----
> [129:160:0531/181749.318090:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
> [129:129:0531/181749.320645:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
> [129:160:0531/181749.352209:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
> [129:129:0531/181749.354280:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
> [129:160:0531/181749.551754:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
> [129:129:0531/181749.559473:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
> [129:160:0531/181750.431299:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
> [129:129:0531/181750.433293:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
> libpng warning: iCCP: known incorrect sRGB profile
>
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages chromium depends on:
> ii chromium-common 67.0.3396.62-1
> ii libasound2 1.1.6-1
> ii libatk-bridge2.0-0 2.26.2-1
> ii libatk1.0-0 2.28.1-1
> ii libavcodec57 7:3.4.2-2+b1
> ii libavformat57 7:3.4.2-2+b1
> ii libavutil55 7:3.4.2-2+b1
> ii libc6 2.27-3
I have also been bitten by this bug, resolved by downgrading back to chromium 66.0.3359.181-1 and then watching Youtube videos or using web video chat applications worked again.
Hoping for a resolution soon enough.
Thanks,
R
On Thu, 31 May 2018 18:34:46 -0400 "Justin P." wrote:
> Package: chromium
> Version: 67.0.3396.62-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
> * What led up to the situation?
>
> Can't use video on youtube. Gif's no longer work. And I cannot get media to play. This started after upgrading from 66.0.3359.181-1 to 67.0.3396.62-1
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> Reverting the package was the only solution I could find. It appears the app build may be missing some flags in the build. I found this that had similar errors to my situation https://groups.google.com/a/chromium.org/forum/?nomobile=true#!msg/android-webview-dev/oVjyFhhxOQ8/ns8q9uPrCAAJ
>
> * What was the outcome of this action?
>
> chromium 66.0.3359.181-1 was reinstalled, video is working again.
>
> * What outcome did you expect instead?
>
> chromium 67.0.3396.62-1 video should work after install.
>
> ----Chromium Log while trying to play files----
> [129:160:0531/181749.318090:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
> [129:129:0531/181749.320645:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
> [129:160:0531/181749.352209:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
> [129:129:0531/181749.354280:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN
> [129:160:0531/181749.551754:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
> [129:129:0531/181749.559473:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
> [129:160:0531/181750.431299:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"audio decoder initialization failed"}
> [129:129:0531/181750.433293:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DECODER_ERROR_NOT_SUPPORTED
> libpng warning: iCCP: known incorrect sRGB profile
>
>
> -- System Information:
> Debian Release: buster/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages chromium depends on:
> ii chromium-common 67.0.3396.62-1
> ii libasound2 1.1.6-1
> ii libatk-bridge2.0-0 2.26.2-1
> ii libatk1.0-0 2.28.1-1
> ii libavcodec57 7:3.4.2-2+b1
> ii libavformat57 7:3.4.2-2+b1
> ii libavutil55 7:3.4.2-2+b1
> ii libc6 2.27-3
jim_p
Jun 6, 2018, 11:40:02 AM6/6/18
to
Package: chromium
Version: 67.0.3396.62-1
Followup-For: Bug #900533
Dear Maintainer,
Is there any info on when this issue could be fixed? It has been a week since
this bug report was opened and there are no official comments here regarding
any progress, neither some newer source package suggesting there is a patch for
it or a fix.
I personally use chromium for its superb html5-based multimedia support. Now
that this support is completely broken, I have no reason to use it anymore and
I think of moving to chrome.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.16.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
ii libavformat57 10:3.4.2-dmo3
ii libavutil55 10:3.4.2-dmo3
ii libc6 2.27-3
ii libcairo2 1.15.10-3
ii libcups2 2.2.7-5
ii libdbus-1-3 1.12.8-2
ii libevent-2.1-6 2.1.8-stable-4
ii libexpat1 2.2.5-3
ii libflac8 1.3.2-3
ii libfontconfig1 2.13.0-5
ii libfreetype6 2.8.1-2
ii libgcc1 1:8.1.0-5
ii libgdk-pixbuf2.0-0 2.36.11-2
ii libglib2.0-0 2.56.1-2
ii libgtk-3-0 3.22.29-3
ii libharfbuzz0b 1.7.6-1+b1
ii libicu60 60.2-6
ii libjpeg62-turbo 1:1.5.2-2+b1
ii liblcms2-2 2.9-1
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.19-3
ii libnss3 2:3.37.1-1
ii libopenjp2-7 2.3.0-1
ii libopus0 1.3~beta+20180518-1
ii libpango-1.0-0 1.42.0-1
ii libpangocairo-1.0-0 1.42.0-1
ii libpng16-16 1.6.34-1
ii libpulse0 11.1-5
ii libre2-4 20180301+dfsg-1
ii libsnappy1v5 1.1.7-1
ii libstdc++6 8.1.0-5
ii libvpx5 1.7.0-3
ii libwebp6 0.6.1-2
ii libwebpdemux2 0.6.1-2
ii libwebpmux3 0.6.1-2
ii libx11-6 2:1.6.5-1
ii libx11-xcb1 2:1.6.5-1
ii libxcb1 1.13-1
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.15-1
ii libxdamage1 1:1.1.4-3
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-1
ii libxi6 2:1.7.9-1
ii libxml2 2.9.4+dfsg1-7
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.32-2
ii libxss1 1:1.2.2-1+b2
ii libxtst6 2:1.2.3-1
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages chromium recommends:
ii fonts-liberation 1:1.07.4-7
ii libgl1-mesa-dri 18.0.4-1
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
-- no debconf information
Version: 67.0.3396.62-1
Followup-For: Bug #900533
Dear Maintainer,
Is there any info on when this issue could be fixed? It has been a week since
this bug report was opened and there are no official comments here regarding
any progress, neither some newer source package suggesting there is a patch for
it or a fix.
I personally use chromium for its superb html5-based multimedia support. Now
that this support is completely broken, I have no reason to use it anymore and
I think of moving to chrome.
-- System Information:
Debian Release: buster/sid
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.16.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii chromium-common 67.0.3396.62-1
ii libasound2 1.1.6-1
ii libatk-bridge2.0-0 2.26.2-1
ii libatk1.0-0 2.28.1-1
ii libavcodec57 10:3.4.2-dmo3
ii chromium-common 67.0.3396.62-1
ii libasound2 1.1.6-1
ii libatk-bridge2.0-0 2.26.2-1
ii libatk1.0-0 2.28.1-1
ii libavformat57 10:3.4.2-dmo3
ii libavutil55 10:3.4.2-dmo3
ii libc6 2.27-3
ii libcairo2 1.15.10-3
ii libcups2 2.2.7-5
ii libdbus-1-3 1.12.8-2
ii libevent-2.1-6 2.1.8-stable-4
ii libexpat1 2.2.5-3
ii libflac8 1.3.2-3
ii libfontconfig1 2.13.0-5
ii libfreetype6 2.8.1-2
ii libgcc1 1:8.1.0-5
ii libgdk-pixbuf2.0-0 2.36.11-2
ii libglib2.0-0 2.56.1-2
ii libgtk-3-0 3.22.29-3
ii libharfbuzz0b 1.7.6-1+b1
ii libicu60 60.2-6
ii libjpeg62-turbo 1:1.5.2-2+b1
ii liblcms2-2 2.9-1
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.19-3
ii libnss3 2:3.37.1-1
ii libopenjp2-7 2.3.0-1
ii libopus0 1.3~beta+20180518-1
ii libpango-1.0-0 1.42.0-1
ii libpangocairo-1.0-0 1.42.0-1
ii libpng16-16 1.6.34-1
ii libpulse0 11.1-5
ii libre2-4 20180301+dfsg-1
ii libsnappy1v5 1.1.7-1
ii libstdc++6 8.1.0-5
ii libvpx5 1.7.0-3
ii libwebp6 0.6.1-2
ii libwebpdemux2 0.6.1-2
ii libwebpmux3 0.6.1-2
ii libx11-6 2:1.6.5-1
ii libx11-xcb1 2:1.6.5-1
ii libxcb1 1.13-1
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.15-1
ii libxdamage1 1:1.1.4-3
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-1
ii libxi6 2:1.7.9-1
ii libxml2 2.9.4+dfsg1-7
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.32-2
ii libxss1 1:1.2.2-1+b2
ii libxtst6 2:1.2.3-1
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages chromium recommends:
ii fonts-liberation 1:1.07.4-7
ii libgl1-mesa-dri 18.0.4-1
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
-- no debconf information
Mike Brodbelt
Jun 6, 2018, 3:20:02 PM6/6/18
to
Same problem as other reporters, also resolved by downgrading chromium,
chromium-common, and chromium-l10n to 66.0.3359.181-1.
chromium-common, and chromium-l10n to 66.0.3359.181-1.
Michael Gilbert
Jun 7, 2018, 8:20:02 PM6/7/18
to
control: tag -1 confirmed, help
On Wed, Jun 6, 2018 at 11:37 AM, jim_p wrote:
> Is there any info on when this issue could be fixed? It has been a week since
> this bug report was opened and there are no official comments here regarding
> any progress, neither some newer source package suggesting there is a patch for
> it or a fix.
It's pretty clearly an issue with the ffmpeg demuxer. I'll debug it
when I find free time. Others willing to help might move things a bit
faster.
Best wishes,
Mike
On Wed, Jun 6, 2018 at 11:37 AM, jim_p wrote:
> Is there any info on when this issue could be fixed? It has been a week since
> this bug report was opened and there are no official comments here regarding
> any progress, neither some newer source package suggesting there is a patch for
> it or a fix.
when I find free time. Others willing to help might move things a bit
faster.
Best wishes,
Mike
Lothar Braun
Jun 9, 2018, 3:20:02 AM6/9/18
to
The problem persists with 67.0.3396.62-2.
Josef Kufner
Jun 9, 2018, 4:40:02 AM6/9/18
to
Jose A. Fernandez Gonzalez wrote, on 8.6.2018 19:32:
> [...] I think the problem is that chromium-67 is
> looking for ffmpeg-4 and the version available in Debian unstable is
> ffmpeg-3.4.2
There is no such dependency specified in the chromium package. That is
certainly wrong.
> [...] I think the problem is that chromium-67 is
> looking for ffmpeg-4 and the version available in Debian unstable is
> ffmpeg-3.4.2
There is no such dependency specified in the chromium package. That is
certainly wrong.
Jose A. Fernandez Gonzalez
Jun 9, 2018, 5:50:03 AM6/9/18
to
When I said ffmpeg I meant ffmpeg libraries, chromium depends on several ffmpeg libraries (libavcodec, libavformat, libavutil, ...) and when I comment that chromium-67 is looking for ffmpeg-4 is because in other distros (archlinux, gentoo, ...) they are packaging chromium-67 pointing to ffmpeg-4 (libavcodec, libavformat, libavutil, ... from ffmpeg-4).
$ LC_ALL=C apt depends chromium
chromium
Depends: libasound2 (>= 1.0.16)
Depends: libatk-bridge2.0-0 (>= 2.5.3)
Depends: libatk1.0-0 (>= 1.12.4)
|Depends: libavcodec57 (>= 7:3.4.2) <<<------ (*)
Depends: libavcodec-extra57 (>= 7:3.4.2) <<<------ (*)
Depends: libavformat57 (>= 7:3.4.2) <<<------ (*)
Depends: libavutil55 (>= 7:3.4.2) <<<------ (*)
Depends: libc6 (>= 2.27)
Depends: libcairo2 (>= 1.6.0)
Depends: libcups2 (>= 1.4.0)
Depends: libdbus-1-3 (>= 1.9.14)
Depends: libevent-2.1-6 (>= 2.1.8-stable)
Depends: libexpat1 (>= 2.0.1)
Depends: libflac8 (>= 1.3.0)
Depends: libfontconfig1 (>= 2.12.6)
Depends: libfreetype6 (>= 2.3.9)
Depends: libgcc1 (>= 1:4.0)
Depends: libgdk-pixbuf2.0-0 (>= 2.22.0)
Depends: libglib2.0-0 (>= 2.31.8)
Depends: libgtk-3-0 (>= 3.9.10)
Depends: libharfbuzz0b (>= 1.6.0)
Depends: libicu60 (>= 60.1-1~)
Depends: libjpeg62-turbo (>= 1.5.0)
Depends: liblcms2-2 (>= 2.2+git20110628)
Depends: libminizip1 (>= 1.1)
Depends: libnspr4 (>= 2:4.9-2~)
Depends: libnss3 (>= 2:3.22)
Depends: libopenjp2-7 (>= 2.2.0)
Depends: libopus0 (>= 1.1)
Depends: libpango-1.0-0 (>= 1.14.0)
Depends: libpangocairo-1.0-0 (>= 1.14.0)
Depends: libpng16-16 (>= 1.6.2-1)
Depends: libpulse0 (>= 0.99.1)
Depends: libre2-4 (>= 20160901)
Depends: libsnappy1v5
Depends: libstdc++6 (>= 6)
Depends: libvpx5 (>= 1.6.0)
Depends: libwebp6 (>= 0.5.1)
Depends: libwebpdemux2 (>= 0.5.1)
Depends: libwebpmux3 (>= 0.6.1-2)
Depends: libx11-6 (>= 2:1.4.99.1)
Depends: libx11-xcb1
Depends: libxcb1 (>= 1.6)
Depends: libxcomposite1 (>= 1:0.3-1)
Depends: libxcursor1 (>> 1.1.2)
Depends: libxdamage1 (>= 1:1.1)
Depends: libxext6
Depends: libxfixes3 (>= 1:5.0)
Depends: libxi6 (>= 2:1.2.99.4)
Depends: libxml2 (>= 2.7.4)
Depends: libxrandr2 (>= 2:1.2.99.3)
Depends: libxrender1
Depends: libxslt1.1 (>= 1.1.25)
Depends: libxss1
Depends: libxtst6
Depends: zlib1g (>= 1:1.2.2)
Depends: chromium-common (= 67.0.3396.62-2)
Conflicts: <libgl1-mesa-swx11>
Conflicts: <libnettle4>
Conflicts: libsecret-1-0 (<< 0.18)
Recommends: libgl1-mesa-dri
Recommends: fonts-liberation
Suggests: chromium-l10n
Suggests: chromium-shell
Suggests: chromium-driver
chromium
Depends: libasound2 (>= 1.0.16)
Depends: libatk-bridge2.0-0 (>= 2.5.3)
Depends: libatk1.0-0 (>= 1.12.4)
|Depends: libavcodec57 (>= 7:3.4.2) <<<------ (*)
Depends: libavcodec-extra57 (>= 7:3.4.2) <<<------ (*)
Depends: libavformat57 (>= 7:3.4.2) <<<------ (*)
Depends: libavutil55 (>= 7:3.4.2) <<<------ (*)
Depends: libc6 (>= 2.27)
Depends: libcairo2 (>= 1.6.0)
Depends: libcups2 (>= 1.4.0)
Depends: libdbus-1-3 (>= 1.9.14)
Depends: libevent-2.1-6 (>= 2.1.8-stable)
Depends: libexpat1 (>= 2.0.1)
Depends: libflac8 (>= 1.3.0)
Depends: libfontconfig1 (>= 2.12.6)
Depends: libfreetype6 (>= 2.3.9)
Depends: libgcc1 (>= 1:4.0)
Depends: libgdk-pixbuf2.0-0 (>= 2.22.0)
Depends: libglib2.0-0 (>= 2.31.8)
Depends: libgtk-3-0 (>= 3.9.10)
Depends: libharfbuzz0b (>= 1.6.0)
Depends: libicu60 (>= 60.1-1~)
Depends: libjpeg62-turbo (>= 1.5.0)
Depends: liblcms2-2 (>= 2.2+git20110628)
Depends: libminizip1 (>= 1.1)
Depends: libnspr4 (>= 2:4.9-2~)
Depends: libnss3 (>= 2:3.22)
Depends: libopenjp2-7 (>= 2.2.0)
Depends: libopus0 (>= 1.1)
Depends: libpango-1.0-0 (>= 1.14.0)
Depends: libpangocairo-1.0-0 (>= 1.14.0)
Depends: libpng16-16 (>= 1.6.2-1)
Depends: libpulse0 (>= 0.99.1)
Depends: libre2-4 (>= 20160901)
Depends: libsnappy1v5
Depends: libstdc++6 (>= 6)
Depends: libvpx5 (>= 1.6.0)
Depends: libwebp6 (>= 0.5.1)
Depends: libwebpdemux2 (>= 0.5.1)
Depends: libwebpmux3 (>= 0.6.1-2)
Depends: libx11-6 (>= 2:1.4.99.1)
Depends: libx11-xcb1
Depends: libxcb1 (>= 1.6)
Depends: libxcomposite1 (>= 1:0.3-1)
Depends: libxcursor1 (>> 1.1.2)
Depends: libxdamage1 (>= 1:1.1)
Depends: libxext6
Depends: libxfixes3 (>= 1:5.0)
Depends: libxi6 (>= 2:1.2.99.4)
Depends: libxml2 (>= 2.7.4)
Depends: libxrandr2 (>= 2:1.2.99.3)
Depends: libxrender1
Depends: libxslt1.1 (>= 1.1.25)
Depends: libxss1
Depends: libxtst6
Depends: zlib1g (>= 1:1.2.2)
Depends: chromium-common (= 67.0.3396.62-2)
Conflicts: <libgl1-mesa-swx11>
Conflicts: <libnettle4>
Conflicts: libsecret-1-0 (<< 0.18)
Recommends: libgl1-mesa-dri
Recommends: fonts-liberation
Suggests: chromium-l10n
Suggests: chromium-shell
Suggests: chromium-driver
Regards.
ZevenOS
Jul 14, 2018, 10:20:02 AM7/14/18
to
I can confirm this bug in stable security.
It needs to be reopened.
Applying the patch mentioned by Jiri Palece (
https://salsa.debian.org/chromium-team/chromium/commit/402b98bb1079079a788696650e0a922b1e16bed8
)
Fixes the issue for me.
So I advise to rebuild chromium with it.
I built this package for Neptune so our users don't have a broken
browser for too long.
Greetings
Leszek Lesner
--
ZevenOS / Neptune Team
http://www.zevenos.com / http://www.neptuneos.com
Leszek Lesner <les...@zevenos.com>
It needs to be reopened.
Applying the patch mentioned by Jiri Palece (
https://salsa.debian.org/chromium-team/chromium/commit/402b98bb1079079a788696650e0a922b1e16bed8
)
Fixes the issue for me.
So I advise to rebuild chromium with it.
I built this package for Neptune so our users don't have a broken
browser for too long.
Greetings
Leszek Lesner
--
ZevenOS / Neptune Team
http://www.zevenos.com / http://www.neptuneos.com
Leszek Lesner <les...@zevenos.com>
Askar Safin
Jul 26, 2018, 4:10:02 AM7/26/18
to
Package: chromium
Version: 67.0.3396.87-1~deb9u1
Followup-For: Bug #900533
My system is Debian Stretch amd64. My sources.list is this:
===
deb http://mirror.yandex.ru/debian stretch main non-free contrib
deb-src http://mirror.yandex.ru/debian stretch main non-free contrib
deb http://security.debian.org/debian-security stretch/updates main contrib non-free
deb-src http://security.debian.org/debian-security stretch/updates main contrib non-free
deb http://mirror.yandex.ru/debian stretch-updates main contrib non-free
deb-src http://mirror.yandex.ru/debian stretch-updates main contrib non-free
deb http://mirror.yandex.ru/debian stretch-backports main
deb-src http://mirror.yandex.ru/debian stretch-backports main
===
The bug still exists in latest version in stable security repo 67.0.3396.87-1~deb9u1 as of today (2018-07-26 UTC+03).
Steps to reproduce. Log in to https://vk.com , then go to https://vk.com/audio . You will not be able to listen any audio.
There is no bug in latest version in stable repo 63.0.3239.84-1~deb9u1 as of today. So, this is clear regression,
introduced by security update.
That daily motion link doesn't work in stable security, too (note: daily motion is banned in Russia).
https://hpr.dogphilosophy.net/test/ doesn't work, too.
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
ii libatk1.0-0 2.22.0-1
ii libavcodec57 7:3.2.11-1~deb9u1
ii libavformat57 7:3.2.11-1~deb9u1
ii libavutil55 7:3.2.11-1~deb9u1
ii libc6 2.24-11+deb9u3
ii libcairo2 1.14.8-1
ii libcups2 2.2.1-8+deb9u2
ii libdbus-1-3 1.10.26-0+deb9u1
ii libevent-2.0-5 2.0.21-stable-3
ii libexpat1 2.2.0-2+deb9u1
ii libflac8 1.3.2-1
ii libfontconfig1 2.11.0-6.7+b1
ii libfreetype6 2.6.3-3.2
ii libgcc1 1:6.3.0-18+deb9u1
ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u2
ii libglib2.0-0 2.50.3-2
ii libgtk2.0-0 2.24.31-2
ii libicu57 57.1-6+deb9u2
ii libjpeg62-turbo 1:1.5.1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.12-6
ii libnss3 2:3.26.2-1.1+deb9u1
ii libopus0 1.2~alpha2-1
ii libpango-1.0-0 1.40.5-1
ii libpangocairo-1.0-0 1.40.5-1
ii libpng16-16 1.6.28-1
ii libpulse0 10.0-1+deb9u1
ii libre2-3 20170101+dfsg-1
ii libsnappy1v5 1.1.3-3
ii libstdc++6 6.3.0-18+deb9u1
ii libvpx4 1.6.1-3+deb9u1
ii libwebp6 0.5.2-1
ii libwebpdemux2 0.5.2-1
ii libwebpmux2 0.5.2-1
ii libx11-6 2:1.6.4-3
ii libx11-xcb1 2:1.6.4-3
ii libxcb1 1.12-1
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.14-1+deb9u1
ii libxdamage1 1:1.1.4-2+b3
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.3-1
ii x11-utils 7.7+3+b1
ii xdg-utils 1.1.1-1+deb9u1
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages chromium recommends:
ii fonts-liberation 1:1.07.4-2
ii libgl1-mesa-dri 13.0.6-1+b2
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
pn chromium-widevine <none>
-- no debconf information
Version: 67.0.3396.87-1~deb9u1
Followup-For: Bug #900533
My system is Debian Stretch amd64. My sources.list is this:
===
deb http://mirror.yandex.ru/debian stretch main non-free contrib
deb-src http://mirror.yandex.ru/debian stretch main non-free contrib
deb http://security.debian.org/debian-security stretch/updates main contrib non-free
deb-src http://security.debian.org/debian-security stretch/updates main contrib non-free
deb http://mirror.yandex.ru/debian stretch-updates main contrib non-free
deb-src http://mirror.yandex.ru/debian stretch-updates main contrib non-free
deb http://mirror.yandex.ru/debian stretch-backports main
deb-src http://mirror.yandex.ru/debian stretch-backports main
===
The bug still exists in latest version in stable security repo 67.0.3396.87-1~deb9u1 as of today (2018-07-26 UTC+03).
Steps to reproduce. Log in to https://vk.com , then go to https://vk.com/audio . You will not be able to listen any audio.
There is no bug in latest version in stable repo 63.0.3239.84-1~deb9u1 as of today. So, this is clear regression,
introduced by security update.
That daily motion link doesn't work in stable security, too (note: daily motion is banned in Russia).
https://hpr.dogphilosophy.net/test/ doesn't work, too.
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.15.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Foreign Architectures: i386
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii libasound2 1.1.3-5
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii libatk1.0-0 2.22.0-1
ii libavcodec57 7:3.2.11-1~deb9u1
ii libavformat57 7:3.2.11-1~deb9u1
ii libavutil55 7:3.2.11-1~deb9u1
ii libc6 2.24-11+deb9u3
ii libcairo2 1.14.8-1
ii libcups2 2.2.1-8+deb9u2
ii libdbus-1-3 1.10.26-0+deb9u1
ii libevent-2.0-5 2.0.21-stable-3
ii libexpat1 2.2.0-2+deb9u1
ii libflac8 1.3.2-1
ii libfontconfig1 2.11.0-6.7+b1
ii libfreetype6 2.6.3-3.2
ii libgcc1 1:6.3.0-18+deb9u1
ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u2
ii libglib2.0-0 2.50.3-2
ii libgtk2.0-0 2.24.31-2
ii libicu57 57.1-6+deb9u2
ii libjpeg62-turbo 1:1.5.1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.12-6
ii libnss3 2:3.26.2-1.1+deb9u1
ii libopus0 1.2~alpha2-1
ii libpango-1.0-0 1.40.5-1
ii libpangocairo-1.0-0 1.40.5-1
ii libpng16-16 1.6.28-1
ii libpulse0 10.0-1+deb9u1
ii libre2-3 20170101+dfsg-1
ii libsnappy1v5 1.1.3-3
ii libstdc++6 6.3.0-18+deb9u1
ii libvpx4 1.6.1-3+deb9u1
ii libwebp6 0.5.2-1
ii libwebpdemux2 0.5.2-1
ii libwebpmux2 0.5.2-1
ii libx11-6 2:1.6.4-3
ii libx11-xcb1 2:1.6.4-3
ii libxcb1 1.12-1
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.14-1+deb9u1
ii libxdamage1 1:1.1.4-2+b3
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-1
ii libxi6 2:1.7.9-1
ii libxml2 2.9.4+dfsg1-2.2+deb9u2
ii libxfixes3 1:5.0.3-1
ii libxi6 2:1.7.9-1
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.29-2.1
ii libxrender1 1:0.9.10-1
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.3-1
ii x11-utils 7.7+3+b1
ii xdg-utils 1.1.1-1+deb9u1
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages chromium recommends:
ii libgl1-mesa-dri 13.0.6-1+b2
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
-- no debconf information
0 new messages