[BUG] VM Issue: After updating hyprland to 0.45.x: Results in breaking EVERYTHING Not launching on SDDM

[Neo-29]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Install 'last ml4 update '

Expected behavior
A clear and concise description of what you expected to happen.
Working desktop?

Screenshots
If applicable, add screenshots to help explain your problem.

Locked on sddm

Distribution (please complete the following information):

• Arch Linux

Additional context
Add any other context about the problem here.

Last update broke everything.
What a pity.
Hope you'll figure out what's the cause.
I was pleased with the previous config.

Why so many changes?

[mylinuxforwork]

@Neo-29 Can you switch to tty with CTRL+ALT+F3 and try to start Hyprland with command Hyprland

[Neo-29]

[mylinuxforwork]

@Neo-29 I have the same issue on my EndeavourOS since today. I run an update of the packages. There is must be a critical change in Hyprland. It is not related to the dotfiles.

I will investigate into it.

[Neo-29]

@Neo-29 I have the same issue on my EndeavourOS since today. I run an update of the packages. There is must be a critical change in Hyprland. It is not related to the dotfiles.

I will investigate into it.

I'm gone on reinstall, we'll see if the issue persists.

[Neo-29]

@Neo-29 I have the same issue on my EndeavourOS since today. I run an update of the packages. There is must be a critical change in Hyprland. It is not related to the dotfiles.

I will investigate into it.

Same issue even on a full reinstall

Something is definitely wrong here

[FR33R00T5]

had the same issue after updating hyprland to 0.45 and 0.45.1. -the solution in my case: it's a problem with the code (ExecStart-Line) in "/usr/lib/systemd/user/hyprland-session.service". you have to change "/usr//usr/bin/Hyprland" in "/usr/bin/Hyprland" .... -hope it helps!

[mylinuxforwork]

had the same issue after updating hyprland to 0.45 and 0.45.1. -the solution in my case: it's a problem with the code (ExecStart-Line) in "/usr/lib/systemd/user/hyprland-session.service". you have to change "/usr//usr/bin/Hyprland" in "/usr/bin/Hyprland" .... -hope it helps!

And which session have you chosen in your Session Manager?

[Neo-29]

had the same issue after updating hyprland to 0.45 and 0.45.1. -the solution in my case: it's a problem with the code (ExecStart-Line) in "/usr/lib/systemd/user/hyprland-session.service". you have to change "/usr//usr/bin/Hyprland" in "/usr/bin/Hyprland" .... -hope it helps!

And which session have you chosen in your Session Manager?

Didn't work here

[mylinuxforwork]

had the same issue after updating hyprland to 0.45 and 0.45.1. -the solution in my case: it's a problem with the code (ExecStart-Line) in "/usr/lib/systemd/user/hyprland-session.service". you have to change "/usr//usr/bin/Hyprland" in "/usr/bin/Hyprland" .... -hope it helps!

Not working.
I have opened an issue on Hyprland GitHub.

[mylinuxforwork]

Just received a feedback.

Duplicate of hyprwm/Hyprland#8340. Use UWSM instead.

Also 0.45.1 no longer contains the service file. That may be a leftover from previous versions.

[mylinuxforwork]

hyprwm/Hyprland#8515

[Neo-29]

What a ridiculous choice they made.
Especially for previous install using sddm
And they are a lot.

[FR33R00T5]

had the same issue after updating hyprland to 0.45 and 0.45.1. -the solution in my case: it's a problem with the code (ExecStart-Line) in "/usr/lib/systemd/user/hyprland-session.service". you have to change "/usr//usr/bin/Hyprland" in "/usr/bin/Hyprland" .... -hope it helps!

And which session have you chosen in your Session Manager?

hyprland systemd

[Neo-29]

Even without a display manager using Hyprland command, it doesn't work...
So..
I'm quite fed up with their constant "moves" without considering the consequences.

[mylinuxforwork]

Even without a display manager using Hyprland command, it doesn't work... So.. I'm quite fed up with their constant "moves" without considering the consequences.

I agree. This is really strange. All Hyprland systems are broken with this update. Curious to see the reaction from the Hyprland developers.

[Neo-29]

Even without a display manager using Hyprland command, it doesn't work... So.. I'm quite fed up with their constant "moves" without considering the consequences.

I agree. This is really strange. All Hyprland systems are broken with this update. Curious to see the reaction from the Hyprland developers.

And users!!

Waiting for it...

Tks again for your hard work around all that.

[rodhfr]

Did a fresh install of Arch (archinstall) on bare metal. Doesn't start from SDDM as described, but works fine when I switch to another TTY and launch Hyprland manually.

[Neo-29]

Did a fresh install of Arch (archinstall) on bare metal. Doesn't start from SDDM as described, but works fine when I switch to another TTY and launch Hyprland manually.

Not here.
I did the same.

Edit :I'm on a vm qemu

[mylinuxforwork]

I suggest that you open an issue on Hyprland GitHub and share your observations. @Neo-29 have seen that you reacted already on my issue.

[mylinuxforwork]

I have updated my laptop to 0.45.1 and could start without issues. But my VMs are still not working. Will check the next days again.

[Neo-29]

I have updated my laptop to 0.45.2 and could start without issues. But my VMs are still not working. Will check the next days again.

On vm virtmanager for me too... so... Yes... Something to investigate 👍👍👍

[mylinuxforwork]

The issue is reported here as well: hyprwm/aquamarine#109

[igor-tereshchenko]

works fine for me with latest hyprland:

hyprland 0.45.1-2
sddm 0.21.0-4
dotfiles 2.9.3

however, after updating dotfiles to the latest version hyprland is crashing, so had to rollback

[mylinuxforwork]

The issue only happens in Virtual Machines. Not on hardware.

[alexchistyakov]

This issue does not just happen in virtual machines. I'm running this on hardware (in Arch) with an AMD Ryzen 9 and an NVIDIA RTX4070 and have been locked out of my work environment for the past 5 days. I've looked through journalctl -b (with verbose logging enabled in Hyprland) and looks like aquamarine can't connect to a renderer.

Specific message: [AQ] [ERR] No renderer connected to backend (printed a billion times)

eglInitialize also fails, which I think causes the massive string of messages about no renderer being connected.

Edit: another crucial message before eglInitialize() fails: [ERR] [AQ] CDRMRenderer: fail, eglInitialize failed

Most likely an issue with an environment variable in one of the config files, since this seems to disproportionately affect ML4W users. There are definitely some environment variables UWSM doesn't want to be set that were set before.

[mylinuxforwork]

This issue does not just happen in virtual machines. I'm running this on hardware (in Arch) with an AMD Ryzen 9 and an NVIDIA RTX4070 and have been locked out of my work environment for the past 5 days. I've looked through journalctl -b (with verbose logging enabled in Hyprland) and looks like aquamarine can't connect to a renderer.

Specific message: [AQ] [ERR] No renderer connected to backend (printed a billion times)

eglInitialize also fails, which I think causes the massive string of messages about no renderer being connected.

Edit: another crucial message before eglInitialize() fails: [ERR] [AQ] CDRMRenderer: fail, eglInitialize failed

Most likely an issue with an environment variable in one of the config files, since this seems to disproportionately affect ML4W users. There are definitely some environment variables UWSM doesn't want to be set that were set before.

I assume it's not related to ML4W Dotfiles. Because it happens on pure Hyprland also installed only with sudo pacman -S hyprland

Will test again the next days. The issue is still open in aquamarine GitHub: hyprwm/aquamarine#109

[nurlan60]

As root, in the file /var/lib/sddm/state.conf
change session to
Session=/usr/share/wayland-sessions/hyprland.desktop

[Neo-29]

As root, in the file /var/lib/sddm/state.conf change session to Session=/usr/share/wayland-sessions/hyprland.desktop

Already these lines in.
Not the issue here.

[Neo-29]

@mylinuxforwork. Tested today with last hyprland and your git version of ml4w...
Still broken unfortunately on virtmanager / qemu

Just to let you know

[alexchistyakov]

I just rolled back to a previous snapshot (after a bunch of headaches with snapper) which has Hyprland 0.44.0 and aquamarine 0.4.3. The issue persists...

I don't have my home directory set to take snapshots, only my root, so this must be coming from some sort of config issue since my entire system is reverted to a working snapshot apart from that.

I'm the guy on hardware and Nvidia btw

Could there be some clashing configs that ML4W modifies and the new version of Hyprland also modifies/relies on? Correct me if I'm wrong, but this seems like the only explanation for my case

[eljejer]

I had this issue also since yesterday. I don't know the cause / which update.
But referring to this issue in the mesa driver, I have a working DE back after downgrading mesa from 24.3.0 to 24.2.7

[eljejer]

This issue does not just happen in virtual machines. I'm running this on hardware (in Arch) with an AMD Ryzen 9 and an NVIDIA RTX4070 and have been locked out of my work environment for the past 5 days. I've looked through journalctl -b (with verbose logging enabled in Hyprland) and looks like aquamarine can't connect to a renderer.
Specific message: [AQ] [ERR] No renderer connected to backend (printed a billion times)
eglInitialize also fails, which I think causes the massive string of messages about no renderer being connected.
Edit: another crucial message before eglInitialize() fails: [ERR] [AQ] CDRMRenderer: fail, eglInitialize failed
Most likely an issue with an environment variable in one of the config files, since this seems to disproportionately affect ML4W users. There are definitely some environment variables UWSM doesn't want to be set that were set before.

I assume it's not related to ML4W Dotfiles. Because it happens on pure Hyprland also installed only with sudo pacman -S hyprland

Will test again the next days. The issue is still open in aquamarine GitHub: hyprwm/aquamarine#109

@mylinuxforwork have you seen this issue?

I could work around my situation of a blank screen coming up on starting Hyprland, by downgrading mesa from 24.3.0 to 24.2.7

[KimVatnedal]

Just updated my laptop and it totally died with some error dispatching to wayland display. Both from launcher (GDM) and terminal. This is on hardware, laptop with nvidia gpu and CachyOS and Gnome as base. Oh well, I had contemplated giving Nix a go, so I guess I will reinstall later.

[igor-tereshchenko]

I just rolled back to a previous snapshot (after a bunch of headaches with snapper) which has Hyprland 0.44.0 and aquamarine 0.4.3. The issue persists...

I don't have my home directory set to take snapshots, only my root, so this must be coming from some sort of config issue since my entire system is reverted to a working snapshot apart from that.

I'm the guy on hardware and Nvidia btw

Could there be some clashing configs that ML4W modifies and the new version of Hyprland also modifies/relies on? Correct me if I'm wrong, but this seems like the only explanation for my case

That's exactly what happened to me, but luckily I did backup my .dotfiles folder before ML4W update and after a rollback via timeshift + .dotfiles rollback everything works again. I even updated hyprland to the latest version without any issues (kept ML4W old version for now).

[alexchistyakov]

I just rolled back to a previous snapshot (after a bunch of headaches with snapper) which has Hyprland 0.44.0 and aquamarine 0.4.3. The issue persists...
I don't have my home directory set to take snapshots, only my root, so this must be coming from some sort of config issue since my entire system is reverted to a working snapshot apart from that.
I'm the guy on hardware and Nvidia btw
Could there be some clashing configs that ML4W modifies and the new version of Hyprland also modifies/relies on? Correct me if I'm wrong, but this seems like the only explanation for my case

That's exactly what happened to me, but luckily I did backup my .dotfiles folder before ML4W update and after a rollback via timeshift + .dotfiles rollback everything works again. I even updated hyprland to the latest version without any issues (kept ML4W old version for now).

Could you somehow compare the two config directories before and after you reverted to your backup and tell us which options are different? This could be the key to resolving this issue

[igor-tereshchenko]

I just rolled back to a previous snapshot (after a bunch of headaches with snapper) which has Hyprland 0.44.0 and aquamarine 0.4.3. The issue persists...
I don't have my home directory set to take snapshots, only my root, so this must be coming from some sort of config issue since my entire system is reverted to a working snapshot apart from that.
I'm the guy on hardware and Nvidia btw
Could there be some clashing configs that ML4W modifies and the new version of Hyprland also modifies/relies on? Correct me if I'm wrong, but this seems like the only explanation for my case

That's exactly what happened to me, but luckily I did backup my .dotfiles folder before ML4W update and after a rollback via timeshift + .dotfiles rollback everything works again. I even updated hyprland to the latest version without any issues (kept ML4W old version for now).

Could you somehow compare the two config directories before and after you reverted to your backup and tell us which options are different? This could be the key to resolving this issue

As I haven't changed anything manually looking at 2.9.3...2.9.6.7
should be sufficient, but unfortunately, the diff is massive and it will be problematic to spot the root cause.

[alansrobotlab2]

oof, this got ugly. ended up doing a full reinstall on arch, no vm, nvidia drivers. installing hyprland on its own results in a simple but functional desktop. installing ml4w using the curl script borks it.

[Neo-29]

oof, this got ugly. ended up doing a full reinstall on arch, no vm, nvidia drivers. installing hyprland on its own results in a simple but functional desktop. installing ml4w using the curl script borks it.

Same... The script breaks all

[alexchistyakov]

oof, this got ugly. ended up doing a full reinstall on arch, no vm, nvidia drivers. installing hyprland on its own results in a simple but functional desktop. installing ml4w using the curl script borks it.

Glad I'm not alone. Could you enable debug logging in Hyprland and check your journalctl to see whether you see the same thing as I was describing? Specifically, try greping (run in tty: journalctl -b | grep -i ) for hypr, renderer, egl

@mylinuxforwork I think it's safe to change the tag to [NVIDIA/VM]. Based on the discussion, it's also isolated to the ML4W dot files (at least as far as NVIDIA goes, might also be two similar but separate issues)

[alansrobotlab2]

Ok, I'm back in business thanks to:
hyprwm/Hyprland#8515 (comment)

steps to resolve/workaround:

1. paru -S uwsm
2. sudo nano /usr/share/wayland-sessions/hyprland-uwsm.desktop
3. systemctl reboot
4. select "Hyprland (uwsm session)" during login
5. enjoy

Name=Hyprland (uwsm session)
Comment=An intelligent dynamic tiling Wayland compositor
Exec=uwsm start hyprland.desktop
Type=Application
DesktopNames=Hyprland
Keywords=tiling;wayland;compositor;

[alexchistyakov]

Ok, I'm back in business thanks to: hyprwm/Hyprland#8515 (comment)

steps to resolve/workaround:

1. paru -S uwsm
2. sudo nano /usr/share/wayland-sessions/hyprland-uwsm.desktop
3. systemctl reboot
4. select "Hyprland (uwsm session)" during login
5. enjoy

Name=Hyprland (uwsm session)
Comment=An intelligent dynamic tiling Wayland compositor
Exec=uwsm start hyprland.desktop
Type=Application
DesktopNames=Hyprland
Keywords=tiling;wayland;compositor;

Maybe I am alone :(
This doesn't resolve it for me

[alansrobotlab2]

Actually scratch that. When I launch hyprland desktop through uwsm all my nvidia gpu accelerated workloads drop to 1/5th speed, including the desktop itself. Super slow, sluggish. even loading up the gpus with neural models slows to a crawl. :-(

No good. 0/10. can not recommend.

For now I still have to ctl+alt+f3 then launch hyprland from the terminal. When done this way at least everything works.

Ok, I'm back in business thanks to: hyprwm/Hyprland#8515 (comment)
steps to resolve/workaround:

1. paru -S uwsm
2. sudo nano /usr/share/wayland-sessions/hyprland-uwsm.desktop
3. systemctl reboot
4. select "Hyprland (uwsm session)" during login
5. enjoy

Name=Hyprland (uwsm session)
Comment=An intelligent dynamic tiling Wayland compositor
Exec=uwsm start hyprland.desktop
Type=Application
DesktopNames=Hyprland
Keywords=tiling;wayland;compositor;

Maybe I am alone :( This doesn't resolve it for me