0.56 regression: transform 1 rotates output but logical geometry remains landscape

[gutierrezje]

Description

After upgrading an Arch Linux system from Hyprland 0.55.4 / Aquamarine 0.12.1 to Hyprland 0.56.0 / Aquamarine 0.13.0, rotating the internal LVDS panel changes the monitor transform to 1 but leaves the compositor's logical surface geometry at 1366x768.

The pixels rotate, but the desktop extends beyond the visible portrait display instead of becoming 768x1366. Touch coordinates rotate correctly. Full-screen screenshots also cannot capture the inaccessible portion.

Downgrading to the July 19 Arch package snapshot restores correct rotation immediately, with the same configuration and rotation script.

Hardware and software

• Lenovo ThinkPad X230 Tablet
• Intel HD Graphics 4000 (Ivy Bridge)
• Internal LVDS-1 panel: 1366x768@60.02 Hz
• Scale: 1.0
• Arch Linux
• Broken: Hyprland 0.56.0-2, Aquamarine 0.13.0-2, Hyprutils 0.14.0-1
• Working: Hyprland 0.55.4-1, Aquamarine 0.12.1-1, Hyprutils 0.13.1-1
• Legacy Hyprlang configuration manager

Reproduction

Base monitor configuration:

monitor = LVDS-1, 1366x768@60, 0x0, 1

Rotate with:

hyprctl keyword monitor "LVDS-1,1366x768@60,0x0,1,transform,1"

The transform-only form behaves identically:

hyprctl keyword monitor "LVDS-1,transform,1"

Observed result

hyprctl monitors -j reports transform 1, but compositor clients and layers retain landscape geometry:

monitor:   transform=1, width=1366, height=768, scale=1
wallpaper: x=0, y=0, w=1366, h=768
kitty:     at=[3,34], size=[1360,731]
waybar:    x=2, y=2, w=1362, h=29

This is compositor-wide and reproduces with Waybar restarted, Waybar absent from the rotation command, hardware cursors enabled or disabled, a full monitor rule, and a transform-only monitor rule.

Expected result

With transform 1, logical surfaces should be laid out within a 768x1366 portrait output, as they were with Hyprland 0.55.4.

Regression verification

The system was rolled back coherently using the Arch Linux Archive snapshot from 2026-07-19. After rebooting into Hyprland 0.55.4 / Aquamarine 0.12.1, the same monitor configuration and rotation command work correctly.

[tekstryder]

If you can easily repro, please bisect between v0.55.4 and v0.56.0 tags.

• https://wiki.hypr.land/Crashes-and-Bugs/#bisecting-an-issue

[nikolaj-zwergius]

So i have the same problem with the transform happening but the screen just extending out our of the physical screen. Leaving the bottom of the physical screen dark.

after git bisect it should be commit 0aa7a84 that is the cause.

edit: Done on Lua-config

[vaxerski]

legacy configs are no longer supported. Please test on lua.

[nikolaj-zwergius]

My testing and my simliar if not same problem is with lua config. sorry forgot to add that to my comment

[vaxerski]

can you give me a proper repro case then, because I have a vertical monitor and it's just fine

[nikolaj-zwergius]

I now realize that this might be a different problem than the original report, but I will include my repro case here for now.

This is on a 2‑in‑1 laptop, where runtime rotation is needed.

Summary

When changing the monitor’s transform value at runtime, the monitor rotates but does not switch between landscape and portrait.
The layout and buffer size are not updated.

This happens both with:

• hyprctl eval
• manually changing the config and reloading

On my Lua config, neither method works correctly.

On the default Hyprland config, the first runtime transform works, but any further transform changes show the broken behavior described below.

The monitor is correctly set by the config on startup:

• If set to 1, transforms 1 and 3 behave correctly. transforms 0 and 2 behave incorrectly
• If set to 0, transforms 0 and 2 behave correctly. transforms 1 and 3 behave incorrectly

On the default config, the Hyprland background renders correctly after a broken transform, but applications do not.
On my setup, the background is from Noctalia, so it also renders incorrectly.

Environment

• output: eDP-1
• GPU: AMD Vega
• Hyprland versions tested:
  • 0.55.4
  • commit 0aa7a84
• configs tested:
  • Default Hyprland config + transform changes
  • My Lua config

Repro case

Monitor setups at start‑Hyprland

hl.monitor({
    output = "eDP-1",
    mode = "1280x720@60",
    transform = 0,
})

hl.monitor({
    output = "eDP-1",
    mode = "1280x720@60",
    transform = 1,
})

Case A — default config, transform = 0

1. start Hyprland with transform = 0
2. hyprctl eval 'hl.monitor({ output = "eDP-1", transform = 0 })'
3. hyprctl eval 'hl.monitor({ output = "eDP-1", transform = 1 })'
4. hyprctl eval 'hl.monitor({ output = "eDP-1", transform = 0 })'

Result:

• step 3: only half the screen, rotated but still in horizontal layout
• step 4: correct rotation and horizontal mode

Expected:

• step 3 should switch to vertical mode

Case B — default config, transform = 1

1. start Hyprland with transform = 1
2. hyprctl eval 'hl.monitor({ output = "eDP-1", transform = 0 })'
3. hyprctl eval 'hl.monitor({ output = "eDP-1", transform = 1 })'
4. hyprctl eval 'hl.monitor({ output = "eDP-1", transform = 0 })'

Result:

• step 1: correct vertical mode
• step 2: correct rotation + horizontal mode
• step 3: half the screen, rotated but still horizontal
• step 4: correct rotation + horizontal mode

Expected:

• step 3 should switch to vertical mode

Case C — default config, transform = 1

1. start Hyprland with transform = 1
2. hyprctl eval 'hl.monitor({ output = "eDP-1", transform = 1 })'
3. hyprctl eval 'hl.monitor({ output = "eDP-1", transform = 0 })'
4. hyprctl eval 'hl.monitor({ output = "eDP-1", transform = 1 })'

Result:

• step 1: correct vertical mode
• step 3: half the screen, rotated but still in vertical layout
• step 4: correct rotation + vertical mode

Expected:

• step 3 should switch to horizontal mode

Case D — my config, transform = 1

1. start Hyprland with transform = 1
2. hyprctl eval 'hl.monitor({ output = "eDP-1", transform = 0 })'
3. hyprctl eval 'hl.monitor({ output = "eDP-1", transform = 1 })'

Result:

• step 1: correct vertical mode
• step 2: half the screen, rotated but still horizontal
• step 3: correct rotation + vertical mode

Expected:

• step 2 should switch to horizontal mode

Case E — changing mode after transform

This case shows that changing only the transform causes the bug, but changing mode + transform forces a correct rebuild.

1. get to a cropped state from any previous case
2. hyprctl eval 'hl.monitor({ output = "eDP-1", mode = "different from current mode" })'

Result:

• changing mode changes the "stuck" mode to the current mode.

Conclusion

Runtime monitor transform is inconsistent.
The first transformation applies correctly, but any following transform leads to a cropped screen in the wrong mode.
Changing resolution after the transform fixes the layout

[Lodvald]

I'm having the same exact problem on my thinkpad x1 yoga 4th gen when rotating the monitor i get a black space at the bottom, i found that setting the scaling factor to 1 and the transform to 1 as well "fixes" it, as in that programs now render correctly in vertical direction.
However if i try to reset rotation back to 0 i now have the black space on the right side of the display and that gets fixed only with a reboot.

[Dregu]

Oh yeah a bunch of people reproed this a month ago on discord. Start with transform = fine, change it runtime = not fine. Then I guess we all decided not to make an issue.

[gulafaran]

maybe? seems 0aa7a84 changed this.

diff --git a/src/output/Monitor.cpp b/src/output/Monitor.cpp
index d20a09b2..a166494c 100644
--- a/src/output/Monitor.cpp
+++ b/src/output/Monitor.cpp
@@ -696,6 +696,7 @@ bool CMonitor::applyMonitorRuleSoft(Config::CMonitorRule&& pMonitorRule) {
     }
 
     Vector2D xfmd     = m_transform % 2 == 1 ? Vector2D{m_pixelSize.y, m_pixelSize.x} : m_pixelSize;
+    m_size            = (xfmd / m_scale).round();
     m_transformedSize = xfmd;
 
     if (m_createdByUser) {

[tekstryder]

Fix for this by gulafaran was merged with commit 566ff8f.

• fix rotate and mirror regression #15587

@gutierrezje and others, please test and confirm this issue is resolved.

[Lodvald]

Can confirm that the rendering issue is fixed on my side, however it doesn't rotate on the physical rotation of my laptop but that has probably something to do with the iio-sensor-proxy.

[nikolaj-zwergius]

It fixed it for me.