fairyglade / ly

display manager with console UI
Do What The F*ck You Want To Public License
5.41k stars 306 forks source link

[Bug] When starting Hyprland from ly XDG_CURRENT_DESKTOP value is blank. #702

Open whyok456 opened 1 week ago

whyok456 commented 1 week ago

Pre-requisites

Ly version

Ly version 1.1.0-dev.101+e885a5e

Observed behavior

When starting Hyprland from ly XDG_CURRENT_DESKTOP doesn't start xdg-portal for hyprland. Which means I can't use apps like obs.

Expected behavior

On other display managers like sddm and greetd it doesn't show any error.

Steps to reproduce

  1. install ly from the compiling steps
  2. try to launch Hyprland
  3. shows this error

Relevant logs

Screenshot-2024-10-10_21:15:40

whyok456 commented 1 week ago

ok well nvm it can be fixed by adding

env = XDG_CURRENT_DESKTOP,Hyprland

to /.config/hypr/hyprland.conf, though it's still weird it gives this error by default

AnErrupTion commented 3 days ago

@whyok456 Hey there! This actually isn't the correct solution, only a workaround. Can you send the output of your Hyprland desktop file in /usr/share/wayland-sessions please?

devlsh commented 2 days ago

@AnErrupTion

[Desktop Entry]
Name=Hyprland
Comment=An intelligent dynamic tiling Wayland compositor
Exec=Hyprland
Type=Application

also having this issue!

AnErrupTion commented 2 days ago

@devlsh What distribution are you using? Whoever packaged Hyprland for it forgot to add the DesktopNames attribute. This means it isn't an Ly issue but a packaging issue.

whyok456 commented 1 day ago

@whyok456 Hey there! This actually isn't the correct solution, only a workaround. Can you send the output of your Hyprland desktop file in /usr/share/wayland-sessions please?

same as devlsh

[Desktop Entry] Name=Hyprland Comment=An intelligent dynamic tiling Wayland compositor Exec=Hyprland Type=Application

and I got hyprland off pacman

Screenshot-2024-10-21_19:48:15

pgrond commented 1 day ago

Yep, can confirm this. Also on Arch.

AnErrupTion commented 1 day ago

Looks like the issue got fixed in master, but it hasn't yet been released. Not sure if you can report this as a bug to the person packaging it so they can fix it, or if they prefer waiting for a new release.