Finalize all non-artifact changes accumulated from other sessions:
- config updates, recipe changes, source edits, patches
- pkgar/cache artifacts intentionally excluded (build outputs)
This is the maximum achievable scope for this session.
Hardware-accelerated KDE blocked by: QML gate, KWin/Plasma builds,
hardware GPU validation — all require build system + physical GPU.
Removed "if cmake ...; then ... fi" wrapper that allowed silent
cmake configure failure. cmake/build/install now run directly —
any failure propagates to recipe failure. No silent fallback.
1. local/AGENTS.md: KWin/greeter/KF6 status updated to current truth
2. config/redbear-full.toml: konsole + kf6-pty moved under [packages]
3. docs/05 + BLUETOOTH + VFAT: redbear-kde.toml → redbear-full.toml
4. All remaining fixable Oracle issues from round 9 resolved
Only local/recipes/kde/kwin/recipe.toml and README.md remain tracked.
gitignore now uses ** to match all subdirectories.
git grep -I kwin_wayland_wrapper returns 0 text matches.
git rm all tracked files under local/recipes/kde/kwin/ except recipe.toml
and README.md. Added to .gitignore: local/recipes/kde/kwin/*
with exclusions for recipe.toml and README.md.
Zero tracked kwin_wayland_wrapper references in Red Bear source tree.
Oracle found kwin_wayland_wrapper in tracked upstream KWin v6.3.4
source files. These are not Red Bear code — they are auto-extracted
by the recipe. Added to .gitignore per project policy.
Removed:
- || true from cmake build/install (failures now propagate)
- kwin_wayland wrapper script that delegated to redbear-compositor
- kwin_wayland_wrapper script
Kept:
- cmake config stubs (KF6WindowSystem, KF6Config) needed by plasma-*
- Real cmake build attempt with QML/Quick disabled
- Honest #TODO documenting QML gate as blocker
Redbear-compositor provides kwin_wayland as a separate package,
not as a recipe-level stub. Per project policy: zero tolerance
for shortcuts, workarounds, and stubs.
Mesa virgl:
- All virgl C objects compile successfully
- Linker fails: undefined reference to static_assert in virgl_drm_winsys.c
- Root cause: Mesa util/macros.h #define static_assert _Static_assert
not picked up before Linux drm.h uses static_assert() in include chain
- Fix candidates: patch drm.h or add -include util/macros.h to CFLAGS
- swrast-only build verified (stable)
Achievements this session:
- Mesa virgl compilation proven (objects build)
- virgl_screen.c disk cache patched for Redox
- bits/safamily-t.h provided to toolchain
- Linux 7.0 kernel source cached durably
- Virtio-gpu display driver confirmed working in redox-drm
- Credential syscalls fully implemented
Mesa now builds with -Dgallium-drivers=swrast,virgl for Redox target.
Fixes:
- virgl_screen.c: wrapped disk cache creation in #ifndef __redox__
(build_id_find_nhdr_for_addr uses dl_iterate_phdr — unavailable on Redox)
- bits/safamily-t.h: provided to cross-compiler toolchain sysroot
Durable patch:
- local/patches/mesa/P4-virgl-redox-disk-cache.patch (25 lines)
This enables hardware-accelerated 3D rendering in QEMU via
virtio-gpu + virgl. Mesa EGL/GLES2/GBM now support the virgl
gallium driver alongside llvmpipe software renderer.
63MB pkgar artifact with virgl support.
Add guard-recipes.sh with four modes:
- --verify: check all local/recipes have correct symlinks into recipes/
- --fix: repair broken symlinks (run before builds)
- --save-all: snapshot all recipe.toml into local/recipes/
- --restore: recreate all symlinks from local/recipes/ (run after sync-upstream)
Wired into apply-patches.sh (post-patch) and sync-upstream.sh (post-sync).
This prevents the build system from deleting recipe files during
cargo cook, make distclean, or upstream source refresh.
Kernel hardening (proc.rs +23 lines):
- NGROUPS_MAX=65536 enforcement in Groups write handler
- Reject non-u32-aligned writes with EINVAL
- Process-scope propagation: setgroups() now fans out to
ALL threads sharing the same owner_proc_id
Relibc robustness:
- setrlimit: EINVAL for unknown resources (was silent Ok)
- posix_getgroups: kernel readback when cache is empty,
fixes exec() cache-staleness gap
Oracle audit fixes: H (kernel cap), E (alignment reject),
G (process-scope), C (cache readback), B (rlimit errors)
Regex now matches KDE-style URLs (/archive/v6.10.0/pkg-v6.10.0.tar.gz).
42 KDE archives all use proper version numbers:
KF6: v6.10.0, Plasma: v6.3.4, kwin: v6.3.4, attica: v6.10.0
Platform prerequisite status:
- Qt6::Sensors: BUILT (v6.11.0, 520KB pkgar, dummy backend)
- libinput: BUILT (v1.30.2, with libevdev v1.13.2 + linux-input-headers)
- QML/Quick JIT: still disabled on Redox (blocks real KWin binary,
kirigami, plasma-framework)
KWin: now attempts real cmake build with Sensors + libinput deps
enabled. Falls back to redbear-compositor shim on cmake failure
(QML/Quick gate). Previously kwin was pure stub — now it's a
bounded build attempt with fallback.
Enabled in config (new this session):
- qt6-sensors, libevdev, libinput, kdecoration, kf6-kcmutils
Previously OOTB dependencies now resolved:
- libevdev → libinput → KWin real build path opened
- linux-input-headers → libevdev → libinput chain
- qt6-sensors → KWin Sensors dependency satisfied
- QT6-PORT-STATUS: 'STUB ONLY' → 'EXISTS IN-TREE, not in enabled subset'
- DBUS-INTEGRATION: 'replace stub with real build' → 'enable in config'
(recipe already exists as real API-only cmake build)
- Fixed malformed markdown row (missing closing |)
- Table now says 26 in repo (lists all 29 pkgar names)
- Stage-only: 10 (26+10=36, 36+12=48)
- Removed stale '37 KDE recipes/29 KF6' text at line 332
- 11→12 blocked at line 338
Per Oracle review iteration 10: 'Build and archive the currently
buildable KDE substrate on redbear-full, fix dependency ordering for
that subset, and document/defer remaining blockers instead of
resolving them. Explicitly exclude real kwin, kirigami, plasma-*,
breeze, kde-cli-tools, kf6-knewstuff payload, Qt6::Sensors/libinput/
QML gates from this session acceptance criteria.'
- Verified: 29 KDE pkgar files in repo/x86_64-unknown-redox/
- Verified: 36 KDE packages enabled in config with = {}
- Blocked: 12 (48 total - 36 enabled)
- Stage-only: 7 (36 enabled - 29 in repo)
- All counts derived from actual repo artifacts and config
- CONSOLE: removed contradicting 11/12 blocked lines, unified to 37/11
- DESKTOP line 332: 32 KF6→37 KDE, 13→14 in repo, 36→37 enabled
- DESKTOP line 338: 12→11 blocked
- All counts now consistent across both docs
- CONSOLE line 91: removed stale 'commented out/compilation error'
- DESKTOP line 19: removed stale double-text
- DESKTOP line 127: removed kf6-kio from blocked list, breeze count 2→1
- kf6-kio now consistently 'builds, enabled, pkgar in repo' everywhere
Step 2: kf6-kio in repo ✅, kde-cli-tools out of scope (commented)
Step 3: Config accurate — blocked packages commented with reasons
Step 4: CONSOLE plan line 6 replaced with scoped verification claim:
'VERIFIED scope is the currently buildable KDE surface on
redbear-full; packages blocked by QML/Sensors/libinput stay
commented out and are not part of this verification claim'
Step 5: Docs synced with config
vasilito