Proof Portal

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-3874GitHub issuePublicReceived

external DP-1 present in hyprctl monitors, no wallpaper/bar showing on it

Reported by maxjo020418 · filed Dec 11, 2025Closed upstream on 2026-07-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source

Received and recorded verbatim. Nothing has been checked yet.

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

external DP-1 present in hyprctl monitors, no wallpaper/bar showing on itrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

AMD 5600u (Thinkpad E14 Gen3), Omarchy 3.2.2

What's wrong?

I am not sure what the problem might be here, whether it's from hyprland, wayland or something in omarchy (or all).

I use my laptop occasionally docked to (usb-c DP) my monitor using hyprdynamicmonitors which would set the monitors.conf according to the states I specify. Following is the monitors.conf for the docked state:

# laptop monitor
monitor=eDP-1,[email protected],1140x1080,1.33333333
# dock external monitoir
monitor=DP-1,[email protected],0x0,1.33333333

workspace = 1, monitor:eDP-1#, default:true
workspace = 2, monitor:DP-1
workspace = 3, monitor:DP-1
workspace = 4, monitor:DP-1
workspace = 5, monitor:DP-1

(would also set to only use eDP-1 when disconnected)

this config worked for weeks before it broke around 1~2 weeks ago (can't specify when or what update borked it cause I didn't use the dock for a while)

What happens is that desktop components (waybar, swaybg, swayosd) just does not run or breaks for the external monitor. so while the laptop monitor works fine, the external monitor remains black (but other tile windows work fine in there)

!Image

I tried these:
- check if I set some "output" config field only to eDP-1 (not set)
- rebooting individual services and also debug mode checks: (eg: WAYLAND_DEBUG=1 swaybg -c '#00ff00' -o DP-1)
I couldn't find anything meaningful, all services either silently fails or fallbacks to eDP-1 after failing to "see" DP-1
- ran hyprctl monitors (all DP-1 and eDP-1 comes out fine)
- ran hyprctl layers (DP-1 is empty)

    Monitor eDP-1:
    	Layer level 0 (background):
    		Layer 55f200ea7170: xywh: 1140 1080 1440 810, namespace: wallpaper, pid: 1704
    	Layer level 1 (bottom):
    	Layer level 2 (top):
    		Layer 55f200168900: xywh: 1140 1080 1440 26, namespace: waybar, pid: 1696
    	Layer level 3 (overlay):
    
    Monitor DP-1:
    	Layer level 0 (background):
    	Layer level 1 (bottom):
    	Layer level 2 (top):
    	Layer level 3 (overlay):

ran wayland-info | grep DP (only eDP-1 comes up?)

  name: 'eDP-1'
  description: 'Lenovo Group Limited 0x40A9  (eDP-1)'
  name: eDP-1
  description: Lenovo Group Limited 0x40A9  (eDP-1)

I could roughly figure out that somehow wayland is failing to expose DP-1 (via wl_output) and the components are failing to run there... I couldn't find any related problems like I experienced.

ps. If I boot the laptop with the dock connected, everything works fine (all the commands result in what I would expect too). If I ever disconnect and reconnect it from the dock or just boot while disconnected, I get the same problem. so I think wayland or hyprland is having problems connecting to a monitor?

View raw text

### System details

AMD 5600u (Thinkpad E14 Gen3), Omarchy 3.2.2

### What's wrong?

I am not sure what the problem might be here, whether it's from hyprland, wayland or something in omarchy (or all).

I use my laptop occasionally docked to (usb-c DP) my monitor using [hyprdynamicmonitors](https://github.com/fiffeek/hyprdynamicmonitors) which would set the `monitors.conf` according to the states I specify. Following is the `monitors.conf` for the docked state:

```conf
# laptop monitor
monitor=eDP-1,[email protected],1140x1080,1.33333333
# dock external monitoir
monitor=DP-1,[email protected],0x0,1.33333333

workspace = 1, monitor:eDP-1#, default:true
workspace = 2, monitor:DP-1
workspace = 3, monitor:DP-1
workspace = 4, monitor:DP-1
workspace = 5, monitor:DP-1
```
(would also set to only use eDP-1 when disconnected)

this config worked for weeks before it broke around 1~2 weeks ago (can't specify when or what update borked it cause I didn't use the dock for a while)

What happens is that desktop components (waybar, swaybg, swayosd) just does not run or breaks for the external monitor. so while the laptop monitor works fine, the external monitor remains black (but other tile windows work fine in there)

![Image](https://github.com/user-attachments/assets/788d946d-348e-4c15-8963-466f5fb6f982)

I tried these:
- check if I set some `"output"` config field only to eDP-1 (not set)
- rebooting individual services and also debug mode checks: (eg: `WAYLAND_DEBUG=1 swaybg -c '#00ff00' -o DP-1`)
I couldn't find anything meaningful, all services either silently fails or fallbacks to eDP-1 after failing to "see" DP-1
- ran `hyprctl monitors` (all DP-1 and eDP-1 comes out fine)
- ran `hyprctl layers` (DP-1 is empty)
    ```
    Monitor eDP-1:
    	Layer level 0 (background):
    		Layer 55f200ea7170: xywh: 1140 1080 1440 810, namespace: wallpaper, pid: 1704
    	Layer level 1 (bottom):
    	Layer level 2 (top):
    		Layer 55f200168900: xywh: 1140 1080 1440 26, namespace: waybar, pid: 1696
    	Layer level 3 (overlay):
    
    Monitor DP-1:
    	Layer level 0 (background):
    	Layer level 1 (bottom):
    	Layer level 2 (top):
    	Layer level 3 (overlay):
    ```
- ran `wayland-info | grep DP` (only eDP-1 comes up?)
  ```
  name: 'eDP-1'
  description: 'Lenovo Group Limited 0x40A9  (eDP-1)'
  name: eDP-1
  description: Lenovo Group Limited 0x40A9  (eDP-1)
  ```

I could roughly figure out that somehow wayland is failing to expose DP-1 (via `wl_output`) and the components are failing to run there... I couldn't find any related problems like I experienced.

**ps.** If I boot the laptop with the dock connected, everything works fine (all the commands result in what I would expect too). If I ever disconnect and reconnect it from the dock or just boot while disconnected, I get the same problem. so I think wayland or hyprland is having problems connecting to a monitor?

Image

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.

Proof

History & reports

Reference