mylinuxforwork
[BUG] VM Issue: After updating hyprland to 0.45.x: Results in breaking EVERYTHING Not launching on SDDM
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- 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?
@Neo-29 Can you switch to tty with CTRL+ALT+F3 and try to start Hyprland with command Hyprland
@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 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 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
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!
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?
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
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.
Just received a feedback.
Duplicate of https://github.com/hyprwm/Hyprland/issues/8340. Use UWSM instead.
Also 0.45.1 no longer contains the service file. That may be a leftover from previous versions.
What a ridiculous choice they made. Especially for previous install using sddm And they are a lot.
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
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.
Even without a display manager using
Hyprlandcommand, 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.
Even without a display manager using
Hyprlandcommand, 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.
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.
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
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.
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.
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 👍👍👍
The issue is reported here as well: https://github.com/hyprwm/aquamarine/issues/109
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
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.
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: https://github.com/hyprwm/aquamarine/issues/109
As root, in the file /var/lib/sddm/state.conf change session to Session=/usr/share/wayland-sessions/hyprland.desktop
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.
@mylinuxforwork. Tested today with last hyprland and your git version of ml4w... Still broken unfortunately on virtmanager / qemu
Just to let you know
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