Why there are two options 1) garuda_hyprland and 2)hyprland at login manager.
And what is the difference between them?
No need I think so
Why there are two options 1) garuda_hyprland and 2)hyprland at login manager.
And what is the difference between them?
No need I think so
The garuda_hyprland version launches Hyprland with a wrapper script which sets some needed environment variables, and is the recommended choice.
The reason we made a separate option for it is because the “regular” one gets overwritten every time the Hyprland package is updated. We considered trying to make the file immutable, but eventually decided instead to create a separate .desktop
file in /usr/share/wayland-sessions
, which is identical to the regular one except it launches the hyprstart
wrapper script instead of directly launching hyprland
.
/usr/share/wayland-sessions
├── garuda_hyprland.desktop
└── hyprland.desktop
File: /usr/share/wayland-sessions/garuda_hyprland.desktop
[Desktop Entry]
Name=Garuda Hyprland
Comment=An intelligent dynamic tiling Wayland compositor
Exec=hyprstart
Type=Application
If you would like to take a peek and see what it is doing, or make any changes, hyprstart
itself is a script in /usr/local/bin
.
2 posts were split to a new topic: Thank you for this feature and overall how Hyprland is configured!