Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-411GitHub issuePublicDecided· Out of scope

NTFS drive fails to mount from Files after recent update, but mounts successfully with ntfs-3g 3

Reported by aydinverse · filed Sep 17, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

NTFS drive fails to mount from Files after recent update, but mounts successfully with ntfs-3g 3revision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Omarchy 4.0.4-1

What's wrong?

After the latest Omarchy update, my NTFS external drive can no longer be mounted through the Files application.

Error shown in Files:

"Unable to access '9353573010' Error mounting /dev/sdb1: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error"

System information:

Omarchy: latest update
Filesystem: NTFS
Device: /dev/sdb1
mount.ntfs present at: /usr/bin/mount.ntfs

Relevant checks:

lsblk -f shows:

sdb1 ntfs 5D155F6E187DCC22

The drive is healthy and accessible:

Works normally in Windows
Works normally in Linux Mint Live USB
Fails only in Omarchy after the latest update when mounted through Files

Manual mounting succeeds without any errors:

sudo mkdir -p /mnt/test sudo mount -t ntfs-3g /dev/sdb1 /mnt/test

After mounting manually, all files and folders are fully accessible.

This indicates that the NTFS filesystem and ntfs-3g are functioning correctly. The issue appears to be related to Files, udisks2, GVFS, or the automount mechanism introduced by the latest update rather than the drive itself.

Please let me know if additional logs or diagnostic information would be helpful.

View raw text
### System details

Omarchy 4.0.4-1

### What's wrong?

After the latest Omarchy update, my NTFS external drive can no longer be mounted through the Files application.

Error shown in Files:

"Unable to access '9353573010' Error mounting /dev/sdb1: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error"

System information:

Omarchy: latest update
Filesystem: NTFS
Device: /dev/sdb1
mount.ntfs present at: /usr/bin/mount.ntfs

Relevant checks:

lsblk -f shows:

sdb1 ntfs 5D155F6E187DCC22

The drive is healthy and accessible:

Works normally in Windows
Works normally in Linux Mint Live USB
Fails only in Omarchy after the latest update when mounted through Files

Manual mounting succeeds without any errors:

sudo mkdir -p /mnt/test sudo mount -t ntfs-3g /dev/sdb1 /mnt/test

After mounting manually, all files and folders are fully accessible.

This indicates that the NTFS filesystem and ntfs-3g are functioning correctly. The issue appears to be related to Files, udisks2, GVFS, or the automount mechanism introduced by the latest update rather than the drive itself.

Please let me know if additional logs or diagnostic information would be helpful.

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 14:55 UTC