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.
mako.service fails because mako is already running (Failed to acquire service name: File exists)
Reported by SmartALB · filed Apr 29, 2026Closed upstream on 2026-04-30 by its own reporter SmartALB. GitHub close reason: completed. Closed by its own reporter — not by itself 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
System details
- Omarchy version: 3.6.0 - Kernel: 6.19.13-arch1-1 - Session: Hyprland (UWSM-managed) - Hyprland: 0.54.3 (hyprland 0.54.3-2 package) - mako: 1.11.0-1 - uwsm: 0.26.4-1 - systemd: 260.1-2 - dbus-broker: 37-3 - dbus-broker-units: 37-3 - hypridle: 0.1.7-8
What's wrong?
The popup disappears quickly, but journald consistently shows that mako.service fails because another mako instance is already running.
Key logs
From journalctl --user -u mako.service -b 0 --no-pager:
- mako: Failed to acquire service name: File exists
- mako: Is a notification daemon already running?
- systemd[...]: Failed to start Lightweight Wayland notification daemon.
From systemctl --user status mako.service --no-pager:
- Active: failed (Result: exit-code)
- ExecStart=/usr/bin/mako (code=exited, status=1/FAILURE)
At the same time, another mako instance is already active:
- app-uwsm-mako-<id>.scope is running /usr/bin/mako
Reproduction
- Run
omarchy-update - Reboot or log out/log in
- Observe brief startup error notification
- Check:
systemctl --user --failed --no-pagersystemctl --user status mako.service --no-pagerjournalctl --user -u mako.service -b 0 --no-pager
What I found
It looks like mako is started twice:
1. Explicitly via Omarchy Hyprland autostart:
- ~/.local/share/omarchy/default/hypr/autostart.conf
- contains: exec-once = uwsm-app -- mako
2. Also via D-Bus/systemd activation:
- /usr/share/dbus-1/services/fr.emersion.mako.service
- contains: SystemdService=mako.service
So this appears to be duplicate startup / race behavior between explicit UWSM autostart and D-Bus/systemd activation.
Expected behavior
No startup error notification and no failed mako.service unit after login.
Actual behavior
Startup shows a brief error notification, and mako.service is failed, although notifications still generally work.
Notes
This started immediately after updating to Omarchy 3.6.0 (or latest updates around that timeframe), and was not present before.
View raw text
### System details - Omarchy version: 3.6.0 - Kernel: 6.19.13-arch1-1 - Session: Hyprland (UWSM-managed) - Hyprland: 0.54.3 (hyprland 0.54.3-2 package) - mako: 1.11.0-1 - uwsm: 0.26.4-1 - systemd: 260.1-2 - dbus-broker: 37-3 - dbus-broker-units: 37-3 - hypridle: 0.1.7-8 ### What's wrong? The popup disappears quickly, but journald consistently shows that `mako.service` fails because another mako instance is already running. ## Key logs From `journalctl --user -u mako.service -b 0 --no-pager`: - `mako: Failed to acquire service name: File exists` - `mako: Is a notification daemon already running?` - `systemd[...]: Failed to start Lightweight Wayland notification daemon.` From `systemctl --user status mako.service --no-pager`: - `Active: failed (Result: exit-code)` - `ExecStart=/usr/bin/mako (code=exited, status=1/FAILURE)` At the same time, another mako instance is already active: - `app-uwsm-mako-<id>.scope` is running `/usr/bin/mako` ## Reproduction 1. Run `omarchy-update` 2. Reboot or log out/log in 3. Observe brief startup error notification 4. Check: - `systemctl --user --failed --no-pager` - `systemctl --user status mako.service --no-pager` - `journalctl --user -u mako.service -b 0 --no-pager` ## What I found It looks like mako is started twice: 1. Explicitly via Omarchy Hyprland autostart: - `~/.local/share/omarchy/default/hypr/autostart.conf` - contains: `exec-once = uwsm-app -- mako` 2. Also via D-Bus/systemd activation: - `/usr/share/dbus-1/services/fr.emersion.mako.service` - contains: `SystemdService=mako.service` So this appears to be duplicate startup / race behavior between explicit UWSM autostart and D-Bus/systemd activation. ## Expected behavior No startup error notification and no failed `mako.service` unit after login. ## Actual behavior Startup shows a brief error notification, and `mako.service` is failed, although notifications still generally work. ## Notes This started immediately after updating to Omarchy 3.6.0 (or latest updates around that timeframe), and was not present before.
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.