egrechko
commented
3 months ago I am getting the exact same issue as well.
Open Kofa1 opened 3 months ago
egrechko
commented
3 months ago I am getting the exact same issue as well.
d-air1
commented
3 months ago I'm not a hyprland user, but I just found out about this protocol finally being merged in wayland. It is based on wlroots wlr-screencopy-unstable-v1, but with improvements.
Link to phoronix article here: https://www.phoronix.com/news/Wayland-Merges-Screen-Capture Link to merge request: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/124
In the link that OP provided, the hyprland project seems to recommend that wlr_screencopy_v1 be used instead of wlr_export_dmabuf. Whereas If I'm understanding this correctly, this new protocol having being merged in upstream wayland protocols might be a bit more generic and useful for all desktop environments instead of just wlroots based ones. Assuming the rest of the desktops implement this. According to the merge request, wlroots already has. Perhaps this thread should be moved to a discussion for the time being?
Kofa1
commented
3 months ago I'm not a hyprland user, but I just found out about this protocol finally being merged in wayland. It is based on wlroots wlr-screencopy-unstable-v1, but with improvements.
Link to phoronix article here: https://www.phoronix.com/news/Wayland-Merges-Screen-Capture Link to merge request: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/124
In the link that OP provided, the hyprland project seems to recommend that wlr_screencopy_v1 be used instead of wlr_export_dmabuf. Whereas If I'm understanding this correctly, this new protocol having being merged in upstream wayland protocols might be a bit more generic and useful for all desktop environments instead of just wlroots based ones. Assuming the rest of the desktops implement this. According to the merge request, wlroots already has. Perhaps this thread should be moved to a discussion for the time being?
Aren't they saying it's a Sunshine issue, which uses outdated protocols? Sorry, I'm not a Wayland dev I have no idea what they're responsible for, just trying to use Linux.
https://github.com/hyprwm/Hyprland/issues/6623#issuecomment-2185228948
https://github.com/hyprwm/Hyprland/issues/6623#issuecomment-2192660921
d-air1
commented
3 months ago @Kofa1 that is what they are saying, but his suggestion has also become outdated.
aruhier
commented
3 months ago @Kofa1 that is what they are saying, but his suggestion has also become outdated.
Kind of, as I don't think sway or hyprland support ext-image-capture-source-v1 already. I guess that wlr_screencopy_v1 will become deprecated in favor ext-image-capture-source-v1 at one point.
Kofa1
commented
2 months ago @Kofa1 that is what they are saying, but his suggestion has also become outdated.
Kind of, as I don't think sway or hyprland support
ext-image-capture-source-v1already. I guess thatwlr_screencopy_v1will become deprecated in favorext-image-capture-source-v1at one point.
I don't really understand, is it going to magically recognise the monitors once that protocol is updated in Hyprland?
aruhier
commented
2 months ago Nothing is magical, Sunshine needs to explicitly implement the client side of these protocols (wlr_screencopy_v1 to support the current releases of Hyprland and Sway, ext-image-capture-source-v1 for the standard protocol that is not yet implemented in Hyprland or Sway).
Hyprland and Sway for the moment only supports wlr_screen_copy_v1, I think ext-image-capture-source-v1 is being merged in wlroots. So if Sunshine switches to wlr_screen_copy_v1 instead of wlr_export_dmabuf, yes the monitors will be recognized directly on Hyprland and Sway. In the future, wlr_screen_copy_v1 might be deprecated for ext-image-capture-source-v1, which supports window/zone capture (and not only screen capture).
korm-spec
commented
2 months ago Is this gonna be fixed anytime soon? It's been a month and the problem exists for 5 months already.
gschintgen
commented
1 month ago Is this gonna be fixed anytime soon? It's been a month and the problem exists for 5 months already.
Could you link to your PR that fixes it? More seriously: This is a volunteer project. Things happen if somebody comes along and implements it. (This could be you!)
Pressuring is only counterproductive. It leads to developers getting grumpy, ignoring the issue or burning out.
Your choices are to be patient, to fix it yourself, or to hire somebody to do it.
Please be considerate. (Giving a thumbs up to the original report is fine and shows interest. Comments are for useful additional information.)
ElYaiko
commented
2 weeks ago Having same issue Any update?
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the latest beta/pre-release?
I'm too lazy to test
Describe the Bug
Virtual outputs created with
hyprctl output create headlessdon't seem to be recognized by Sunshine.Error: Unknown Monitor connector type [HEADLESS]: Please report this to the GitHub issue tracker\Expected Behavior
No response
Additional Context
https://github.com/hyprwm/Hyprland/issues/6623#issue-2367348069
Host Operating System
Linux
Operating System Version
6.10.2-arch1-1, Hyprland window manager
Architecture
64 bit
Sunshine commit or version
Sunshine version: 0.23.1
Package
Linux - AUR (Third Party)
GPU Type
Nvidia
GPU Model
TU117
GPU Driver/Mesa Version
nvidia-open 555.58.02-10
Capture Method
None
Config
Apps
No response
Relevant log output