BusDK Update

Virtual desktop: Bus Engine OS boots to a graphical login backed by Bus identities

Bus Engine OS now reaches a graphical login screen. The early virtual desktop path brings up a source-built Wayland/Wayfire GUI stack and presents a greeter wired to Bus identities, the platform identity service.

The current scope is an experimental, smoke-tested GUI boot. The important step is that the from-source, agent-operated OS now reaches a real graphical surface a person can see, with login work connected to the same identity boundary used elsewhere in BusDK.

June 30, 2026Bus Engine OSvirtual desktopBus identities

In short

TL;DR

Bus Engine OS now boots past a console into a visible Wayland/Wayfire login screen in the virtual desktop path.
The greeter is wired to Bus identities, so desktop login work follows the platform identity service boundary.
The current state is early and experimental: a smoke-tested graphical boot with desktop-product work still ahead.

The June 30 work ties together three pieces that had to meet at the same surface. bus-engine-os supplies the source-built operating system and GUI packages, including the Wayland and Wayfire stack. bus-portal-greeter supplies the login-facing greeter. bus-integration-desktop supplies the virtual desktop integration path around session startup and smoke checks.

The visible result is simple but important: the OS can boot under the virtual GUI path, move beyond a text console, and show a desktop login screen. That greeter is connected to Bus identities, so the graphical session starts from the same identity system the rest of the platform is being built around.

The maturity is intentionally modest. The current result shows a graphical boot path and greeter wiring under smoke-test conditions, with broader desktop-product work still ahead. For how to run the virtual desktop path, what the smoke result means, and which parts remain experimental, follow docs.busdk.com.