Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1003689: chromium: Chromium doesn't start

12,457 views
Skip to first unread message

Martin Dosch

unread,
Jan 13, 2022, 1:30:03 PM1/13/22
to
Package: chromium
Version: 97.0.4692.71-0.1
Severity: normal
X-Debbugs-Cc: mar...@mdosch.de

Dear Maintainer,

chromium is no more starting on my system. If I try to start it in a terminal I
get the following output:

[708429:708429:0113/192057.675801:ERROR:gpu_init.cc(457)] Passthrough is not
supported, GL is egl, ANGLE is
[708429:708429:0113/192057.684752:ERROR:sandbox_linux.cc(378)]
InitializeSandbox() called with multiple threads in process gpu-process.
[708382:708382:0113/192057.717409:ERROR:cursor_loader.cc(114)] Failed to load a
platform cursor of type kNull
[708429:708429:0113/192059.334041:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=SCANOUT
[708429:708429:0113/192059.334276:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 1024x512, RGBA_8888, usage SCANOUT
[708429:708429:0113/192059.334443:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=GPU_READ
[708429:708429:0113/192059.334549:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 1024x512, RGBA_8888, usage GPU_READ
[708429:708429:0113/192059.334653:ERROR:shared_image_backing_factory_gl_image.cc(351)]
CreateSharedImage: Failed to create bindable image
[708429:708429:0113/192059.334742:ERROR:shared_image_factory.cc(586)]
CreateSharedImage: could not create backing.
[708429:708429:0113/192059.334976:ERROR:skia_output_surface_impl_on_gpu.cc(1714)]
Failed to make current.
[708429:708429:0113/192059.343452:ERROR:raster_decoder.cc(1238)]
RasterDecoderImpl: Context lost during MakeCurrent.
[708429:708429:0113/192059.343715:ERROR:shared_image_stub.cc(534)]
SharedImageStub: context already lost
[708429:708429:0113/192059.357480:ERROR:shared_image_stub.cc(534)]
SharedImageStub: context already lost
[708429:708429:0113/192059.387529:ERROR:skia_output_surface_impl_on_gpu.cc(1714)]
Failed to make current.
[708429:708429:0113/192059.403432:ERROR:skia_output_surface_impl_on_gpu.cc(1714)]
Failed to make current.
[708429:708429:0113/192059.493480:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=SCANOUT
[708429:708429:0113/192059.493801:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 1024x512, RGBA_8888, usage SCANOUT
[708429:708429:0113/192059.493972:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=GPU_READ
[708429:708429:0113/192059.494115:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 1024x512, RGBA_8888, usage GPU_READ
[708429:708429:0113/192059.494288:ERROR:shared_image_backing_factory_gl_image.cc(351)]
CreateSharedImage: Failed to create bindable image
[708429:708429:0113/192059.494469:ERROR:shared_image_factory.cc(586)]
CreateSharedImage: could not create backing.
[708382:708382:0113/192059.571489:ERROR:gpu_process_host.cc(968)] GPU process
exited unexpectedly: exit_code=5
[708569:708569:0113/192059.735783:ERROR:gpu_init.cc(457)] Passthrough is not
supported, GL is egl, ANGLE is
[708511:1:0113/192059.741308:ERROR:command_buffer_proxy_impl.cc(125)]
ContextResult::kTransientFailure: Failed to send
GpuControl.CreateCommandBuffer.
[708569:708569:0113/192059.746960:ERROR:sandbox_linux.cc(378)]
InitializeSandbox() called with multiple threads in process gpu-process.
[708569:708569:0113/192059.887936:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=SCANOUT
[708569:708569:0113/192059.888187:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 1024x512, RGBA_8888, usage SCANOUT
[708569:708569:0113/192059.888369:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=GPU_READ
[708569:708569:0113/192059.888503:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 1024x512, RGBA_8888, usage GPU_READ
[708569:708569:0113/192059.888834:ERROR:shared_image_backing_factory_gl_image.cc(351)]
CreateSharedImage: Failed to create bindable image
[708569:708569:0113/192059.889004:ERROR:shared_image_factory.cc(586)]
CreateSharedImage: could not create backing.
[708569:708569:0113/192059.889363:ERROR:skia_output_surface_impl_on_gpu.cc(1714)]
Failed to make current.
[708569:708569:0113/192059.890097:ERROR:skia_output_surface_impl_on_gpu.cc(1714)]
Failed to make current.
[708569:708569:0113/192059.890531:ERROR:shared_image_stub.cc(534)]
SharedImageStub: context already lost
[708382:708382:0113/192059.892314:ERROR:command_buffer_proxy_impl.cc(328)] GPU
state invalid after WaitForGetOffsetInRange.
[708569:708569:0113/192059.971429:ERROR:shared_image_stub.cc(534)]
SharedImageStub: context already lost
[708511:1:0113/192059.971878:ERROR:command_buffer_proxy_impl.cc(328)] GPU state
invalid after WaitForGetOffsetInRange.
[708569:708569:0113/192059.978302:ERROR:shared_image_stub.cc(534)]
SharedImageStub: context already lost
[708569:708569:0113/192059.978628:ERROR:skia_output_surface_impl_on_gpu.cc(1714)]
Failed to make current.
[708511:1:0113/192059.979238:ERROR:command_buffer_proxy_impl.cc(125)]
ContextResult::kTransientFailure: Failed to send
GpuControl.CreateCommandBuffer.
[708569:708569:0113/192100.036262:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=SCANOUT
[708569:708569:0113/192100.036487:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 2304x1280, RGBA_8888, usage SCANOUT
[708569:708569:0113/192100.036973:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=GPU_READ
[708569:708569:0113/192100.037277:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 2304x1280, RGBA_8888, usage GPU_READ
[708569:708569:0113/192100.037389:ERROR:shared_image_backing_factory_gl_image.cc(351)]
CreateSharedImage: Failed to create bindable image
[708569:708569:0113/192100.037518:ERROR:shared_image_factory.cc(586)]
CreateSharedImage: could not create backing.
[708511:1:0113/192100.087391:ERROR:command_buffer_proxy_impl.cc(328)] GPU state
invalid after WaitForGetOffsetInRange.
[708382:708382:0113/192100.088900:ERROR:gpu_process_host.cc(968)] GPU process
exited unexpectedly: exit_code=5
[708612:708612:0113/192100.246813:ERROR:gpu_init.cc(457)] Passthrough is not
supported, GL is egl, ANGLE is
[708612:708612:0113/192100.254863:ERROR:sandbox_linux.cc(378)]
InitializeSandbox() called with multiple threads in process gpu-process.
[708612:708612:0113/192100.370524:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=SCANOUT
[708612:708612:0113/192100.400143:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 1024x512, RGBA_8888, usage SCANOUT
[708612:708612:0113/192100.400329:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=GPU_READ
[708612:708612:0113/192100.400935:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 1024x512, RGBA_8888, usage GPU_READ
[708612:708612:0113/192100.401125:ERROR:shared_image_backing_factory_gl_image.cc(351)]
CreateSharedImage: Failed to create bindable image
[708612:708612:0113/192100.401331:ERROR:shared_image_factory.cc(586)]
CreateSharedImage: could not create backing.
[708612:708612:0113/192100.401608:ERROR:shared_image_stub.cc(534)]
SharedImageStub: context already lost
[708612:708612:0113/192100.414752:ERROR:shared_image_stub.cc(534)]
SharedImageStub: context already lost
[708612:708612:0113/192100.415069:ERROR:skia_output_surface_impl_on_gpu.cc(1714)]
Failed to make current.
[708612:708612:0113/192100.415477:ERROR:raster_decoder.cc(1238)]
RasterDecoderImpl: Context lost during MakeCurrent.
[708612:708612:0113/192100.415752:ERROR:shared_image_stub.cc(534)]
SharedImageStub: context already lost
[708612:708612:0113/192100.434566:ERROR:skia_output_surface_impl_on_gpu.cc(1714)]
Failed to make current.
[708612:708612:0113/192100.449410:ERROR:skia_output_surface_impl_on_gpu.cc(1714)]
Failed to make current.
[708612:708612:0113/192100.472164:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=SCANOUT
[708612:708612:0113/192100.472380:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 1024x512, RGBA_8888, usage SCANOUT
[708612:708612:0113/192100.472722:ERROR:gbm_pixmap_wayland.cc(76)] Cannot
create bo with format= RGBA_8888 and usage=GPU_READ
[708612:708612:0113/192100.472877:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)]
Failed to create pixmap 1024x512, RGBA_8888, usage GPU_READ
[708612:708612:0113/192100.473092:ERROR:shared_image_backing_factory_gl_image.cc(351)]
CreateSharedImage: Failed to create bindable image
[708612:708612:0113/192100.473269:ERROR:shared_image_factory.cc(586)]
CreateSharedImage: could not create backing.
[708382:708382:0113/192100.518288:ERROR:gpu_process_host.cc(968)] GPU process
exited unexpectedly: exit_code=5
[708656:708656:0113/192100.647634:ERROR:gpu_init.cc(457)] Passthrough is not
supported, GL is disabled, ANGLE is
[708656:708656:0113/192100.648414:ERROR:sandbox_linux.cc(378)]
InitializeSandbox() called with multiple threads in process gpu-process.
[708382:708410:0113/192101.455433:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)]
START: ReportBluetoothAvailability(). If you don't see the END: message, this
is crbug.com/1216328.
[708382:708410:0113/192101.455515:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)]
END: ReportBluetoothAvailability()


-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (900, 'testing'), (600, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.0-rc7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8), LANGUAGE not set
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 97.0.4692.71-0.1
ii libasound2 1.2.6.1-1
ii libatk-bridge2.0-0 2.38.0-2
ii libatk1.0-0 2.36.0-3
ii libatomic1 11.2.0-14
ii libatspi2.0-0 2.42.0-2
ii libc6 2.33-2
ii libcairo2 1.16.0-5
ii libcups2 2.3.3op2-7
ii libdbus-1-3 1.12.20-3
ii libdrm2 2.4.109-2
ii libevent-2.1-7 2.1.12-stable-1
ii libexpat1 2.4.2-1
ii libflac8 1.3.3-2
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.11.1+dfsg-1
ii libgbm1 21.3.4-1
ii libgcc-s1 11.2.0-14
ii libglib2.0-0 2.70.2-1
ii libharfbuzz0b 2.7.4-1
ii libicu67 67.1-7
ii libjpeg62-turbo 1:2.1.2-1
ii libjsoncpp25 1.9.5-2
ii liblcms2-2 2.12~rc1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.32-3
ii libnss3 2:3.73.1-1
ii libopenjp2-7 2.4.0-3
ii libopus0 1.3.1-0.1
ii libpango-1.0-0 1.48.10+ds1-1
ii libpng16-16 1.6.37-3
ii libpulse0 15.0+dfsg1-3
ii libre2-9 20211101+dfsg-1
ii libsnappy1v5 1.1.8-1
ii libstdc++6 11.2.0-14
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-2+b1
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.4-1
ii libxfixes3 1:5.0.3-2
ii libxkbcommon0 1.3.1-1
ii libxml2 2.9.12+dfsg-5+b1
ii libxrandr2 2:1.5.2-1
ii libxslt1.1 1.1.34-4
ii zlib1g 1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii chromium-sandbox 97.0.4692.71-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.33-2
ii libstdc++6 11.2.0-14
ii libx11-6 2:1.7.2-2+b1
ii libxext6 2:1.3.4-1
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-4.1
ii zlib1g 1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii chromium-sandbox 97.0.4692.71-0.1
ii dunst [notification-daemon] 1.5.0-1+b1
ii fonts-liberation 1:1.07.4-11
ii gnome-shell [notification-daemon] 41.2-1
ii libgl1-mesa-dri 21.3.4-1
ii libu2f-udev 1.1.10-3
ii mako-notifier [notification-daemon] 1.6-2
ii notification-daemon 3.20.0-4+b1
ii system-config-printer 1.5.14-1
ii upower 0.99.13-1

Versions of packages chromium-sandbox depends on:
ii libc6 2.33-2

-- debconf-show failed

Andres Salomon

unread,
Jan 13, 2022, 3:20:03 PM1/13/22
to

Can you please try starting chromium with the argument "--use-gl=desktop" and see if that  fixes it?

Also, I'm guessing you're running this under Wayland. If --use-gl=desktop doesn't help, can you try deleting lines 61 through 63 in /usr/bin/chromium? These are the lines to delete:

if [ -n "$WAYLAND_DISPLAY" ]; then
  CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ozone-platform=wayland"
fi


Andres Salomon

unread,
Jan 14, 2022, 4:00:04 AM1/14/22
to
On 1/14/22 03:10, Martin Dosch wrote:
> Dear Andres,
[...]
>> Also, I'm guessing you're running this under Wayland. If
>> --use-gl=desktop doesn't help, can you try deleting lines 61 through
>> 63 in /usr/bin/chromium? These are the lines to delete:
>
> That's it! Thank you, this fixed it. Chromium starts again.

Interesting. Can you please provide the terminal output when running it
successfully?

Also, please try running it with "--ozone-platform-hint=auto" (also
including the terminal output)? I expect it will crash, but if it
doesn't then maybe we should be using that instead.

Adrien Ponchelet

unread,
Jan 15, 2022, 9:10:03 AM1/15/22
to
Dear Andres,

I have the same problem as Martin.

The "--use-gl=desktop" option doesn't work for me to. Open is ok, but
window is figed. I cannot do anything.
When I commenting the line 61 to 63 (/usr/bin/chromium) which refer to
Wayland, it works fine.
The "--ozone-platform-hint=auto" option (without lines commented)
doesn't work, same as launching the "chromium" command.

Below, my console log :

$> uname -a
Linux portable 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08)
x86_64 GNU/Linux

$> chromium --version
Chromium 97.0.4692.71 built on Debian 11.2, running on Debian 11.2

$> chromium --use-gl=desktop
[9055:9055:0115/143258.305656:ERROR:gl_factory.cc(146)] Requested GL
implementation is not available.
[9055:9055:0115/143258.310224:ERROR:viz_main_impl.cc(161)] Exiting GPU
process due to errors during initialization
[9007:9036:0115/143258.827916:ERROR:nss_util.cc(286)] After loading Root
Certs, loaded==false: NSS error code: -8018
[9119:9119:0115/143259.057540:ERROR:gl_factory.cc(146)] Requested GL
implementation is not available.
[9119:9119:0115/143259.061447:ERROR:viz_main_impl.cc(161)] Exiting GPU
process due to errors during initialization
[9183:9183:0115/143259.416071:ERROR:gl_factory.cc(146)] Requested GL
implementation is not available.
[9183:9183:0115/143259.433760:ERROR:viz_main_impl.cc(161)] Exiting GPU
process due to errors during initialization
[9196:9196:0115/143259.992476:ERROR:gpu_init.cc(457)] Passthrough is not
supported, GL is disabled, ANGLE is
[9196:9196:0115/143259.993159:ERROR:sandbox_linux.cc(378)]
InitializeSandbox() called with multiple threads in process gpu-process.
[9196:9212:0115/143300.028018:ERROR:wayland_buffer_manager_gpu.cc(124)]
WaylandBufferManagerGpu is not initialized. Can't register a surface.
[9007:9052:0115/143301.229936:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)]
START: ReportBluetoothAvailability(). If you don't see the END: message,
this is crbug.com/1216328.
[9007:9052:0115/143301.230020:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)]
END: ReportBluetoothAvailability()
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated

$> chromium (with lines commented in /usr/bin/chromium)
[9308:9369:0115/143528.235577:ERROR:nss_util.cc(286)] After loading Root
Certs, loaded==false: NSS error code: -8018
libva error: vaGetDriverNameByIndex() failed with unknown libva error,
driver_name = (null)
[9352:9352:0115/143528.823080:ERROR:sandbox_linux.cc(378)]
InitializeSandbox() called with multiple threads in process gpu-process.
[9308:9370:0115/143530.646896:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)]
START: ReportBluetoothAvailability(). If you don't see the END: message,
this is crbug.com/1216328.
[9308:9370:0115/143530.646943:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)]
END: ReportBluetoothAvailability()
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[0115/143550.781276:ERROR:scoped_ptrace_attach.cc(27)] ptrace: No such
process (3)
*** stack smashing detected ***: terminated
Fontconfig error: Cannot load default config file
*** stack smashing detected ***: terminated

$> chromium --ozone-platform-hint=auto
[9807:9807:0115/143805.240618:ERROR:gpu_init.cc(457)] Passthrough is not
supported, GL is egl, ANGLE is
[9807:9807:0115/143805.247921:ERROR:sandbox_linux.cc(378)]
InitializeSandbox() called with multiple threads in process gpu-process.
[9759:9790:0115/143805.688139:ERROR:nss_util.cc(286)] After loading Root
Certs, loaded==false: NSS error code: -8018
[9759:9788:0115/143807.847431:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)]
START: ReportBluetoothAvailability(). If you don't see the END: message,
this is crbug.com/1216328.
[9759:9788:0115/143807.847472:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)]
END: ReportBluetoothAvailability()
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[9892:1:0115/143814.653495:ERROR:command_buffer_proxy_impl.cc(125)]
ContextResult::kTransientFailure: Failed to send
GpuControl.CreateCommandBuffer.
[9904:1:0115/143814.653495:ERROR:command_buffer_proxy_impl.cc(125)]
ContextResult::kTransientFailure: Failed to send
GpuControl.CreateCommandBuffer.
[9759:9759:0115/143815.797128:ERROR:gpu_process_host.cc(968)] GPU
process exited unexpectedly: exit_code=11
[9947:9947:0115/143816.024628:ERROR:gpu_init.cc(457)] Passthrough is not
supported, GL is egl, ANGLE is
[9947:9947:0115/143816.031839:ERROR:sandbox_linux.cc(378)]
InitializeSandbox() called with multiple threads in process gpu-process.
[9892:1:0115/143823.657122:ERROR:command_buffer_proxy_impl.cc(328)] GPU
state invalid after WaitForGetOffsetInRange.
[9904:1:0115/143823.657142:ERROR:command_buffer_proxy_impl.cc(328)] GPU
state invalid after WaitForGetOffsetInRange.
[9759:9759:0115/143824.788024:ERROR:gpu_process_host.cc(968)] GPU
process exited unexpectedly: exit_code=11
[9966:9966:0115/143824.988087:ERROR:gpu_init.cc(457)] Passthrough is not
supported, GL is egl, ANGLE is
[9966:9966:0115/143824.994020:ERROR:sandbox_linux.cc(378)]
InitializeSandbox() called with multiple threads in process gpu-process.
[9892:1:0115/143833.748096:ERROR:command_buffer_proxy_impl.cc(328)] GPU
state invalid after WaitForGetOffsetInRange.
[9904:1:0115/143833.748082:ERROR:command_buffer_proxy_impl.cc(328)] GPU
state invalid after WaitForGetOffsetInRange.
[9759:9759:0115/143834.774422:ERROR:gpu_process_host.cc(968)] GPU
process exited unexpectedly: exit_code=11
[9986:9986:0115/143835.225443:ERROR:gpu_init.cc(457)] Passthrough is not
supported, GL is disabled, ANGLE is
[9986:9986:0115/143835.225960:ERROR:sandbox_linux.cc(378)]
InitializeSandbox() called with multiple threads in process gpu-process.
*** stack smashing detected ***: terminated
[0115/143906.928570:ERROR:scoped_ptrace_attach.cc(37)] process not stopped
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated

Best regards,
--
Adrien

Andres Salomon

unread,
Jan 17, 2022, 3:10:04 AM1/17/22
to
On Sat, 15 Jan 2022 14:58:20 +0100 Adrien Ponchelet wrote:
> Dear Andres,
>
> I have the same problem as Martin.
>
> The "--use-gl=desktop" option doesn't work for me to. Open is ok, but
> window is figed. I cannot do anything.
> When I commenting the line 61 to 63 (/usr/bin/chromium) which refer to
> Wayland, it works fine.
> The "--ozone-platform-hint=auto" option (without lines commented)
> doesn't work, same as launching the "chromium" command.

>


Thanks for your report as well. Since this is affecting wayland users on both bullseye and sid, I'm going to revert the wayland stuff in the next upload; it doesn't appear ready for prime time.

Once it's reverted, wayland users will still be able to manually pass --ozone-platform=wayland to chromium to get native wayland support.

I would encourage both of you to also grab a stock chromium binary from upstream (via snap or whatever mechanism you prefer), and file bug reports upstream if --ozone-platform=wayland still fails to run on your system with the official binaries. Assuming you're interested in native wayland support, that is. :)


Andres Salomon

unread,
Jan 17, 2022, 3:20:04 AM1/17/22
to

Kim-Alexander Brodowski

unread,
Jan 18, 2022, 4:00:04 AM1/18/22
to

Dear Maintainer,

we're also experiencing issues with the latest chromium update. We run chromium in kiosk mode without a full desktop environment. After updating to 97.0.4692.71-0.1~deb11u1, chromium fails to start. We were able to resolve this initial problem by installing libgtk-3-0 manually , which appears to be missing from the dependencies. However, this does not fix the problem entirely. chromium opens after that, but the tab remains blank and triggers chromium's unresponsive tab dialog.

Downgrading to 90.0.4430.212-1 (stable) or replacing chromium with Google's proprietary Chrome package fixes both problems for us reliably.

On Mon, 17 Jan 2022 11:20:42 +0100 Martin Dosch <mar...@mdosch.de> wrote:

> Hi,

>
> On 17.01.2022 03:00, Andres Salomon wrote:
> >I would encourage both of you to also grab a stock chromium binary from
> >upstream (via snap or whatever mechanism you prefer), and file bug
> >reports upstream if --ozone-platform=wayland still fails to run on your
> >system with the official binaries. Assuming you're interested in native
> >wayland support, that is. :)
>
> It seems to work with the latest upstream build. So maybe this is
> already fixed upstream.
>
> > ./chrome --version
> > Chromium 99.0.4836.0
>
> Best regards,
> Martin
-- 
Mit freundlichen Grüßen
Kim-Alexander Brodowski

IServ GmbH
Entwicklung
Bültenweg 73
38106 Braunschweig

Telefon:   +49 531 22 43 666-0
Fax:       +49 531 22 43 666-9
E-Mail:    Kim.Br...@iserv.eu
Internet:  https://iserv.eu

USt-IdNr. DE265149425 | Amtsgericht Braunschweig | HRB 201822
Geschäftsführer: Benjamin Heindl, Martin Hüppe, Jörg Ludwig
Grundsätze zum Datenschutz: https://iserv.eu/privacy

Andres Salomon

unread,
Jan 20, 2022, 8:00:04 PM1/20/22
to
On 1/17/22 05:20, Martin Dosch wrote:
> Hi,
>
> On 17.01.2022 03:00, Andres Salomon wrote:
>> I would encourage both of you to also grab a stock chromium binary
>> from upstream (via snap or whatever mechanism you prefer), and file
>> bug reports upstream if --ozone-platform=wayland still fails to run
>> on your system with the official binaries. Assuming you're interested
>> in native wayland support, that is. :)
>
> It seems to work with the latest upstream build. So maybe this is
> already fixed upstream.
>
>> ./chrome --version
>> Chromium 99.0.4836.0

Thanks for trying that out.

I uploaded 99.0.4818.0-0.1 to experimental. It would be really helpful
if you could also test with that version, so I can figure out if the
wayland graphics problem is introduced by debian's various patches &
build config, or if it's something that's actually an upstream bug that
got fixed in v99.

Andres Salomon

unread,
Jan 21, 2022, 3:30:03 AM1/21/22
to
On 1/21/22 03:04, Martin Dosch wrote:
> Hi,
>
> On 20.01.2022 19:51, Andres Salomon wrote:
>> I uploaded 99.0.4818.0-0.1 to experimental. It would be really
>> helpful if you could also test with that version, so I can figure out
>> if the wayland graphics problem is introduced by debian's various
>> patches & build config, or if it's something that's actually an
>> upstream bug that got fixed in v99.
>
> I installed chromium from experimental and it still doesn't start
> until I remove the wayland specific if clause in the start script.

Thank you for checking. It sounds like we (debian) broke something. Can
you please go to chrome://gpu in the experimental debian chromium (v99)
, click "copy report to clipboard", and paste that into a text file? 
And then run the stock chrome version with --ozone-platform=wayland, and
again go to chrome://gpu and save that output to another text file. And
then send those text files (feel free to zip them up if they're large)
to this bug report?  That way I can see if there's any 3d drivers or
anything else that we're not building that you need.

Andres Salomon

unread,
Jan 21, 2022, 3:40:05 PM1/21/22
to
On 1/21/22 03:21, Martin Dosch wrote:
> Hi,
>
> there you go.
>
> Best regards,
> Martin


Thanks!

Wow, okay, this is not what I expected. The upstream version has
hardware acceleration disabled for your graphics hardware. Yet it's only
disabled if running in wayland native mode; it's enabled for X11 mode.
On the (intel-based gpu) install that I'm testing here, chromium in
wayland-native mode has hardware acceleration enabled.

I'm not sure why wayland native mode wouldn't be able to access hardware
acceleration; maybe wayland combined with mesa for some reason doesn't
support the hardware acceleration? But either way, it makes sense that
Debian's version crashes - we don't (yet) build swiftshader, which is
what the upstream version is using for software rendering. So either
mesa and wayland need to play nice together on newer amd hardware before
we can re-enable native wayland support, or we need to start building
swiftshader (and users will likely complain about slow graphics/heavy
cpu usage).


--- /tmp/debian-chromium.txt    2022-01-21 13:41:00.045761594 -0500
+++ /tmp/upstream-chromium.txt  2022-01-21 13:41:07.334007210 -0500
@@ -1,74 +1,35 @@

 Graphics Feature Status
-Canvas: Hardware accelerated
+Canvas: Software only, hardware acceleration unavailable


-GPU0   VENDOR= 0x1002, DEVICE=0x15d8 *ACTIVE*
-GPU1   VENDOR= 0x1002, DEVICE=0x67ef
+GPU0   VENDOR= 0xffff [Google Inc. (Google)], DEVICE=0xffff [ANGLE
(Google, Vulkan 1.2.0 (SwiftShader Device (Subzero) (0x0000C0DE)),
SwiftShader driver-5.0.0)] *ACTIVE*

Andres Salomon

unread,
Jan 27, 2022, 7:10:05 PM1/27/22
to
On 1/27/22 18:50, Amr Ibrahim wrote:
> Hello,
>
> I just want to give a small guide into how to enable Wayland again for
> people like me who prefer Wayland and it works well for them:
>
> 1. Start chromium
> 2. Type chrome://flags in the address bar
> 3. Search for ozone
> 4. Change "Preferred Ozone platform" into "Auto"
> 5. Restart chromium
>
> Best,
> Amr


Thanks. Yes, you can also run "chromium --ozone-platform=wayland" to get
native wayland. Cc'ing to the wayland bug report so others see this as well.
0 new messages