On Ubuntu 26.04, using Google Chrome in the terminal displays error messages

Budgie Desktop
1

On Ubuntu budgie 26.04, using Google Chrome in the terminal displays error messages, whereas Budgie 24.04 does not exhibit this issue.

sudo dpkg -i google-chrome-stable_current_amd64.deb

ubuntu@master:~$ [213792:213792:0630/201739.760482:ERROR:ui/ozone/platform/wayland/gpu/wayland_surface_factory.cc:249] '--ozone-platform=wayland' is not compatible with Vulkan. Consider switching to '--ozone-platform=x11' or disabling Vulkan
Created TensorFlow Lite XNNPACK delegate for CPU.
ubuntu@master:~$ [228247:228247:0630/201840.495697:ERROR:ui/ozone/platform/wayland/gpu/wayland_surface_factory.cc:249] '--ozone-platform=wayland' is not compatible with Vulkan. Consider switching to '--ozone-platform=x11' or disabling Vulkan
<sys>:0: Warning: g_bytes_compare: assertion 'bytes1 != NULL' failed
[213727:213768:0630/202141.960562:ERROR:google_apis/gcm/engine/registration_request.cc:275] Registration URL fetching failed.
[213727:213768:0630/202609.653305:ERROR:google_apis/gcm/engine/registration_request.cc:275] Registration URL fetching failed.
[213794:213813:0630/202755.935998:ERROR:net/socket/ssl_client_socket_impl.cc:944] handshake failed; returned -1, SSL error code 1, net_error -202
[213794:213813:0630/202756.324881:ERROR:net/socket/ssl_client_socket_impl.cc:944] handshake failed; returned -1, SSL error code 1, net_error -202
^C
ubuntu@master:~$ [213794:213813:0630/202934.221010:ERROR:net/socket/ssl_client_socket_impl.cc:944] handshake failed; returned -1, SSL error code 1, net_error -202
[213794:213813:0630/202934.478265:ERROR:net/socket/ssl_client_socket_impl.cc:944] handshake failed; returned -1, SSL error code 1, net_error -202
[213727:213768:0630/203104.833061:ERROR:google_apis/gcm/engine/registration_request.cc:275] Registration URL fetching failed.
[213794:213813:0630/203335.691103:ERROR:net/socket/ssl_client_socket_impl.cc:944] handshake failed; returned -1, SSL error code 1, net_error -202
[213794:213813:0630/203339.012547:ERROR:net/socket/ssl_client_socket_impl.cc:944] handshake failed; returned -1, SSL error code 1, net_error -202
[213727:213768:0630/203633.656539:ERROR:google_apis/gcm/engine/registration_request.cc:275] Registration URL fetching failed.

ubuntu@master:~$ echo 'export G_MESSAGES_DEBUG=none' >> ~/.bashrc
source ~/.bashrc
ubuntu@master:~$ [526676:526676:0630/204017.038731:ERROR:ui/ozone/platform/wayland/gpu/wayland_surface_factory.cc:249] '--ozone-platform=wayland' is not compatible with Vulkan. Consider switching to '--ozone-platform=x11' or disabling Vulkan
Created TensorFlow Lite XNNPACK delegate for CPU.
ubuntu@master:/usr/share/applications$ Created TensorFlow Lite XNNPACK delegate for CPU.
[557493:557493:0630/204229.785416:ERROR:ui/gl/gl_surface_presentation_helper.cc:260] GetVSyncParametersIfAvailable() failed for 1 times!
[557493:557493:0630/204229.789319:ERROR:ui/gl/gl_surface_presentation_helper.cc:260] GetVSyncParametersIfAvailable() failed for 2 times!
[557493:557493:0630/204231.169696:ERROR:ui/gl/gl_surface_presentation_helper.cc:260] GetVSyncParametersIfAvailable() failed for 3 times!
[557448:557448:0630/204320.471662:ERROR:ui/gfx/x/atom_cache.cc:234] Add application/vnd.portal.filetransfer to kAtomsToCache
[557448:557448:0630/204320.471748:ERROR:ui/gfx/x/atom_cache.cc:234] Add application/vnd.portal.files to kAtomsToCache
ubuntu@master:/usr/share/applications$ [623529:623529:0630/204656.498092:ERROR:ui/ozone/platform/wayland/gpu/wayland_surface_factory.cc:249] '--ozone-platform=wayland' is not compatible with Vulkan. Consider switching to '--ozone-platform=x11' or disabling Vulkan
Created TensorFlow Lite XNNPACK delegate for CPU.
2

The key part of your report is this

ubuntu@master:\~$ \[213792:213792:0630/201739.760482:ERROR:ui/ozone/platform/wayland/gpu/wayland_surface_factory.cc:249\] '--ozone-platform=wayland' is not compatible with Vulkan. Consider switching to '--ozone-platform=x11' or disabling Vulkan

This is most likely a bug with Chrome’s vulkan graphics rendering - whilst many apps use opengl, it appears Chrome has switched to using vulkan. It isn’t a vulkan issue per se - many apps use Vulkan successfully without issue. This is most likely an issue with how Chrome has implemented its linux vulkan rendering engine.