Your message dated Sun, 17 Apr 2022 16:03:49 -0400
with message-id <83ac4be9-ec03-6a8f-99a0-3a0e0bdf8...@queued.net>
and subject line Re: Bug#1009359: New security upgrade prevent Chromium from
starting
has caused the Debian Bug report #1009359,
regarding chromium: New security upgrade prevent Chromium from starting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1009359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 100.0.4896.75-1~deb11u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: cally...@free.fr, t...@security.debian.org
Dear Maintainer,
Following bug #1006822 [0] and this comment [1] I'm opening a new ticket as I
am affected by this issue too.
When starting chromium after the upgrade to 100.0.4896.75-1~deb11u1 I get the
following errors :
[35:35:0412/113953.179004:ERROR:sandbox_linux.cc(385)]
InitializeSandbox() called with multiple threads in process gpu-process.
[0412/113953.315972:ERROR:scoped_ptrace_attach.cc(27)] ptrace:
Operation not permitted (1)
* What led up to the situation?
Upgrading package from 100.0.4896.60-1~deb11u1
* What exactly did you do (or not do) that was effective (or
ineffective)?
Tried running it with --disable-gpu --disable-software-rasterizer and
* What was the outcome of this action?
I get this error instead :
[1242387:1242387:0412/120127.702912:ERROR:gpu_init.cc(446)]
Passthrough is not supported, GL is disabled, ANGLE is
* What outcome did you expect instead?
That the browser would start.
I'm on X11 and none of these worked :
> chromium --ozone-platform=wayland
>
> chromium --ozone-platform=x11
>
> chromium --no-sandbox
I do not have any particular configuration in /etc/environment or /etc/chromium
and it's worth noting that I have the EXACT same issue with the flatpack
version of chromium which stopped working with the same upgrade.
I actually tried to downgrade and got the same error. Here is the full list of
packages that were upgraded at the same time and may affect it.
The following packages will be upgraded:
chromium chromium-common chromium-sandbox codium
firefox-esr firefox-esr-l10n-fr
gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0
libjavascriptcoregtk-4.0-18 libwebkit2gtk-4.0-37
libxencall1 libxendevicemodel1 libxenevtchn1
libxenforeignmemory1 libxengnttab1 libxenhypfs1
libxenmisc4.14 libxenstore3.0 libxentoolcore1
libxentoollog1 protonvpn-gui signal-desktop
thunderbird
There is a probably a flag to force it to starts that I haven't found.
Thanks in advance for your help and for your fantastic work
LeTic
[0] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006822
[1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006822#20
-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-12-amd64 (SMP w/16 CPU threads)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chromium depends on:
ii chromium-common 100.0.4896.75-1~deb11u1
ii libasound2 1.2.4-1.1
ii libatk-bridge2.0-0 2.38.0-1
ii libatk1.0-0 2.36.0-2
ii libatomic1 10.2.1-6
ii libatspi2.0-0 2.38.0-4
ii libc6 2.31-13+deb11u2
ii libcairo2 1.16.0-5
ii libcups2 2.3.3op2-3+deb11u1
ii libdbus-1-3 1.12.20-2
ii libdrm2 2.4.104-1
ii libevent-2.1-7 2.1.12-stable-1
ii libexpat1 2.2.10-2+deb11u3
ii libflac8 1.3.3-2
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgbm1 20.3.5-1
ii libgcc-s1 10.2.1-6
ii libglib2.0-0 2.66.8-1
ii libgtk-3-0 3.24.24-4
ii libjpeg62-turbo 1:2.0.6-4
ii libjsoncpp24 1.9.4-4
ii liblcms2-2 2.12~rc1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.29-1
ii libnss3 2:3.61-1+deb11u2
ii libopenjp2-7 2.4.0-3
ii libopus0 1.3.1-0.1
ii libpango-1.0-0 1.46.2-3
ii libpng16-16 1.6.37-3
ii libpulse0 14.2-2
ii libre2-9 20210201+dfsg-1
ii libsnappy1v5 1.1.8-1
ii libstdc++6 10.2.1-6
ii libwebp6 0.6.1-2.1
ii libwebpdemux2 0.6.1-2.1
ii libwebpmux3 0.6.1-2.1
ii libx11-6 2:1.7.2-1
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxkbcommon0 1.0.3-2
ii libxml2 2.9.10+dfsg-6.7
ii libxrandr2 2:1.5.1-1
ii libxslt1.1 1.1.34-4
ii xdg-desktop-portal-gtk [xdg-desktop-portal-backend 1.8.0-1
ii zlib1g 1:1.2.11.dfsg-2+deb11u1
Versions of packages chromium recommends:
ii chromium-sandbox 100.0.4896.75-1~deb11u1
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
Versions of packages chromium-common depends on:
ii libc6 2.31-13+deb11u2
ii libstdc++6 10.2.1-6
ii libx11-6 2:1.7.2-1
ii libxext6 2:1.3.3-1.1
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-4.1
ii zlib1g 1:1.2.11.dfsg-2+deb11u1
Versions of packages chromium-common recommends:
ii chromium-sandbox 100.0.4896.75-1~deb11u1
ii fonts-liberation 1:1.07.4-11
ii gnome-shell [notification-daemon] 3.38.6-1~deb11u1
ii libgl1-mesa-dri 20.3.5-1
ii libu2f-udev 1.1.10-3
ii notification-daemon 3.20.0-4
ii system-config-printer 1.5.14-1
ii upower 0.99.11-2
Versions of packages chromium-sandbox depends on:
ii libc6 2.31-13+deb11u2
--- End Message ---
--- Begin Message ---
On 4/17/22 15:48, Anthony Callegaro wrote:
Hey Andres,
Weirdest thing happened. While trying to debug with gdb I had the trap and was
looking up some information to try to debug it further the Chromium window with
all my tabs suddendly appeared after 5 or 10 mns.
Now if I run it without gdb it works... So I guess the cache was corrupted and
somehow it fixed itself.
Thanks for your help in debugging this further.
Take care
LeTic
Thanks for the followup. To be honest, this sounds suspiciously like a
security bug for upstream, but if you can't reproduce it then I'm not
sure I can help get it fixed upstream. However, if you still have a copy
of your cache and wouldn't mind sharing it with the world (or maybe part
of it with the world, if you could delete the stuff that doesn't make
chromium crash), it would be worth filing a bug with upstream chromium
and providing a tarball of the cache to see if they can debug it. Either
way, I'll close this bug. You can still follow up here and I'll see it,
if you do have a snapshot of your cache and can provide it either here
or to https://crbug.com/.
--- End Message ---
