Repository navigation
2x error with CLI on Wayland (process of logging in is OK) #25
Description
There is this printed:
pangolin login
First copy your one-time code: SOME-CODE
Press Enter to open https://pangolin.somedomain.com/auth/login/device in your browser...
[45:45:0207/152913.948800:ERROR:ui/ozone/platform/wayland/gpu/wayland_surface_factory.cc:251]
'--ozone-platform=wayland' is not compatible with Vulkan.
Consider switching to '--ozone-platform=x11' or disabling Vulkan
[2:24:0207/152914.596560:ERROR:net/cert/ev_root_ca_metadata.cc:162] Failed to decode OID: 0
Device authorized
Logged in as pang@ol.in
Machine is:
cat /etc/os-release
PRETTY_NAME="Zorin OS 18"
NAME="Zorin OS"
VERSION_ID="18"
VERSION="18"
VERSION_CODENAME=noble
ID=zorin
ID_LIKE="ubuntu debian"
Linux 6.14.0-37-generic
Windowing System: Wayland
Originally posted by @KusAdama in fosrl/pangolin#2431
Activity
github-actions commentedon Feb 25, 2026
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
huda-code commentedon Jun 25, 2026
Hi! I'd like to work on this issue if it's still available. I'll investigate the Wayland-specific errors during the login flow and propose a fix if they're actionable.
oschwartz10612 commentedon Jun 25, 2026
huda-code commentedon Jun 25, 2026
Thanks! I'm investigating this now.
From looking through the login flow, the browser is opened via
pkg/browser, which forwards the launched command's stdout/stderr to the CLI.Before I open a PR, I'd like to confirm whether the reported Wayland/Vulkan messages are emitted by the browser launcher (
xdg-open) itself or by the Chromium process after launch.If anyone can still reproduce this on a Chromium-based browser, could you confirm whether the messages disappear when launching the same URL directly with
xdg-open <url>from a terminal? That will help determine the correct fix.