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.
[Quattro] LocalSend tray item duplicates the built-in Share flow
Reported by 0xApotheosis · filed Aug 13, 2026Closed upstream on 2026-08-14 by the merge of PR #6852 (closed by dhh). GitHub close reason: completed.
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 Ultra 7 355, Intel Panther Lake graphics, Omarchy 4.0.0rc4-1, Hyprland 0.56.2, quickshell-git 0.3.0.r20.g28771c7-1, LocalSend 1.18.1-1.
What's wrong?
On Quattro, LocalSend starts hidden and appears in omarchy.tray, but the item adds no useful status and duplicates Omarchy's existing Trigger > Share > Receive surface. A primary click does nothing. A secondary click only exposes Open and Quit LocalSend, and hovering shows the implementation title org.localsend.localsend_app.
LocalSend is part of install/omarchy-base.packages, so this affects an app in the default installation.
Steps to reproduce
- Enable LocalSend autostart/start-hidden, or launch
localsend --hidden. - Expand the tray in the Quattro bar.
- Primary-click the LocalSend icon.
- Observe that no window or menu appears.
- Secondary-click the same icon and select
Open; the existing LocalSend window appears.
Expected behavior
LocalSend should remain available through Omarchy's built-in Share/Receive flow without adding this redundant generic tray item.
Root cause
LocalSend's Linux tray_manager backend registers an Ayatana/AppIndicator StatusNotifierItem with a DBusMenu, but it omits the optional ItemIsMenu property and provides no working Activate handler:
Title: s "org.localsend.localsend_app"
Menu: o "/org/ayatana/NotificationItem/.../Menu"
ItemIsMenu: No such property
Activate: org.freedesktop.DBus.Error.UnknownMethod: No handler for ActivateQuattro's Tray.qml opens the menu on primary click only when Quickshell's modelData.onlyMenu is true; otherwise it calls activate(). Quickshell defaults a missing ItemIsMenu property to false, so this call is a silent no-op.
This differs from Waybar, which deliberately defaults item_is_menu to true because libappindicator implements neither ItemIsMenu nor Activate. That compatibility default explains why the same tray item worked before the Quattro migration:
The same missing-property/no-activation shape is also observable from Dropbox's Ayatana item, although Omarchy normally suppresses that tray item when its dedicated Dropbox widget is present.
Quattro's normal Hide control is not a durable workaround here. The tray persists raw StatusNotifierItem IDs, while tray_manager generates LocalSend's AppIndicator ID with shortid.generate() on each launch:
Suggested direction
Treat LocalSend as already owned by an Omarchy surface and suppress its generic tray item, paralleling the existing Dropbox suppression when the dedicated Dropbox widget is present. LocalSend keeps running in the background, and Super+Ctrl+S > Receive or the application launcher can show its window.
The full omarchy-debug output was generated locally but is not attached because it contains host, network, UUID, path, and account information; the relevant package and compositor versions are included above.
View raw text
## System details Intel Core Ultra 7 355, Intel Panther Lake graphics, Omarchy 4.0.0rc4-1, Hyprland 0.56.2, quickshell-git 0.3.0.r20.g28771c7-1, LocalSend 1.18.1-1. ## What's wrong? On Quattro, LocalSend starts hidden and appears in `omarchy.tray`, but the item adds no useful status and duplicates Omarchy's existing `Trigger > Share > Receive` surface. A primary click does nothing. A secondary click only exposes `Open` and `Quit LocalSend`, and hovering shows the implementation title `org.localsend.localsend_app`. LocalSend is part of `install/omarchy-base.packages`, so this affects an app in the default installation. ### Steps to reproduce 1. Enable LocalSend autostart/start-hidden, or launch `localsend --hidden`. 2. Expand the tray in the Quattro bar. 3. Primary-click the LocalSend icon. 4. Observe that no window or menu appears. 5. Secondary-click the same icon and select `Open`; the existing LocalSend window appears. ### Expected behavior LocalSend should remain available through Omarchy's built-in Share/Receive flow without adding this redundant generic tray item. ### Root cause LocalSend's Linux `tray_manager` backend registers an Ayatana/AppIndicator StatusNotifierItem with a DBusMenu, but it omits the optional `ItemIsMenu` property and provides no working `Activate` handler: ```text Title: s "org.localsend.localsend_app" Menu: o "/org/ayatana/NotificationItem/.../Menu" ItemIsMenu: No such property Activate: org.freedesktop.DBus.Error.UnknownMethod: No handler for Activate ``` Quattro's `Tray.qml` opens the menu on primary click only when Quickshell's `modelData.onlyMenu` is true; otherwise it calls `activate()`. Quickshell defaults a missing `ItemIsMenu` property to false, so this call is a silent no-op. This differs from Waybar, which deliberately defaults `item_is_menu` to true because libappindicator implements neither `ItemIsMenu` nor `Activate`. That compatibility default explains why the same tray item worked before the Quattro migration: https://github.com/Alexays/Waybar/blob/6c3bd01bae35f2ba46cc3b25f95a028861112295/include/modules/sni/item.hpp#L65-L71 The same missing-property/no-activation shape is also observable from Dropbox's Ayatana item, although Omarchy normally suppresses that tray item when its dedicated Dropbox widget is present. Quattro's normal Hide control is not a durable workaround here. The tray persists raw StatusNotifierItem IDs, while `tray_manager` generates LocalSend's AppIndicator ID with `shortid.generate()` on each launch: https://github.com/leanflutter/tray_manager/blob/c51797434afba07fb715738178deb67ab9b09ade/packages/tray_manager/lib/src/tray_manager.dart#L99-L113 ### Suggested direction Treat LocalSend as already owned by an Omarchy surface and suppress its generic tray item, paralleling the existing Dropbox suppression when the dedicated Dropbox widget is present. LocalSend keeps running in the background, and `Super+Ctrl+S > Receive` or the application launcher can show its window. The full `omarchy-debug` output was generated locally but is not attached because it contains host, network, UUID, path, and account information; the relevant package and compositor versions are included above.
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.