### System details

Ryzen 5600x with 32 gb of ram and nvidia 3060 12gb varient

### What's wrong?

Hi,

I’ve reproduced the issue again and performed the additional test requested in the discussion. I can now provide a more precise reproduction sequence and the resolved bar layout.

Steps to Reproduce

Start Omarchy normally with the default status bar position.

Open Discord.

Quit Discord using Quit from the Discord system tray icon menu.

Try interacting with the right-side status bar widgets.

Actual Behaviour

After quitting Discord, the following widgets become unresponsive to mouse interaction:

Dropbox

Tailscale

Agents

Audio/Speaker

The pointing-hand cursor no longer appears over the affected widgets. Display and Network/Ethernet have continued to behave normally in my observations.

The issue persists until the shell is restarted or the bar is moved to another position.

Additional Test: Right-click on Audio

While the issue was active, I right-clicked the Audio widget to test whether it could still receive pointer input independently of the bar's left-click handling.

Result: Right-click did not toggle mute/unmute.

This is an important observation because it suggests the problem may not be limited to the bar's left-click hit-testing. However, I understand that this result alone does not establish whether the cause is the input region, widget state, or another part of the interaction path.

Resolved Bar Layout

Running:

omarchy-shell shell listShellConfig | jq .bar.layout

returned the following right-side widget order:

omarchy.tray → omarchy.dropbox → omarchy.tailscale → omarchy.agents → omarchy.audio → omarchy.power → omarchy.monitor → omarchy.network

The direct query jq '.layout.right' ~/.config/omarchy/shell.json returned null, but the resolved shell configuration command successfully returned the layout.

This ordering may be relevant when comparing which widgets remain interactive and which become unresponsive.

Layer and Journal Diagnostics

The hyprctl layers output showed a single monitor (HDMI-A-2, 1920×1080) and the Omarchy bar at 1920×24. No additional top or overlay layer was visible in that snapshot.

The journal also contained these Quickshell warnings around Discord startup:

Error updating property StatusNotifierItem:IconName

QDBusError("org.freedesktop.DBus.Error.Failed", "error occurred in Get")

I cannot confirm that these warnings cause the interaction failure, but I am including them for completeness.

Additional Observation: Repositioning the Bar

Moving the bar to the left or right side of the screen clears the issue and restores normal interaction.

This suggests that rebuilding or recalculating the bar's layout may be relevant, although the exact mechanism remains unconfirmed.

Request for Further Investigation

Given the reproducible trigger, the failed Audio right-click test, the resolved widget order, and the fact that repositioning the bar clears the issue, could the investigation examine:

Whether pointer events reach the affected widgets after the tray item disappears.

Whether the bar's input region or widget geometry becomes stale.

Whether tray lifecycle changes affect widget registration or interaction state.

Whether repositioning the bar triggers a refresh that restores pointer interaction.

I appreciate the careful source-level investigation so far. I hope these additional observations help distinguish a shell-level hit-testing issue from a lower-level input delivery or widget-state problem and lead to a reliable fix.

Thank you for continuing to investigate this.