Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work
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') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-0.bpo.2-amd64 (SMP w/8 CPU cores) 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 ii libatk1.0-0 2.22.0-1 ii libavcodec57 7:3.2.11-1~deb9u1 ii libavformat577:3.2.11-1~deb9u1 ii libavutil55 7:3.2.11-1~deb9u1 ii libc62.24-11+deb9u3 ii libcairo21.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 libexpat12.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 libpulse010.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 libwebpdemux20.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 libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.29-2.1 ii libxss1 1:1.2.2-1 ii libxtst6 2:1.2.3-1 ii x11-utils7.7+3+b1 ii xdg-utils1.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 pn chromium-l10n pn chromium-shell pn chromium-widevine -- no debconf information
Bug#900533: The most annoying bug ever: https://bugs.debian.org/900533 , fix it!
Recently Debian Stretch introduced the most annoying bug ever:
https://bugs.debian.org/900533 ("chromium 67.0.3396.62-1: youtube video, gif's,
html5, and movies no longer work"). It affects a very very lot of Debian users.
It renders entire system completely unusable. Because ability of viewing
videos, listening to music etc using one's favorite browser is one of the main
functions of the system.
I am unable listen music using https://vk.com/audio anymore.
Bad Chromium version was installed through stretch-security repository into
every Stretch installation.
So, please fix the bug immediately!!! And make it install to usual Stretch
installations (with stable and stable-security repos enables) in next upgrade.
This is very important, so I sent this widespread mail.
==
Askar Safin
http://vk.com/safinaskar
Bug#851182: Subj
Same for this more complicated example:
#include
std::string
f (void)
{
printf ("a\n");
return "";
}
int
main (void)
{
printf ("%s\n", f ().c_str ());
}
==
Askar Safin
http://vk.com/safinaskar
Bug#851182: gdb is broken in current sid: "std::string f (void)" doesn't work
Package: gdb
Version: 7.12-4
Severity: grave
Justification: renders package unusable
Steps to reproduce:
* Create this file /h.cpp:
#include
std::string
f (void)
{
return "";
}
int
main (void)
{
f ();
}
* Then:
root@ideal-os:/# g++ -g -o h h.cpp
root@ideal-os:/# gdb ./h
GNU gdb (Debian 7.12-4) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Bug#848162: (no subject)
Moreover, this is regression. Jessie's konsole works well. Moreover, described behavior contradicts to konsole's documentation. I have konsole 4:16.08.2-2 . "konsole --help" says: -eCommand to execute. This option will catch all following arguments, so use it as the last option. And still my version of konsole has this bug. == Askar Safin
Bug#846640: lldb-3.8: lldb freezes after "run"
Package: lldb-3.8 Version: 1:3.8.1-16 Severity: grave Justification: renders package unusable lldb 3.8 freezes after "run". Same for lldb 3.9 in stretch. Details: http://bugs.debian.org/846531
Bug#846531: lldb-3.8 and lldb-3.9 are completely unusable in stretch (multiply problems); fix them or remove from scretch
Package: lldb-3.8
Version: 1:3.8.1-16
Severity: grave
Justification: renders package unusable
lldb 3.8 is unusable is Stretch. Here is list of bugs. Most of them apply to
lldb 3.9, too. Some of them apply
to lldb 3.7, too, but lldb 3.7 is somewhat usable unlike lldb 3.8 and lldb 3.9.
Steps to reproduce. I installed fresh Debian Stretch amd64 to Qemu/KVM virtual
machine (for clean experiment)
using Debian Stretch alpha 8 installer
(
http://cdimage.debian.org/cdimage/stretch_di_alpha8/amd64/iso-cd/debian-stretch-DI-alpha8-amd64-netinst.iso
).
During installation I cleared checkbox "Install standard system utilities" to
catch lldb dependency errors.
After installation I put 'APT::Install-Recommends "false";' to apt.conf for the
same reason.
Then I performed some misc. configuration and installed some misc. packages
(for example, openssh-server to
connect to this VM from outside).
Then:
debian:~# apt-get install clang-3.8 lldb-3.8
debian:~# echo 'int main (void) {}' > a.cpp
debian:~# clang-3.8 -g -o a a.cpp # See below on clang-3.8 and clang++-3.8
debian:~# lldb-3.8 ./a
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named lldb.embedded_interpreter
(lldb) target create "./a"
Current executable set to './a' (x86_64).
(lldb)
Problem 1. "ImportError: No module named lldb.embedded_interpreter".
Then I pressed "r". "\U+96272" appeared instead. This happened in ssh session
from host in X terminal (KDE's
konsole), TERM is xterm. Same is happenning on linux console in VM (TERM is
linux).
Problem 2. "\U+96272".
Then:
debian:~# cat | lldb-3.8 ./a
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named lldb.embedded_interpreter
(lldb) target create "./a"
Current executable set to './a' (x86_64).
r
(lldb) r
error: process launch failed: unable to locate lldb-server
Problem 3. "error: process launch failed: unable to locate lldb-server".
Then:
debian:~# ln -s lldb-server-3.8 /usr/bin/lldb-server
debian:~# cat | lldb-3.8 ./a
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named lldb.embedded_interpreter
(lldb) target create "./a"
Current executable set to './a' (x86_64).
r
(lldb) r
^C
^\Quit
debian:~#
And now lldb freezed.
Problem 4. lldb freezes.
And now I don't know what to do and how to fix this. It seems
http://lists.llvm.org/pipermail/lldb-dev/2016-March/009925.html is related.
Then:
debian:~# apt-get install python-lldb-3.8
This fixed that "lldb.embedded_interpreter" problem, but lldb still freezes.
Full log is here: http://paste.debian.net/900115/
Additional notes:
* This bug report is sent from that VM using "bugreport".
* lldb 3.9 has the same bugs except that "lldb.embedded_interpreter" bug.
* lldb 3.7 has some of this bugs, but it is usable. It doesn't freeze, so I
actually was able
to debug that C++ one-liner (but terminal support is still broken).
* At first I compiled the program so: "clang-3.8 -g -o a a.cpp" and reproduced
all this bugs.
Then I compiled it so: "clang++-3.8 -g -o a a.cpp" and reproduced all this bugs
again.
So:
* Fix this bugs in lldb 3.7, lldb 3.8 and lldb 3.9 before Stretch release. Or
just remove this packages from Scretch.
* Test that they work out-of-the-box. Even if the system doesn't have "standard
system utilities" and apt configured
not to install recommended packages.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lldb-3.8 depends on:
ii libc6 2.24-7
ii libedit2 3.1-20160903-2
ii libffi6 3.2.1-6
ii libgcc1 1:6.2.0-13
ii liblldb-3.8 1:3.8.1-16
ii libllvm3.81:3.8.1-16
ii libncurses5 6.0+20160917-1
ii libpython2.7 2.7.12-7
ii libstdc++66.2.0-13
ii libtinfo5 6.0+20160917-1
ii llvm-3.8-dev 1:3.8.1-16
ii zlib1g1:1.2.8.dfsg-2+b3
lldb-3.8 recommends no packages.
Versions of packages lldb-3.8 suggests:
ii python-lldb-3.8 1:3.8.1-16
-- no debconf information
Bug#762304: debootstrap doesn't unmount /proc and /sys if caught Ctrl-C
Package: debootstrap Version: 1.0.48+deb7u1 Severity: grave debootstrap doesn't unmount /proc and /sys (on my Debian GNU/Linux) if caught Ctrl-C in unpacking stage. I started debootstrap, then I changed my mind, pressed Ctrl-C and then decided to delete target (let's assume it is /tmp/wheezy). I typed "rm -r /tmp/wheezy", and then unexpectedly I saw the following: rm: cannot remove `/tmp/wheezy/proc/asound/PCH': Operation not permitted rm: cannot remove `/tmp/wheezy/proc/asound/card0/id': Operation not permitted rm: cannot remove `/tmp/wheezy/proc/asound/card0/codec#0': Operation not permitted [...] rm: cannot remove `/tmp/wheezy/proc/1/mem': Permission denied rm: cannot remove `/tmp/wheezy/proc/1/cwd': Permission denied rm: cannot remove `/tmp/wheezy/proc/1/root': Permission denied rm: cannot remove `/tmp/wheezy/proc/1/exe': Permission denied rm: cannot remove `/tmp/wheezy/proc/1/mounts': Permission denied [...] This is very frustrating output. It is similar to output of the "rm -rf /*" command, so I was scared and I decided then I am deleting all my files. Then I discovered that the files are safe. (But I think this is possible that "rm -r /tmp/wheezy/proc /tmp/wheezy/sys" somehow damages host system.) So, please, fix this bug. I gave it severity "grave" because: 1. Output of "rm -r /tmp/wheezy" makes a user very scared. 2. "rm -r" doesn't follow symbolic links. So, "rm -r /tmp/wheezy" (which includes "rm -r /tmp/wheezy/proc/1/root") fortunately didn't remove all files. But if "rm" did, then all files would be deleted. 3. debootstrap on my Debian GNU/Linux doesn't mount /dev, it mounts just /proc and /sys. But if it mounted /dev (via "mount --bind /dev /tmp/wheezy/dev" or via "mount -t devtmpfs devtmpfs /tmp/wheezy/dev"), then "rm -r /tmp/wheezy" would do "rm -r /tmp/wheezy/dev" and this would erase /dev on the host system (including /dev/null) and this would make the system unstable and it would probably crash. So, as you can see, this bug is very close to make serious problems to whole system or even to data loss. Moreover, this is possible that this bug really cases crashes or data loss on other arches (for example, kFreeBSD or Hurd), for example, because they mount /dev or something like that. Command, which reproduces the bug: debootstrap --variant=minbase wheezy /tmp/wheezy http://localhost:3142/debian Host is wheezy. == Askar Safin http://vk.com/safinaskar Moscow, Russia Moscow State University, http://msu.ru , Faculty of Mechanics and Mathematics, Department of Mathematical Logic and Theory of Algorithms .
