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.
Enable SSD TRIM
Reported by zsolt-donca · filed Oct 5, 2025Closed upstream on 2026-07-18 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
What do you need?
I did a fresh installation of Omachy v3.0.2 on a laptop with an nvme SSD, and SSD TRIM does not seem to be working out of the box. This can result in poor performance and reduced life of my SSD.
My enhancement request is to enable SSD trimming automatically within in the installer, or maybe following a prompt. I understand that Arch Linux does not enable it by default because it can have theoretical security implications (see wiki)), but I think that's pretty far fetched, and it's not just me: I believe that basically all Linux distros enable it out-of-the box for systems with full disk encryption, including Ubuntu.
See my investigation below, including how to enable it.
Following the Arch Wiki on SSD TRIM, I can confirm that by default my encrypted root partition is not supporting TRIM (by having zero in the column DISC-GRAN:
~ ❯ : lsblk --discard
NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO
zram0 0 4K 2T 0
nvme0n1 0 4K 2T 0
├─nvme0n1p1 0 4K 2T 0
└─nvme0n1p2 0 4K 2T 0
└─root 0 0B 0B 0And triggering a manual trimming also confirms this:
~ ❯ : sudo fstrim -av
/boot: 1.5 GiB (1632141312 bytes) trimmed on /dev/nvme0n1p1The fix is documented in the LUKS2 page:
# cryptsetup --allow-discards --persistent refresh rootIt is persistent, and even starts to work immediately (note the 4K value of root and that fstrim reported trimming the root partition):
~ ❯ : lsblk --discard
NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO
zram0 0 4K 2T 0
nvme0n1 0 4K 2T 0
├─nvme0n1p1 0 4K 2T 0
└─nvme0n1p2 0 4K 2T 0
└─root 0 4K 2T 0
~ ❯ : sudo fstrim -av
/boot: 1.5 GiB (1632141312 bytes) trimmed on /dev/nvme0n1p1
/: 908.9 GiB (975896055808 bytes) trimmed on /dev/mapper/rootI am not sure what's the best when it comes to how to actually execute the trimming, but I enabled Periodic TRIM):
# systemctl enable fstrim.timerAnother option would be to use asynchronous discarding through a mount option.
View raw text
### What do you need? I did a fresh installation of Omachy v3.0.2 on a laptop with an nvme SSD, and SSD TRIM does not seem to be working out of the box. This can result in **poor performance and reduced life of my SSD**. My enhancement request is to enable SSD trimming automatically within in the installer, or maybe following a prompt. I understand that Arch Linux does not enable it by default because it can have theoretical security implications (see [wiki](https://wiki.archlinux.org/title/Dm-crypt/Specialties#Discard/TRIM_support_for_solid_state_drives_(SSD))), but I think that's pretty far fetched, and it's not just me: I believe that basically all Linux distros enable it out-of-the box for systems with full disk encryption, including Ubuntu. See my investigation below, including how to enable it. Following the [Arch Wiki on SSD TRIM](https://wiki.archlinux.org/title/Solid_state_drive#TRIM), I can confirm that by default my encrypted root partition is not supporting TRIM (by having zero in the column `DISC-GRAN`: ``` ~ ❯ : lsblk --discard NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO zram0 0 4K 2T 0 nvme0n1 0 4K 2T 0 ├─nvme0n1p1 0 4K 2T 0 └─nvme0n1p2 0 4K 2T 0 └─root 0 0B 0B 0 ``` And triggering a manual trimming also confirms this: ``` ~ ❯ : sudo fstrim -av /boot: 1.5 GiB (1632141312 bytes) trimmed on /dev/nvme0n1p1 ``` The fix is documented in the [LUKS2](https://wiki.archlinux.org/title/Dm-crypt/Specialties#LUKS2) page: ``` # cryptsetup --allow-discards --persistent refresh root ``` It is persistent, and even starts to work immediately (note the `4K` value of `root` and that `fstrim` reported trimming the root partition): ``` ~ ❯ : lsblk --discard NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO zram0 0 4K 2T 0 nvme0n1 0 4K 2T 0 ├─nvme0n1p1 0 4K 2T 0 └─nvme0n1p2 0 4K 2T 0 └─root 0 4K 2T 0 ~ ❯ : sudo fstrim -av /boot: 1.5 GiB (1632141312 bytes) trimmed on /dev/nvme0n1p1 /: 908.9 GiB (975896055808 bytes) trimmed on /dev/mapper/root ``` I am not sure what's the best when it comes to how to actually execute the trimming, but I enabled [Periodic TRIM](https://wiki.archlinux.org/title/Solid_state_drive#Periodic_TRIM)): ``` # systemctl enable fstrim.timer ``` Another option would be to use asynchronous discarding through a mount option.
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.