Bug#1006822: Chromium

2022-03-28 Thread Rpnpif

Hello,

I have the same issue: chromium dose not start with this message:

ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple 
threads in process gpu-process.


I have not wayland.


chromium --ozone-platform=wayland

chromium --ozone-platform=x11

chromium --no-sandbox


None of that does no work.

Regards

--
Rpnpif



Bug#1006822: Chromium

2022-03-15 Thread Andreas Juch
Hi,

Thanks for your reply! I must apologize for the late answer, it seems gmail
filtered the mail.

I previously had set CHROMIUM_FLAGS in /etc/environment. These used to work
for me:

CHROMIUM_FLAGS="--enable-features=UseOzonePlatform --ozone-platform=wayland"

I removed chromium and did dpkg --purge chromium, so the /etc/chromium
directory was gone and moved my ~/.config/chromium directory away. I tried
the three commands:

Wayland doesn't work:

chromium --ozone-platform=wayland
[8051:8051:0315/214032.418318:ERROR:cursor_loader.cc(116)] Failed to load a
platform cursor of type kNull
[8097:8097:0315/214032.422594:ERROR:gpu_init.cc(440)] Passthrough is not
supported, GL is egl, ANGLE is
[8097:8097:0315/214032.425174:ERROR:sandbox_linux.cc(377)]
InitializeSandbox() called with multiple threads in process gpu-process.
[8051:8126:0315/214032.584157:ERROR:wayland_event_watcher.cc(301)] Fatal
Wayland communication error Broken pipe.

X11 works, but looks ugly:

chromium --ozone-platform=x11
libva error: vaGetDriverNameByIndex() failed with unknown libva error,
driver_name = (null)
[8253:8253:0315/214128.450682:ERROR:sandbox_linux.cc(377)]
InitializeSandbox() called with multiple threads in process gpu-process.
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated

--no-sandbox also works (but is x11)

chromium --no-sandbox
libva error: vaGetDriverNameByIndex() failed with unknown libva error,
driver_name = (null)
[8415:8415:0315/214200.223436:ERROR:sandbox_linux.cc(377)]
InitializeSandbox() called with multiple threads in process gpu-process.
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[8415:8415:0315/214203.784734:ERROR:gl_surface_presentation_helper.cc(260)]
GetVSyncParametersIfAvailable() failed for 1 times!

chromium without any arguments also works in x11 mode. Probably I forgot to
clear something, or the reinstall did something.


Bug#1006822: chromium: Chromium doesn't start on sway after latest securty update

2022-03-05 Thread Andres Salomon

On Sat, 05 Mar 2022 21:34:29 +0100 Andreas Juch wrote:
> Package: chromium
> Version: 99.0.4844.51-1~deb11u1
> Severity: important
> X-Debbugs-Cc: t...@security.debian.org
>
> Dear Maintainer,
>
> After the latest security update of chromium from 98 to 99 chromium
> doesn't start any more. I'm using wayland with the sway window manager.
>
> The messages in the terminal are:
>
> [6788:6788:0305/212730.897589:ERROR:gpu_init.cc(440)] Passthrough is 
not supported, GL is egl, ANGLE is
> [6788:6788:0305/212730.900388:ERROR:sandbox_linux.cc(377)] 
InitializeSandbox() called with multiple threads in process gpu-process.
> [6742:6742:0305/212730.912434:ERROR:cursor_loader.cc(116)] Failed to 
load a platform cursor of type kNull
> [6742:6838:0305/212731.190121:ERROR:wayland_event_watcher.cc(301)] 
Fatal Wayland communication error Broken pipe.

>
> I already commented out all CHROMIUM_FLAGS and moved away
> .config/chromium, but it still doesn't start.
>
> With WAYLAND_DEBUG=1 there is more output, but I don't know if its

> relevant:


Please try running chromium the following ways, and let me know which 
does and doesn't work:



chromium --ozone-platform=wayland

chromium --ozone-platform=x11

chromium --no-sandbox


Also, I don't know how you cleared CHROMIUM_FLAGS, but if you didn't 
already: try moving /etc/chromium* out of the way and reinstalling the 
package to make sure that you don't have any random flags set.




Bug#1006822: chromium: Chromium doesn't start on sway after latest securty update

2022-03-05 Thread Andreas Juch
Package: chromium
Version: 99.0.4844.51-1~deb11u1
Severity: important
X-Debbugs-Cc: t...@security.debian.org

Dear Maintainer,

After the latest security update of chromium from 98 to 99 chromium
doesn't start any more. I'm using wayland with the sway window manager.

The messages in the terminal are:

[6788:6788:0305/212730.897589:ERROR:gpu_init.cc(440)] Passthrough is not 
supported, GL is egl, ANGLE is
[6788:6788:0305/212730.900388:ERROR:sandbox_linux.cc(377)] InitializeSandbox() 
called with multiple threads in process gpu-process.
[6742:6742:0305/212730.912434:ERROR:cursor_loader.cc(116)] Failed to load a 
platform cursor of type kNull
[6742:6838:0305/212731.190121:ERROR:wayland_event_watcher.cc(301)] Fatal 
Wayland communication error Broken pipe.

I already commented out all CHROMIUM_FLAGS and moved away
.config/chromium, but it still doesn't start.

With WAYLAND_DEBUG=1 there is more output, but I don't know if its
relevant:

[1000778.947]  -> wl_display@1.get_registry(new id wl_registry@2)
[1000778.967]  -> wl_disp...@1.sync(new id wl_callback@3)
[1000779.037] wl_display@1.delete_id(3)
[1000779.052] wl_registry@2.global(1, "wl_shm", 1)
[1000779.065]  -> wl_regis...@2.bind(1, "wl_shm", 1, new id [unknown]@4)
[1000779.085] wl_registry@2.global(2, "wl_drm", 2)
[1000779.091]  -> wl_regis...@2.bind(2, "wl_drm", 2, new id [unknown]@5)
[1000779.100]  -> wl_disp...@1.sync(new id wl_callback@6)
[1000779.103] wl_registry@2.global(3, "zwp_linux_dmabuf_v1", 3)
[1000779.108]  -> wl_regis...@2.bind(3, "zwp_linux_dmabuf_v1", 3, new id 
[unknown]@7)
[1000779.117]  -> wl_disp...@1.sync(new id wl_callback@8)
[1000779.121] wl_registry@2.global(4, "wl_compositor", 4)
[1000779.127]  -> wl_regis...@2.bind(4, "wl_compositor", 4, new id [unknown]@9)
[1000779.133] wl_registry@2.global(5, "wl_subcompositor", 1)
[1000779.138]  -> wl_regis...@2.bind(5, "wl_subcompositor", 1, new id 
[unknown]@10)
[1000779.144] wl_registry@2.global(6, "wl_data_device_manager", 3)
[1000779.149]  -> wl_regis...@2.bind(6, "wl_data_device_manager", 3, new id 
[unknown]@11)
[1000779.156] wl_registry@2.global(7, "zwlr_gamma_control_manager_v1", 1)
[1000779.162] wl_registry@2.global(8, "gtk_primary_selection_device_manager", 1)
[1000779.167]  -> wl_regis...@2.bind(8, "gtk_primary_selection_device_manager", 
1, new id [unknown]@12)
[1000779.174] wl_registry@2.global(9, "zxdg_output_manager_v1", 3)
[1000779.179]  -> wl_regis...@2.bind(9, "zxdg_output_manager_v1", 3, new id 
[unknown]@13)
[1000779.187] wl_registry@2.global(10, "org_kde_kwin_idle", 1)
[1000779.191]  -> wl_regis...@2.bind(10, "org_kde_kwin_idle", 1, new id 
[unknown]@14)
[1000779.200] wl_registry@2.global(11, "zwp_idle_inhibit_manager_v1", 1)
[1000779.205]  -> wl_regis...@2.bind(11, "zwp_idle_inhibit_manager_v1", 1, new 
id [unknown]@15)
[1000779.210] wl_registry@2.global(12, "zwlr_layer_shell_v1", 2)
[1000779.229] wl_registry@2.global(13, "xdg_wm_base", 2)
[1000779.233]  -> wl_regis...@2.bind(13, "xdg_wm_base", 2, new id [unknown]@16)
[1000779.238] wl_registry@2.global(14, "zwp_tablet_manager_v2", 1)
[1000779.242] wl_registry@2.global(15, 
"org_kde_kwin_server_decoration_manager", 1)
[1000779.246] wl_registry@2.global(16, "zxdg_decoration_manager_v1", 1)
[1000779.251]  -> wl_regis...@2.bind(16, "zxdg_decoration_manager_v1", 1, new 
id [unknown]@17)
[1000779.257] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
[1000779.261]  -> wl_regis...@2.bind(17, "zwp_relative_pointer_manager_v1", 1, 
new id [unknown]@18)
[1000779.266] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
[1000779.270]  -> wl_regis...@2.bind(18, "zwp_pointer_constraints_v1", 1, new 
id [unknown]@19)
[1000779.275] wl_registry@2.global(19, "wp_presentation", 1)
[1000779.281]  -> wl_regis...@2.bind(19, "wp_presentation", 1, new id 
[unknown]@20)
[1000779.288] wl_registry@2.global(20, "zwlr_output_manager_v1", 1)
[1000779.293] wl_registry@2.global(21, "zwlr_output_power_manager_v1", 1)
[1000779.297] wl_registry@2.global(22, "zwp_input_method_manager_v2", 1)
[1000779.302] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
[1000779.307] wl_registry@2.global(24, "zwlr_foreign_toplevel_manager_v1", 2)
[1000779.313] wl_registry@2.global(25, "zwlr_export_dmabuf_manager_v1", 1)
[1000779.317] wl_registry@2.global(26, "zwlr_screencopy_manager_v1", 3)
[1000779.321] wl_registry@2.global(27, "zwlr_data_control_manager_v1", 2)
[1000779.325] wl_registry@2.global(28, 
"zwp_primary_selection_device_manager_v1", 1)
[1000779.330]  -> wl_regis...@2.bind(28, 
"zwp_primary_selection_device_manager_v1", 1, new id [unknown]@21)
[1000779.336] wl_registry@2.global(29, "wp_viewporter", 1)
[1000779.341]  -> wl_regis...@2.bind(29, "wp_viewporter", 1, new id 
[unknown]@22)
[1000779.348] wl_registry@2.global(30, "zwp_virtual_keyboard_manager_v1", 1)
[1000779.352] wl_registry@2.global(31, "zwlr_virtual_pointer_manager_v1", 2)
[1000779.356] wl_registry@2.global(32, "zwlr_input_inhibit_manager_v1", 1)
[1000779.360] wl_registry@2