Closed mylinuxforwork closed 2 hours ago
Platform is EndeavourOS in KVM Virtual Machine.
Changed the paths to /usr/bin/ but Hyprland isn't starting anymore. Works perfectly with 045.1-1. Any ideas?
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.
Duplicate of #8340. Use UWSM instead.
Also 0.45.1 no longer contains the service file. That may be a leftover from previous versions.
Thanks. I will test it. But this has a really big impact. Especially if only Hyprland is installed as the one DE.
I think, a super easy step by step guide is required to explain this new setup. I am receiving many requests from users with completely broken systems.
@fufexan Followed your guide in UWSM but cannot find the uwsm session for Hyprland in /usr/share/wayland-sessions
How to start Hyprland after installing uwsm with sddm?
Make sure Hyprland has been built with systemd support. For some reason it's not automatically detected by meson (iirc the Arch package uses meson), so the flag has to be passed explicitly -Dsystemd=enabled
, and also -Duwsm=enabled
. The latter should be auto-enabled if systemd is also enabled though.
Make sure Hyprland has been built with systemd support. For some reason it's not automatically detected by meson (iirc the Arch package uses meson), so the flag has to be passed explicitly
-Dsystemd=enabled
, and also-Duwsm=enabled
. The latter should be auto-enabled if systemd is also enabled though.
This is not for beginners. How does existing Hyprland users know that? Arch users are installing or updating Hyprland with sudo pacman -S hyprland resulting in a broken system.
All of my test systems are broken after running just yay.
Is there a way to make the update to 0.45.1 more user friendly fro Arch and Endeavour users?
I can confirm... It's BROKEN. Please consider that you've got users and not developers only at the end of the line. This is important.
Just restarted my Laptop with 0.45.1 with no issues.
Maybe it's only a KVM VM issue?
Just restarted my Laptop with 0.45.1 with no issues.
Maybe it's only a KVM VM issue?
Could be. I'm on kvm too. Something to investigate.
Is there a way to make the update to 0.45.1 more user friendly fro Arch and Endeavour users?
Check whether the PKGBUILDS are wrong, and if so, contact the package maintainers. However the systemd meson feature has been available for a long time now, shouldn't cause issues. The uwsm
feature was added and enabled by default, so that also shouldn't cause issues.
I have no experience with KVM VMs, so I can't assist there.
Is there a way to make the update to 0.45.1 more user friendly fro Arch and Endeavour users?
Check whether the PKGBUILDS are wrong, and if so, contact the package maintainers. However the systemd meson feature has been available for a long time now, shouldn't cause issues. The
uwsm
feature was added and enabled by default, so that also shouldn't cause issues.I have no experience with KVM VMs, so I can't assist there.
Thank you for your feedback. I will create a new Arch Linux VM with Hyprland profile in a VM and will try again.
Already reported ? *
Regression?
Yes
System Info and Version
System/Version info
```shDescription
Just installed yay -S hyprland to 0.45.1 Hyprland isn't starting anymore.
The reason is the broken /usr/lib/systemd/usr/hyprland-session.service
[Service] Type=notify ExecStart=/usr//usr/bin/Hyprland ExecStop=/usr//usr/bin/hyprctl dispatch exit ExecStopPost=systemctl --user unset-environment DISPLAY WAYLAND_DISPLAY HYPRLAND_INSTANCE_SIGNATURE XDG_CURRENT_DESKTOP Restart=on-failure Slice=session.slice
The ExecStart and ExecStop paths are wrong.
How to reproduce
Install 0.45.1 and try to start Hyprland with sddm or Hyprland command.
Crash reports, logs, images, videos
No response