How run cast_shell binary

45 views
Skip to first unread message

Jacek Skiba

unread,
Dec 29, 2025, 10:45:10 AM12/29/25
to Chromium-dev
Hello, 


However this returns error:
ERROR:chromecast/cast_core/runtime/browser/runtime_service_impl.cc:63] Runtime id must be specified in command line with: --cast-core-runtime-id

With those switches cast_shell is started:
out/cast/cast_shell \
    --cast-core-runtime-id=1 \
    --runtime-service-path="localhost:9000" \
    --cast-mojo-broker-path=unix:/tmp/cast_mojo_broker \
    --ozone-platform=x11 \

However in this state cast_shell is by default is idle state. I see browser, gou and zygote processes, but renderer process is not created, so we have only a black screen.

How can I inject URL into cast?
From my understanding Cast runtime service is responsible for app launch. I need to send some gRPC request for it?

mark a. foltz

unread,
Jan 5, 2026, 7:30:13 PM (8 days ago) Jan 5
to jaceks...@gmail.com, Chromium-dev
Make sure your GN args are set up for building this target.


This target is only supported on LInux.  Try passing --ozone-platform=wayland (you might be on Wayland).

This is just building a single-window renderer that will navigate to the URL on the commandline.  Building an equivalent to a Chromecast product isn't possible from code in Chromium.

m.


--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/9bd96a29-98f0-49a5-91b1-afc9deb4f7e3n%40chromium.org.

Jacek Skiba

unread,
Jan 12, 2026, 5:11:39 PM (22 hours ago) Jan 12
to mark a. foltz, Chromium-dev
Wayland platform is not supported by cast_shell target:

out/cast/cast_shell \
    --cast-core-runtime-id=9 \
    --runtime-service-path="localhost:9000" \
    --cast-mojo-broker-path=unix:/tmp/cast_mojo_broker \
   --ozone-platform=wayland \

[523471:523471:0112/224950.956734:FATAL:ui/ozone/platform_selection.cc:46] Invalid ozone platform: wayland
#0 0x58530dd1ce72 base::debug::CollectStackTrace()
#1 0x58530dd05531 base::debug::StackTrace::StackTrace()
#2 0x58530dc02b63 logging::LogMessage::Flush()

Those are supported by cast_shell platforms:
gen/ui/ozone/platform_list.cc : const char* kPlatformNames[] = {
                                           "headless",  // kPlatformHeadless
                                           "cast",  // kPlatformCast
                                           "x11",  // kPlatformX11

For x11 and headless renderer process is not created (browser is in suspend state), where for cast I'm getting a crash from Viz:
[524579:524589:0112/230245.567337:FATAL:components/viz/service/display_embedder/output_surface_provider_impl.cc:167] Check failed: surface_ozone.

@Mark A. Foltz: should I create a chromium issue for it?
Reply all
Reply to author
Forward
0 new messages