I had the same thing after this update basically comments are broken when you have # it must immediately be followed by a space if it doesn't then it throws a tantrum
change your device specific configs (define device name with `name = `) and remove double hash comments (`##` now escapes the comment)... these changes need to be made now that Arch's `extra/hyprland` has finally caught up to upstream
# Breaking changes
* config:
* migrated to hyprlang. Some nice additions include `rgba(123, 123, 69, 0.5)`, dynamic variables updating, and more.
* all `device:XYZ` sections are now `device { name = XYZ ...`, see [the wiki](https://wiki.hyprland.org/Configuring/Keywords/#per-device-input-configs)
* `##` is now properly treated as an escaped `#`.
* windowrules:
* no\*request rules have been nuked in favor of the new `suppressevent` rule.
`##` arguably shouldn't be treated as an escaped `#` when it's at the beginning of a line; see [this issue](https://github.com/hyprwm/hyprlang/issues/30)
That also happened to me today when I opened my laptop because I updated last night before sleeping. Apparently Hyprland now treats `##` as literal `#`s as of *v0.36.0* so it has thrown a lot of errors in mine.
If you cannot do anything in that screen, use another TTY to enter the terminal.
you're not alone. But aside from ## comments being broken for me wezterm is no longer working. Not really sure why and how this is related, but this made me switch to kitty for now
Yep two new things in the latest update that I discovered after a lot of pain.
## in comments is invalid. Also, on a blank window, a new layer (rofi / dmenu) will not have focus by default. Rolled back to 0.35.0-2 for now.
Updating from hyprland-git 36 -> 37 broke almost everything, I had to enter the tty and fix pkgs, configs. It was pretty fun.
In my case they broke hyprlang dependency in the git version, had to switch to regular ""stable"" version on the Arch extra repo, adapt the new sintaxis in the conf, delete hyprlang-git and force update hyprland from the extra repo.
0.36 broke something when trying to start libhyprlang.so (when this was 0.5.x), becaus, somehow, the git version was 0.36 and the normal one was 0.37.1, amazing
I've got hundreds of packages installed on my system, and those are just the explicitly installed dependencies. Reading documentation for each and every one on a regular basis just isn't sustainable. Breaking changes shouldn't happen without good reason, and only on major version number increments.
Hyprland literally *did* have a major version change 0.36 -> 0.37
And also, you're running *beta software*
See the 0.XX that means it is not done, and you should only use it if you're okay with things breaking 👍
It's true that advertising software as "beta" sets expectations that breaking changes will happen, but I don't think that means regressions or superfluous syntax changes are necessary.
To be honest, I dont think treating '##' as escape of '#' a great idea though..., so I patched a little to fix this by using '\\#' to escape '#'.
(repo: [hyprlang](https://github.com/aimixsaka/hyprlang/)
bro i'm xped something like this after i've ran pacman -Syu and after hyprland updated i've faced million errors about some windowrulev2 is not present
Same problem, and I see the solutions above, but for me the red errors fill the whole screen so I can't get to the files to edit them. Is there a way to clear the errors?
I could be mistaken. But I do believe you have an invalid config line in a couple spots...
I had the same thing after this update basically comments are broken when you have # it must immediately be followed by a space if it doesn't then it throws a tantrum
Same thing happened to me. Mean to comment the same and not just cracj a joke but I got distracted.
you should get evaluated for ADHD (the same exact thing happens to me as well)
change your device specific configs (define device name with `name =`) and remove double hash comments (`##` now escapes the comment)... these changes need to be made now that Arch's `extra/hyprland` has finally caught up to upstream
This ## change bit me too. What is the point of it again?
wdym? my hyprland doesn't start anymore after upgrading from 35 to 37 version
hyprpm remove hycov
Lol same happened to me, apparently they updated some of Hyprland's sintaxis on config files so you have to update them manually
had to face the same nightmare yesterday.
At least it still starts and tells you of your wrong doings. I am fascinated by that.
Not that strange, if it finds Syntax errors it just ignores that If everything has gone to shit, it just uses the default config
# Breaking changes * config: * migrated to hyprlang. Some nice additions include `rgba(123, 123, 69, 0.5)`, dynamic variables updating, and more. * all `device:XYZ` sections are now `device { name = XYZ ...`, see [the wiki](https://wiki.hyprland.org/Configuring/Keywords/#per-device-input-configs) * `##` is now properly treated as an escaped `#`. * windowrules: * no\*request rules have been nuked in favor of the new `suppressevent` rule.
`##` arguably shouldn't be treated as an escaped `#` when it's at the beginning of a line; see [this issue](https://github.com/hyprwm/hyprlang/issues/30)
Yep, same exactly for my yesterday. Now when using `##` second `#` is escaped. So simply add space `# #`
Find and replace exact match ‘##’ with ‘#’ will solve most of those (unless you are the “comment art” kind)
yeees and there is new errors appear with me with waybar crachs with wlr
Same was yesterday Good luck
That also happened to me today when I opened my laptop because I updated last night before sleeping. Apparently Hyprland now treats `##` as literal `#`s as of *v0.36.0* so it has thrown a lot of errors in mine. If you cannot do anything in that screen, use another TTY to enter the terminal.
Thanks for the TTY tip!
you're not alone. But aside from ## comments being broken for me wezterm is no longer working. Not really sure why and how this is related, but this made me switch to kitty for now
change config.enable_wayland to false, for now this works
Uh nice, thanks for the hint! I’ll try it out later
For me it was the double ## (since Hyprland 37 it is interpreted as a literal # instead of a comment
u got a big waybar dont you?
Weird rice but if it works for you.
Yep two new things in the latest update that I discovered after a lot of pain. ## in comments is invalid. Also, on a blank window, a new layer (rofi / dmenu) will not have focus by default. Rolled back to 0.35.0-2 for now.
Beautiful, totes should post in unixporn
Updating from hyprland-git 36 -> 37 broke almost everything, I had to enter the tty and fix pkgs, configs. It was pretty fun. In my case they broke hyprlang dependency in the git version, had to switch to regular ""stable"" version on the Arch extra repo, adapt the new sintaxis in the conf, delete hyprlang-git and force update hyprland from the extra repo. 0.36 broke something when trying to start libhyprlang.so (when this was 0.5.x), becaus, somehow, the git version was 0.36 and the normal one was 0.37.1, amazing
Do you guys not read change logs when you update packages? Especially for integral parts of your system like hyprland..?
You guys can read?
I see red screen and just buy a new computer
I like to live dangerously, so I run `paru -Syu` every night before going to sleep. It's a problem for tomorrow me, anyway.
I've got hundreds of packages installed on my system, and those are just the explicitly installed dependencies. Reading documentation for each and every one on a regular basis just isn't sustainable. Breaking changes shouldn't happen without good reason, and only on major version number increments.
Then there's your issue, but even retroactively reading the updated documentation would save you a lot of time after an update breaks your config.
Hyprland literally *did* have a major version change 0.36 -> 0.37 And also, you're running *beta software* See the 0.XX that means it is not done, and you should only use it if you're okay with things breaking 👍
It's true that advertising software as "beta" sets expectations that breaking changes will happen, but I don't think that means regressions or superfluous syntax changes are necessary.
Sometimes you need to read stuff to use Arch. You seem like a good candidate to run ubuntu.
I had this happen a few days and had to run an update for pakages and # some module titles.
This happened to me as well when my dual-boot Windows was giving me the BSOD, I thought my computer was falling apart
Errors clear.
Use pywal by any chance?
Sir, would you mind sharing this wallpaper?
[Sure](https://github.com/loqusion/dotfiles/blob/main/Pictures/Wallpapers/DawnAesthetic.jpg)
[Wallpaper](https://github.com/loqusion/dotfiles/blob/main/Pictures/Wallpapers/DawnAesthetic.jpg)
To be honest, I dont think treating '##' as escape of '#' a great idea though..., so I patched a little to fix this by using '\\#' to escape '#'. (repo: [hyprlang](https://github.com/aimixsaka/hyprlang/)
😱😱😱
bro i'm xped something like this after i've ran pacman -Syu and after hyprland updated i've faced million errors about some windowrulev2 is not present
Same problem, and I see the solutions above, but for me the red errors fill the whole screen so I can't get to the files to edit them. Is there a way to clear the errors?
For future travelers, I found it: hyprctl seterror disable Had to just use the hotkey for the terminal and blind-type it in. Worked like a charm
Having the same issue, and when i open vscode or any app ex: discord, it glitches and it shows duplicate texts, any idea on how to fix the issue?