Keep a rotated laptop or handheld panel rotated after a reboot
Read /usr/share/omarchy/bin/omarchy-hyprland-monitor-clamshell, omarchy-hyprland-monitor-watch, omarchy-hyprland-monitor-laptop, omarchy-hw-laptop, omarchy-hyprland-monitor-scaling and omarchy-refresh-config on 4.0.4-1, and issues #7066 and #7326 in full. The core inference holds and is honestly flagged LIKELY: sync_internal_scale re-applies the panel with an hl.monitor eval that has no transform when the active scale differs from the configured one, position comes from a connector-named single-line rule or auto, and the reported config is scale "1.2" with transform = 3 on the catch-all. Reading the watcher strengthens it: it runs the clamshell script at login and again 1, 4 and 11 seconds later, and not on configreloaded, which explains why the rotation holds after a save and fails after a reboot. The cause misstated the 2-second poll, which only runs on a machine omarchy-hw-laptop accepts. The danger was wrong: omarchy-refresh-config copies the user file to monitors.lua.bak.<epoch> before replacing it, so nothing is lost. Whether 1.2 is invalid for the reporter's panel is not known, because #7066 gives no resolution. The fix also missed that the Display panel's scale buttons drop the transform the same way. Nothing was reloaded or re-applied on this machine.
Do not try to reset this with omarchy refresh config hypr/monitors.lua. It replaces your file with the shipped template, which has no rotation and no per-panel rule. It saves your version first as ~/.config/hypr/monitors.lua.bak.<epoch seconds>, so if you ran it, copy that backup back over monitors.lua.
Symptom
I set transform = 3 in ~/.config/hypr/monitors.lua to rotate my built-in screen (reported on a GPD handheld, whose panels are natively portrait), and it works until I reboot. After a reboot the config still says transform = 3 but the screen is not rotated. Changing the transform value, saving, then changing it back fixes it until the next reboot. A related report on a Dell Latitude says the internal panel's manually set position snaps back to an automatic one within about a second.
Cause
LIKELY, inferred from reading omarchy-hyprland-monitor-clamshell and omarchy-hyprland-monitor-watch on 4.0.4-1 and not yet confirmed by the reporter. Omarchy autostarts omarchy-hyprland-monitor-watch, which runs the clamshell script when it starts at login, again 1, 4 and 11 seconds later, and the same way after every monitor added or removed event. On a machine it treats as a laptop (an ACPI lid switch, or a portable DMI chassis type) it also runs it every 2 seconds while an external monitor is active. It does not run it on a config reload. When the internal panel's active scale differs from the scale the script reads from monitors.lua, it re-applies the panel with hyprctl eval "hl.monitor({ output = \"$INTERNAL\", mode = \"preferred\", position = \"$position\", scale = $scale })". That rule carries no transform, so the panel falls back to unrotated, and its position comes from a single-line rule naming the panel's connector, or auto when there is none. A mismatch is expected when the configured scale does not divide the panel's resolution cleanly, which the Hyprland wiki calls an invalid scale, because the active scale then differs from the one written. The reported config used scale = "1.2" on the catch-all rule, and the report does not give the panel's resolution. Saving monitors.lua reloads the whole config, which re-applies the full rule with its transform, and because a reload does not trigger the watcher, the rotation then holds until the next login or hotplug. That explains why "change it and change it back" works until a reboot. To confirm, watch hyprctl monitors -j for the transform dropping to 0 within about 11 seconds of login.
Fix
**Give the internal panel its own one-line rule** with the transform, an explicit position, and a scale Hyprland applies exactly. The script matches only single-line rules naming the connector in a quoted string. First read the panel's name, current scale and transform:
hyprctl monitors all -j | jq -r '.[] | "\(.name) scale=\(.scale) transform=\(.transform)"'
-- ~/.config/hypr/monitors.lua
hl.monitor({ output = "DSI-1", mode = "preferred", position = "0x0", scale = 1.25, transform = 3 })
Use your panel's name (eDP-1, DSI-1) and a scale that divides its resolution cleanly, then run hyprctl reload. Check that hyprctl monitors -j reports exactly the scale you wrote. If it reports a different number, use that number in the rule, so the watcher sees no mismatch and leaves the panel alone.
Or keep the stock local omarchy_monitor_scale = "auto". The watcher does not re-apply a scale it cannot read as a number, but a transform on the catch-all rule still applies to every monitor, so a per-panel rule is cleaner.
The Display panel's scale buttons have the same gap: omarchy-hyprland-monitor-scaling re-applies the focused monitor with position = "auto" and no transform, so using them on the rotated panel unrotates it until the next hyprctl reload. Change the scale in monitors.lua instead.
Also check the record hyprland-invalid-scale-not-divisible for choosing a scale Hyprland accepts.
Verify
Reboot, wait ten seconds, then run hyprctl monitors -j | jq '.[] | {name, scale, transform, x, y}'. The panel still shows transform: 3 and the position you set, and both survive plugging in and removing an external monitor.
Sources
- https://github.com/omacom/omarchy/issues/7066
- https://github.com/omacom/omarchy/issues/7326
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-hyprland-monitor-clamshell
- https://github.com/hyprwm/hyprland-wiki/blob/main/content/configuring/core/monitors/positioning.md
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-hyprland-monitor-watch