NoBrain Linux 0.1.4

NoBrain Linux 0.1.4

NoBrain Linux 0.1.4 is the Build 161 fresh-install reliability release. It
keeps the Build 144 Void rootfs package baseline and the 0.1.3 desktop and
clipboard behavior.

What changed

• Fresh extraction now repairs rootfs symlink targets that accidentally gained
  a trailing 0001, including the ARM64 loader and boot-critical libraries.
• Existing matching rootfs installations receive the same repair before reuse.
• Missing Python, compiler, and GCC compatibility links are recreated and
  verified before Linux startup continues.
• Startup creates the missing libX11.so development linker name before
  compiling the dialog helper. This prevents the linker from selecting the
  static libX11.a and failing on unresolved xcb_* symbols.
• Guest diagnostics use the mounted /sdcard path, so logs remain accessible
  on a fresh Android install without relying on public Downloads permission.
• The local APK alignment helper streams large APK data instead of copying the
  complete archive into RAM.

Root cause

The 0.1.3 rootfs archive contained 938 symlink targets with an accidental
trailing 0001. Build 161 repairs all 934 resolvable archive links plus three
required compatibility links; four optional targets are absent from the
snapshot. After that repair, fresh startup exposed a separate linker issue:
the runtime libX11.so.6 existed but the unversioned libX11.so name did not.
The dialog-helper build consequently selected libX11.a and stopped startup
immediately after MIME/GDK preparation.

Device validation

Build 161 was installed directly after uninstalling NoBrain and clearing its
data on a Nubia 8150N. Rootfs extraction exited successfully, repaired 937
corrupt and compatibility links, installed the missing xterm packages, and
reached Desktop ready. DWM remained alive, xterm opened, xbindkeys and the
command FIFO started, and the application menu cache contained 966 entries. All
public Python and shell regression checks passed.

The OEM Unisoc large-application watchdog independently killed one extraction
attempt at roughly 203 MiB RSS while several unrelated applications were using
hundreds of MiB each. Android recorded a SIGKILL rather than an application
exception; relaunching completed normally.

Candidate identity

The tested release-signed 0.1.4 candidate has the following identity:

Runtime build: 161
Size: 594568475 bytes
SHA-256: a371693b41fb394d8fc628da2570ab50d8c6be5eb23d317eb61f54ed7713f154
Signing certificate SHA-256:
1966b79fe9c29c1ae6949f5669301f4862c9d3dead838c00b188e97e8f2355bc