[BUG] Config errors from new Hyprland update

[BroDudeGuyMan]

Describe the bug

Hyprland errors related to the dwindle:pseudotile layout are appearing after the most recent update.

Config error in file /home/${USER}/.config/hypr/conf/layouts/default.conf at line 6: config option <dwindle:pseudotile> does not exist.

Steps to reproduce

Installing the latest packages from the Waybar widget, and then rebooting.

Expected behavior

Should just work as normal.

Screenshots

Distribution

Arch Linux

If Other, specify

No response

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[BroDudeGuyMan]

hyprwm/Hyprland#8424 (comment)

The link above is to the related breaking change from the Hyprland repo.

[dwilliam62]

Update you ML4W dotfiles Or you can remove the lines that the errors shows "does not exist"

This is not a "bug" it's the reality of Hyprland as it's a project still being developed at a rapid pace Those values are no longer supported in 0.55

[dwilliam62]

Once you remove that line the errors will stop

[mylinuxforwork]

Don described correctly the two possible ways to solve this issue.

[escuco]

Same here with CachyOS.
Removing the line seems to be safe, it worked for me.

[dwilliam62]

Does anyone else with two screens experience, that the mouse cursor is locked only to screen 1? hyprctl reload fixes the issue temporary but I can't find out what's actually wrong. Also, some of my custom windowrules doesn't seem to apply anymore. Peculiar issue... That cursor lock happens after restart or log-out. In display manager works fine so it's definitely hyprland.

Also, sorry for barging in, but seemed fitted since the issue appeared with 0.55 update...

Since this is not related to the topic, you should create your own topic and provide hardware info, OS, and what version of the ML4W dotfiles because I am guessing you aren't on the current version of them to start. Adding in an unrelated issue, just makes it more confusing, who is talking about what issue.

[mrjxtr]

just remove the line that has pseudotile on your config... the official release notes says it's not doing anything in the first place, so it's safe to remove.

dwindle:pseudotile has been removed as it wasn’t doing anything.

[OsoTx713]

Does anyone else with two screens experience, that the mouse cursor is locked only to screen 1? hyprctl reload fixes the issue temporary but I can't find out what's actually wrong. Also, some of my custom windowrules doesn't seem to apply anymore. Peculiar issue... That cursor lock happens after restart or log-out. In display manager works fine so it's definitely hyprland.

Also, sorry for barging in, but seemed fitted since the issue appeared with 0.55 update...

Since this is not related to the topic, you should create your own topic and provide hardware info, OS, and what version of the ML4W dotfiles because I am guessing you aren't on the current version of them to start. Adding in an unrelated issue, just makes it more confusing, who is talking about what issue.

Mine does the exact same thing have you found a fix yet?

[mrjxtr]

Mine does the exact same thing have you found a fix yet?

Check issue #1600 ... my fix personally was downgrading to v0.54

[mylinuxforwork]

You can install ML4W OS 2.12.3 or remove the line from the file. No need to downgrade.

[mrjxtr]

You can install ML4W OS 2.12.3 or remove the line from the file. No need to downgrade.

Yes, removing the line from the file works for the config error.

Downgrading to v0.54 was my fix for the "the mouse cursor is locked only to screen 1" bug

[dwilliam62]

You can install ML4W OS 2.12.3 or remove the line from the file. No need to downgrade.

Yes, removing the line from the file works for the config error.

Downgrading to v0.54 was my fix for the "the mouse cursor is locked only to screen 1" bug

You might want to check the 54.1 fix list. There were some important fixes there

[mylinuxforwork]

Fixed on Rolling Release for 2.13.0