ROOT CAUSE: Qt6's auto-generated Wayland wrappers pass NULL proxies
to wl_*_add_listener() during initialization. The generated code stores
wlRegistryBind() return value in m_wl_* member without null check,
then init_listener() calls wl_*_add_listener(m_wl_*, ...) which
page-faults at null+8 (write to proxy->object.implementation).
FIX (kded6): wrapper script renames libqwayland.so to .disabled
before launching kded6.real. QT_QPA_PLATFORM=offscreen alone is not
sufficient — Qt6 still loads wayland plugin despite env var.
FIX (libwayland): null guards in redox.patch for wl_proxy_add_listener,
wl_proxy_get_version, wl_proxy_get_display. Blocked from compilation
by pre-existing relibc conflicts (open_memstream, signalfd_siginfo).
FIX (Qt6 wrappers): regex-based null guard insertion proven in concept.
Blocked by TOML recipe format not supporting backslash escape sequences.
Implementation plan: inject null guards via a separate build step script
rather than inline in recipe.toml.
Qt plugins (libqwayland.so, libqredox.so) fail to dlopen() because
libwayland-client.so was missing at runtime. libwayland = "ignore"
prevents the package from being installed.
Fixed by adding post-build copy step in qtbase recipe: libwayland-*.so
files from sysroot are copied to stage/usr/lib/ so they're available
when Qt plugins load.
Also restored libwayland recipe.toml (was accidentally truncated to 22
lines without blake3 hash).
- WAYLAND-IMPLEMENTATION-PLAN.md v2.0: document architecture decision
that Wayland is the only supported display path. Remove all
framebuffer fallback workarounds (offscreen QPA, redox QPA shim).
- qwaylanddisplay.cpp: add fprintf instrumentation for crash diagnosis;
skip xkb_context_new on Redox to eliminate potential xkb crash vector.
- greeter-ui/main.cpp: remove QT_QPA_PLATFORM=redox workaround.
The greeter must use Wayland. Accept the crash until Qt6 is fixed.
- Ruled out: relibc calloc (zeroes correctly), libwayland proxy_create
(correct), compositor protocol (compliant). Root cause is in Qt6
generated Wayland wrappers passing NULL to wl_proxy_add_listener.
redox-toolchain.cmake CMAKE_CXX_FLAGS now includes:
-I${COOKBOOK_SYSROOT}/usr/include/QtQml
-I${COOKBOOK_SYSROOT}/usr/include/QtQuick
Previous attempts (CMAKE_CXX_FLAGS override, env CXXFLAGS) failed
because toolchain uses CACHE STRING "" FORCE which overrides all.
Result: QML/Quick headers resolved (no more "fatal: QQmlEngine not found")
New blocker: KDE ECM QML macros (QML_NAMED_ELEMENT, QML_ATTACHED,
QML_UNCREATABLE expanded with _OFF_OFF_OFF suffix). This is upstream
KDE build infrastructure, not a Red Bear include issue.
QML gate status: include layer resolved, KDE ECM macro layer next.
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
Consolidate the active desktop path around redbear-full while landing the greeter/session stack and the runtime fixes needed to keep Wayland and KWin bring-up moving forward.
vasilito