From ac1da6065b565a9208669d59fbe5b7183c03b7e3 Mon Sep 17 00:00:00 2001 From: Vasilito Date: Wed, 29 Apr 2026 14:31:53 +0100 Subject: [PATCH] =?UTF-8?q?docs:=20D-Bus,=20boot,=20wayland=20plans=20?= =?UTF-8?q?=E2=86=92=20v3.0=20parent=20references?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - DBUS-INTEGRATION-PLAN.md: parent plan v2.0→v3.0, redbear-kde→redbear-full - BOOT-PROCESS-IMPROVEMENT-PLAN.md: v2.0→v3.0, redbear-kde→redbear-full - WAYLAND-IMPLEMENTATION-PLAN.md: redbear-wayland/kde marked historical All active doc parent plan references now point to CONSOLE-TO-KDE-DESKTOP-PLAN.md v3.0. --- local/docs/BOOT-PROCESS-IMPROVEMENT-PLAN.md | 4 ++-- local/docs/DBUS-INTEGRATION-PLAN.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/local/docs/BOOT-PROCESS-IMPROVEMENT-PLAN.md b/local/docs/BOOT-PROCESS-IMPROVEMENT-PLAN.md index f8261984..b4702302 100644 --- a/local/docs/BOOT-PROCESS-IMPROVEMENT-PLAN.md +++ b/local/docs/BOOT-PROCESS-IMPROVEMENT-PLAN.md @@ -2,7 +2,7 @@ **Version:** 1.0 — 2026-04-27 **Status:** Active — supersedes ad-hoc boot fixes and replaces historical P0–P6 boot notes -**Canonical plans:** `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` (v2.0), `local/docs/GREETER-LOGIN-IMPLEMENTATION-PLAN.md` +**Canonical plans:** `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` (v3.0), `local/docs/GREETER-LOGIN-IMPLEMENTATION-PLAN.md` **Diagnosis:** `local/docs/BOOT-PROCESS-ASSESSMENT.md` (Phase 7 kernel RAM hang + ISO organization) --- @@ -156,7 +156,7 @@ - [ ] `kwin_wayland_wrapper --drm` starts as the user session compositor - [ ] `plasmashell` starts (or at minimum, a KWin desktop surface appears) -**Critical gap:** `redbear-kde-session` — the script that `redbear-session-launch` invokes for the KDE session — was not found in the source tree. This script or binary must be created/staged at `/usr/bin/redbear-kde-session`. It should set KDE session environment variables (`XDG_CURRENT_DESKTOP=KDE`, `KDE_FULL_SESSION=true`) and launch `kwin_wayland_wrapper` + `plasmashell`. The upstream KWin Wayland service entry (`plasma-kwin_wayland.service.in`) provides a reference template. +**Critical gap:** `redbear-full-session` — the script that `redbear-session-launch` invokes for the KDE session — was not found in the source tree. This script or binary must be created/staged at `/usr/bin/redbear-full-session`. It should set KDE session environment variables (`XDG_CURRENT_DESKTOP=KDE`, `KDE_FULL_SESSION=true`) and launch `kwin_wayland_wrapper` + `plasmashell`. The upstream KWin Wayland service entry (`plasma-kwin_wayland.service.in`) provides a reference template. **Estimated effort:** 4–7 days (session handoff + KDE session bring-up + missing script creation) diff --git a/local/docs/DBUS-INTEGRATION-PLAN.md b/local/docs/DBUS-INTEGRATION-PLAN.md index 75203ed9..240ae16f 100644 --- a/local/docs/DBUS-INTEGRATION-PLAN.md +++ b/local/docs/DBUS-INTEGRATION-PLAN.md @@ -3,7 +3,7 @@ **Version:** 1.0 — 2026-04-17 **Status:** Active plan **Scope:** Full D-Bus infrastructure for KDE Plasma 6 on Wayland, tightly integrated with Redox scheme IPC -**Parent plan:** `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` (v2.0) +**Parent plan:** `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` (v3.0) --- @@ -13,7 +13,7 @@ D-Bus is **mandatory infrastructure** for KDE Plasma 6 — not optional, not def services, KWin, plasmashell, and virtually every KF6 framework communicate over D-Bus at runtime. Red Bear OS already has D-Bus 1.16.2 building with a 24-line redox.patch, the system bus wired -in `redbear-full` and `redbear-kde` profiles, and QtDBus enabled in qtbase. This is a solid +in `redbear-full` profile (historical `redbear-kde` name retired), and QtDBus enabled in qtbase. This is a solid foundation, but it is only the transport layer. What's missing is the **service layer** — the D-Bus services that KDE actually expects to talk to.