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.
nautilus "Trash Settings" / "File History Settings" buttons error out of the box (no gnome-control-center)
Reported by vbtwo31984 · filed Sep 6, 2026Closed upstream on 2026-09-06 by its own reporter vbtwo31984, as a duplicate of #5531 (R-4334). GitHub close reason: duplicate.
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
System details
Intel Core i7-10750H, NVIDIA RTX 2070 Mobile (Optimus) + Intel UHD 630, Omarchy 4.0.2, nautilus 50.2.2-1
What's wrong?
The base package set installs nautilus but not gnome-control-center. Two built-in nautilus buttons hard-code a D-Bus call to org.gnome.Settings, which is therefore not activatable:
- Trash view → Trash Settings
- Recent view → File History Settings
Both fire the same call:
org.freedesktop.Application.ActivateAction("launch-panel", [<('privacy', [<'usage'>])>], {})
on org.gnome.SettingsWith no gnome-control-center present, clicking either shows this dialog:
There was an error launching the app. Details: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
<img width="1249" height="1028" alt="Image" src="https://github.com/user-attachments/assets/2503c103-94b9-4601-97f1-1effb8477b20" />
Steps to reproduce
- Fresh Omarchy 4.0.2.
- Open Files, navigate to Trash (or Recent).
- Click "Trash Settings" (or "File History Settings" in Recent). (or right-click "Trash/Recent" in sidebar and click "Settings")
- Error dialog appears; nothing opens.
Headless repro:
gdbus call --session --dest org.gnome.Settings --object-path /org/gnome/Settings \
--method org.freedesktop.Application.ActivateAction launch-panel \
"[<('privacy', [<'usage'>])>]" "{}"
# → Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatableExpected
The button opens something that can edit those settings, or it isn't shown. The panel only governs org.gnome.desktop.privacy keys: remember-recent-files, recent-files-max-age, remove-old-trash-files, old-files-age, remove-old-temp-files.
Possible directions (maintainers to weigh)
- Set a sensible
org.gnome.desktop.privacy remove-old-trash-files true(+old-files-age) default ininstall/user/first-run/, matching the existinggnome-theme.sh/gtk-primary-paste.shpattern, so trash self-manages; the button still errors but rarely gets used. - Ship a small stand-in that claims
org.gnome.Settingsand handles thelaunch-panelprivacy action. - Bundle
gnome-control-center(heavy; likely unwanted).
Full omarchy-debug available on request — it is the standard package list; the only relevant facts are gnome-control-center absent and nautilus 50.2.2-1 present.
View raw text
### System details
Intel Core i7-10750H, NVIDIA RTX 2070 Mobile (Optimus) + Intel UHD 630, Omarchy 4.0.2, nautilus 50.2.2-1
### What's wrong?
The base package set installs `nautilus` but not `gnome-control-center`. Two built-in nautilus buttons hard-code a D-Bus call to `org.gnome.Settings`, which is therefore not activatable:
- Trash view → **Trash Settings**
- Recent view → **File History Settings**
Both fire the same call:
```
org.freedesktop.Application.ActivateAction("launch-panel", [<('privacy', [<'usage'>])>], {})
on org.gnome.Settings
```
With no `gnome-control-center` present, clicking either shows this dialog:
> **There was an error launching the app.**
> Details:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
<img width="1249" height="1028" alt="Image" src="https://github.com/user-attachments/assets/2503c103-94b9-4601-97f1-1effb8477b20" />
### Steps to reproduce
1. Fresh Omarchy 4.0.2.
2. Open Files, navigate to Trash (or Recent).
3. Click "Trash Settings" (or "File History Settings" in Recent). (or right-click "Trash/Recent" in sidebar and click "Settings")
4. Error dialog appears; nothing opens.
Headless repro:
```
gdbus call --session --dest org.gnome.Settings --object-path /org/gnome/Settings \
--method org.freedesktop.Application.ActivateAction launch-panel \
"[<('privacy', [<'usage'>])>]" "{}"
# → Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
```
### Expected
The button opens something that can edit those settings, or it isn't shown. The panel only governs `org.gnome.desktop.privacy` keys: `remember-recent-files`, `recent-files-max-age`, `remove-old-trash-files`, `old-files-age`, `remove-old-temp-files`.
### Possible directions (maintainers to weigh)
- Set a sensible `org.gnome.desktop.privacy remove-old-trash-files true` (+ `old-files-age`) default in `install/user/first-run/`, matching the existing `gnome-theme.sh` / `gtk-primary-paste.sh` pattern, so trash self-manages; the button still errors but rarely gets used.
- Ship a small stand-in that claims `org.gnome.Settings` and handles the `launch-panel` privacy action.
- Bundle `gnome-control-center` (heavy; likely unwanted).
Full `omarchy-debug` available on request — it is the standard package list; the only relevant facts are `gnome-control-center` absent and `nautilus 50.2.2-1` present.
- 2503c103-94b9-4601-97f1-1effb8477b20
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.