Your message dated Wed, 13 Jan 2021 22:53:38 +0100
with message-id <X/[email protected]>
and subject line Re: Bug#979834: chromiums shows … nothing but errors on the 
console
has caused the Debian Bug report #979834,
regarding chromiums shows … nothing but errors on the console
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 [email protected]
immediately.)


-- 
979834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979834
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 87.0.4280.141-0.1
Severity: serious
Justification: unusable as shipped

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Starting today's chromium leads to
- - nothing within the window (actually an image from the previous
  desktop)
- - tons of errors like

Xlib: sequence lost (0x1012c > 0x12e) in reply type 0x0!

  in the terminal.

After looking through 
https://peter.sh/experiments/chromium-command-line-switches/
and trying some switches I found that --gpu-sandbox-start-early helps
to get it back to working.

Some observations:

% chromium --use-gl=desktop
Xlib: sequence lost (0x1010d > 0x10f) in reply type 0x0!
Xlib: sequence lost (0x10114 > 0x116) in reply type 0x0!
Xlib: sequence lost (0x1011b > 0x11d) in reply type 0x0!
[11129:11129:0111/200209.168377:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
Xlib: sequence lost (0x1012c > 0x12e) in reply type 0x0!
Xlib: sequence lost (0x10133 > 0x135) in reply type 0x0!
Xlib: sequence lost (0x1013a > 0x13c) in reply type 0x0!
Xlib: sequence lost (0x10145 > 0x147) in reply type 0x0!
Xlib: sequence lost (0x1014c > 0x14e) in reply type 0x0!
Xlib: sequence lost (0x10153 > 0x155) in reply type 0x0!

% chromium --use-gl=desktop --gpu-sandbox-start-early
[12840:12840:0111/200259.913622:ERROR:gl_implementation.cc(282)] Failed to load 
libGL.so.1: libGL.so.1: cannot open shared object file: Operation not permitted
[12840:12840:0111/200259.923311:ERROR:viz_main_impl.cc(150)] Exiting GPU 
process due to errors during initialization

% chromium --use-gl=egl --gpu-sandbox-start-early
[25274:25274:0111/200829.114696:ERROR:gl_implementation.cc(282)] Failed to load 
libGLESv2.so.2: libGLESv2.so.2: cannot open shared object file: Operation not 
permitted
[25274:25274:0111/200829.136862:ERROR:viz_main_impl.cc(150)] Exiting GPU 
process due to errors during initialization

locate finds both /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 and 
/usr/lib/x86_64-linux-gnu/libGL.so.1

This Xlib error reminds me of #979561 (without the segfault). Unlike
in geeqie, downgrading libx11-6 from 2:1.7.0-1 to 2:1.6.12-1 doesn't
help (chromium first starts (without any switches) but crashes soon).


Cheers,
gregor


- -- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), 
(500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common      87.0.4280.141-0.1
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-2
ii  libavcodec58         7:4.3.1-5
ii  libavformat58        7:4.3.1-5
ii  libavutil56          7:4.3.1-5
ii  libc6                2.31-9
ii  libcairo2            1.16.0-5
ii  libcups2             2.3.3op1-3
ii  libdbus-1-3          1.12.20-1
ii  libdrm2              2.4.103-2
ii  libevent-2.1-7       2.1.12-stable-1
ii  libexpat1            2.2.10-1
ii  libflac8             1.3.3-2
ii  libfontconfig1       2.13.1-4.2
ii  libfreetype6         2.10.4+dfsg-1
ii  libgbm1              20.3.2-1
ii  libgcc-s1            10.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0         2.66.4-1
ii  libgtk-3-0           3.24.24-1
ii  libharfbuzz0b        2.6.7-1
ii  libicu67             67.1-5
ii  libjpeg62-turbo      1:2.0.5-2
ii  libjsoncpp24         1.9.4-4
ii  liblcms2-2           2.9-4+b1
ii  libminizip1          1.1-8+b1
ii  libnspr4             2:4.29-1
ii  libnss3              2:3.60-1
ii  libopenjp2-7         2.3.1-1
ii  libopus0             1.3.1-0.1
ii  libpango-1.0-0       1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libpng16-16          1.6.37-3
ii  libpulse0            14.0-2
ii  libre2-9             20201101+dfsg-2
ii  libsnappy1v5         1.1.8-1
ii  libstdc++6           10.2.1-6
ii  libwebp6             0.6.1-2+b1
ii  libwebpdemux2        0.6.1-2+b1
ii  libwebpmux3          0.6.1-2+b1
ii  libx11-6             2:1.7.0-1
ii  libx11-xcb1          2:1.7.0-1
ii  libxcb1              1.14-2.1
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  libxml2              2.9.10+dfsg-6.3+b1
ii  libxrandr2           2:1.5.1-1
ii  libxslt1.1           1.1.34-4
ii  zlib1g               1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  87.0.4280.141-0.1

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-9
ii  libstdc++6  10.2.1-6
ii  libx11-6    2:1.7.0-1
ii  libxext6    2:1.3.3-1.1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-2
ii  zlib1g      1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox       87.0.4280.141-0.1
ii  fonts-liberation       1:1.07.4-11
ii  libgl1-mesa-dri        20.3.2-1
pn  libu2f-udev            <none>
ii  notification-daemon    3.20.0-4
pn  system-config-printer  <none>
pn  upower                 <none>

Versions of packages chromium-sandbox depends on:
ii  libc6  2.31-9

- -- no debconf information

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl/8pVdfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZrdw//fN6gc9NmOR2K54WZM6Gyh6PK8PRNuNNHQT+p4XkxYjh8aFP0n+/U82NG
edtuEWGqyOVh1hChwNmbvqr6FUTRrx21e6RN1j2sMcEM+gapyx30dKG1FVNKuJtW
BK2jXoQN4tGHx9vaQlIvkjYaO+bcFdKLFMId5fHJ4yk2M3LVBOt1UOpUGKHVtME9
8HB37St+7+Z/v7qk0E6eYK2DUufTS5cgnAfGzHVDMIrUP8RrgZ7ORH3ue8nB0fMT
DS2ajuyj6vTboZDZnp4axPBTOA1KNV50zlVRdRGnZkZIIbxtnExFJH0ckvXdrbgb
SI6WXvPyjSEe76wEMFNt9RmNxWhTAPq+37+oBGmirxt2oPrHDoSks2TzaQRJ7YCQ
9PavyePKs0MTIJPx6zF3M3fimwP9RfUB5LNwCEIqRP2O2wY1e20YUtEb9ZXQ22nq
cy3cU3yLGpVQ4gxX2AYyU2eK08abliLEd7/m2pXBC5eCJfGTr1NddoJ1KH2i4Dn6
5erhB+PlGoB9E/a8VGq6xrDB5AmrdE20lZAY4mdflOrN1cAnSsKeKfr7nCgibZKE
qxVw5IQHflrvULcXC+XfVvXGfvjhVqoYpu0bh6SMt0orYM5HaaCVPDpclP6p4v4H
b4EfsDPcK01JxZXc0Ha7yWlW+gVwSVdzadVh7g0i9pJOWIjbri4=
=UANR
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
On Wed, 13 Jan 2021 16:05:33 +0100, nicoo wrote:

> Could you try to reproduce with `--temp-profile`, to eliminate the possibility
> of it being something specific to your system?

Good idea, thanks for the proposal.

So, after turning off --gpu-sandbox-start-early:

% chromium --temp-profile

And yes, it just works.

Hm.

So let's get funky, leave --gpu-sandbox-start-early turned off, and

.
.
.

it still works with my usual profile.

% chromium               

(chromium:28408): Gtk-WARNING **: 22:47:12.891: Theme parsing error: 
gtk.css:4:25: The style property GtkRange:stepper-size is deprecated and 
shouldn't be used anymore. It will be removed in a future version
[28447:28447:0113/224712.955750:ERROR:gl_implementation.cc(282)] Failed to load 
libGL.so.1: libGL.so.1: cannot open shared object file: Operation not permitted
[28447:28447:0113/224712.958859:ERROR:viz_main_impl.cc(150)] Exiting GPU 
process due to errors during initialization
Fontconfig error: Cannot load default config file(283)] After loading Root 
Certs, loaded==false: NSS error code: -8018

and then I "see" something.
 

So, whatever that was, it doesn't occur anymore, hence closing the
bug.

Thanks for nudging me into trying again :)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Beatles

Attachment: signature.asc
Description: Digital Signature


--- End Message ---

Reply via email to