Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
linux-git (6.18.0-1-git) crashes on Framework Desktop (Strix Halo) before GUI
Reported by kvz · filed Dec 8, 2025Closed upstream on 2025-12-11 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
Follow-up to #3815 (DSC inactive on Framework + LG 6K). While testing a newer DC stack, the git kernel crashes before the GUI.
What happened
- Booted Limine entry
//linux-git(6.18.0-1-git-12189-g67a454e6b1c6) on Framework Desktop (AMD Strix Halo iGPU). - Reached Omarchy unlock, but Hypr never came up; session hung.
- Kernel log shows a BUG in
lib/string_helpers.cvery early.
Key log (journalctl -b -1 -k)
strnlen: detected buffer overflow: 17 byte read of buffer size 16
WARNING: lib/string_helpers.c:1035 at 0x0, CPU#5: kworker/5:0/51
Modules linked in: … amdgpu …
kernel BUG at lib/string_helpers.c:1043!
Oops: invalid opcode: 0000 [#1] SMP NOPTI
Tainted: G W 6.18.0-1-git-12189-g67a454e6b1c6 …System
- Framework Desktop (AMD Ryzen AI Max 300 Series / Strix Halo iGPU)
- Display: LG UltraFine 6K via DP (works at 6K@30 and 4K@60 on stable kernel)
- Bootloader: Limine; UKI generated by
linux-gitpkg - Stable kernel boots fine: 6.17.9-arch1-1
Why it matters
Trying git was to pick up newer AMD DC/DSC fixes. Instead, git kernel panics, so we can’t validate DSC enablement. Tracking this so others don’t get stuck and so we know when it’s safe to retest.
If you want more logs or to file this upstream (drm/amd or lkml) I can post the full journalctl -b -1 -k and hardware details.
View raw text
Follow-up to #3815 (DSC inactive on Framework + LG 6K). While testing a newer DC stack, the git kernel crashes before the GUI. ### What happened - Booted Limine entry `//linux-git` (6.18.0-1-git-12189-g67a454e6b1c6) on Framework Desktop (AMD Strix Halo iGPU). - Reached Omarchy unlock, but Hypr never came up; session hung. - Kernel log shows a BUG in `lib/string_helpers.c` very early. ### Key log (journalctl -b -1 -k) ``` strnlen: detected buffer overflow: 17 byte read of buffer size 16 WARNING: lib/string_helpers.c:1035 at 0x0, CPU#5: kworker/5:0/51 Modules linked in: … amdgpu … kernel BUG at lib/string_helpers.c:1043! Oops: invalid opcode: 0000 [#1] SMP NOPTI Tainted: G W 6.18.0-1-git-12189-g67a454e6b1c6 … ``` ### System - Framework Desktop (AMD Ryzen AI Max 300 Series / Strix Halo iGPU) - Display: LG UltraFine 6K via DP (works at 6K@30 and 4K@60 on stable kernel) - Bootloader: Limine; UKI generated by `linux-git` pkg - Stable kernel boots fine: 6.17.9-arch1-1 ### Why it matters Trying git was to pick up newer AMD DC/DSC fixes. Instead, git kernel panics, so we can’t validate DSC enablement. Tracking this so others don’t get stuck and so we know when it’s safe to retest. If you want more logs or to file this upstream (drm/amd or lkml) I can post the full `journalctl -b -1 -k` and hardware details.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.