Hyprland 0.55.0 config errors in default/hypr/looknfeel.conf (col.border_locked = -1, dwindle:pseudotile removed)

[Ehsanul-deepchainlabs]

System details

Intel i7-13700H, NVIDIA RTX 4060, Omarchy 3.8.0 (master @ b2d95ee), Hyprland 0.55.0

What's wrong?

On a fresh boot, Hyprland reports three config errors from the stock omarchy default looknfeel.conf:

Config error in file /home//.local/share/omarchy/default/hypr/looknfeel.conf at line 53: Error parsing gradient -1: failed to parse -1 as a color
Config error in file /home//.local/share/omarchy/default/hypr/looknfeel.conf at line 54: Error parsing gradient -1: failed to parse -1 as a color
Config error in file /home//.local/share/omarchy/default/hypr/looknfeel.conf at line 111: config option dwindle:pseudotile does not exist.

Cause

Hyprland 0.55.0 dropped support for two things the omarchy default config still uses:

1. Lines 53–54 — col.border_locked_active = -1 / col.border_locked_inactive = -1. The -1 "inherit from parent color" shorthand is no longer accepted; the parser expects a real color/gradient. Confirmed via
   hyprctl getoption group:col.border_locked_active → custom type: 0 0deg.
2. Line 111 — dwindle:pseudotile = true. The option was removed in Hyprland 0.55.0. Confirmed via hyprctl getoption dwindle:pseudotile → no such option.

Steps to reproduce

1. Install Omarchy 3.8.0 (or update an existing install to master @ b2d95ee).
2. Be on Hyprland 0.55.0 (current Arch hyprland package).
3. Reboot / re-login. Errors appear in the Hyprland error overlay and hyprctl configerrors.

Workaround

Errors are non-fatal — Hyprland continues to run, those three lines are just ignored. Users can override col.border_locked_active/inactive in ~/.config/hypr/looknfeel.conf with explicit colors, but there's no way
to "un-set" dwindle:pseudotile from a sourced default — it has to be removed from the default file itself.

Suggested fix

Update default/hypr/looknfeel.conf for Hyprland 0.55.0:

• Replace col.border_locked_active = -1 with col.border_locked_active = $activeBorderColor (and same for inactive), or drop the two lines (Hyprland falls back to col.border_active/inactive by default).
• Remove the dwindle { pseudotile = true ... } line — pseudotile is now per-window only (via the pseudo dispatcher / windowrule = pseudo, ...).

Noticed the hyprland-lua-conversion branch is already overhauling this area, so this may already be addressed there — flagging in case it should also be patched on master before that lands.

omarchy-debug

omarchy-debug.txt

[lucifer]

Yeh I have this too, fully updated on the Dev channel as of May 11 noonEST, issue persists.

[wh01s17]

same problem

[ryanrhughes]

Resolved via #5723

[lucifer]

Confirmed, no more errors.

[realaaa]

thanks for that mate this is great ! helped a lot

on this note - HOW is this error being presented this horrible way, is it on purpose??

this basically makes it impossible to use your browser almost - as this is on top of your top of the screen

absolutely horrendous design decision, surely they can report non-fatal errors in a LESS intrusive way ?

I mean I get it - we do need to know when something is broken in the configs, but this is IN YOUR FACE ?

sorry, rant finished :)