Bug#1003689: chromium: Chromium doesn't start
Am Donnerstag, dem 27.01.2022 um 18:55 -0500 schrieb Andres Salomon: > you can also run "chromium --ozone-platform=wayland" to get native > wayland. Thanks for the tip, I never tried that. I do the chrome://flags way because it's persistent and doesn't require running chromium from the command-line. And "Preferred Ozone platform = Auto" is fail-safe in case the system does not support Wayland. Best, Amr
Bug#1003689: chromium: Chromium doesn't start
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.
Bug#1003689: chromium: Chromium doesn't start
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
Bug#1003689: chromium: Chromium doesn't start
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= 0x [Google Inc. (Google)], DEVICE=0x [ANGLE (Google, Vulkan 1.2.0 (SwiftShader Device (Subzero) (0xC0DE)), SwiftShader driver-5.0.0)] *ACTIVE*
Bug#1003689: chromium: Chromium doesn't start
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.
Bug#1003689: chromium: Chromium doesn't start
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.
Bug#1003689: chromium: Chromium doesn't start
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 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.brodow...@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
Bug#1003689: chromium: Chromium doesn't start
On 1/17/22 03:00, Andres Salomon wrote: 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. :) Here's some hints about what to report upstream, btw: https://www.reddit.com/r/swaywm/comments/imcoo6/chrome_wayland_available_via_feature_flag_in/g493mes/?utm_source=reddit_medium=web2x=3
Bug#1003689: chromium: Chromium doesn't start
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. :)
Bug#1003689: chromium: Chromium doesn't start
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.
Bug#1003689: chromium: Chromium doesn't start
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.
Bug#1003689: chromium: Chromium doesn't start
On Thu, 13 Jan 2022 19:24:30 +0100 Martin Dosch wrote: > 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_ and usage=SCANOUT > [708429:708429:0113/192059.334276:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)] > Failed to create pixmap 1024x512, RGBA_, usage SCANOUT > [708429:708429:0113/192059.334443:ERROR:gbm_pixmap_wayland.cc(76)] Cannot > create bo with format= RGBA_ and usage=GPU_READ > [708429:708429:0113/192059.334549:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)] > Failed to create pixmap 1024x512, RGBA_, 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_ and usage=SCANOUT > [708429:708429:0113/192059.493801:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)] > Failed to create pixmap 1024x512, RGBA_, usage SCANOUT > [708429:708429:0113/192059.493972:ERROR:gbm_pixmap_wayland.cc(76)] Cannot > create bo with format= RGBA_ and usage=GPU_READ > [708429:708429:0113/192059.494115:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(261)] > Failed to create pixmap 1024x512, RGBA_, 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)] 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
