Ya know, instead of managing the pipewire services as exec inside hyprland why not use shed, it provides an implementation of user services and can handle Wayland sessions.

https://github.com/eylles/shed

OP from the org account here, it's because I've yet to have heard of it. I've never had to deal with manually managing Pipewire before, so I'm a bit green & lost in that department. Might look into it sometime.

Real; I myself am doing that, finally.

https://github.com/eylles/shed

the manpage provides an example for using with sway, my latest shed development related forum post gives some insight on what shed can do and how it may be used for wayland sessions, mind you i got no idea how those are started beyond that the compositor is also the windowing server so it needs to have environment preparation before running, which shed can do
https://dev1galaxy.org/viewtopic.php?pid=63141#p63141

mind you my only frame of refference for wayland stuff is https://wiki.gentoo.org/wiki/Sway#Starting_Sway

but i can guarantee you that in my x11 setup shed is able to perfectly manage pipewire.

Export the necessary environment variables

Setting these variables ensure that Hyprland and Wayland-based applications are properly identified and can function correctly on your Devuan system.

export XDG_CURRENT_DESKTOP=Hyprland
export XDG_SESSION_TYPE=wayland
export MOZ_ENABLE_WAYLAND=1

Launch Hyprland with D-Bus session

The dbus-run-session command is used to start a new D-Bus session, which is necessary for Hyprland to communicate with other system services. The -- separates the dbus-run-session command from the hyprland command, ensuring that Hyprland is executed as the main process:

Launch Hyprland with:

dbus-run-session start-hyprland

By including these commands in your startup or session configuration, you should be able to run Hyprland on your Devuan system and share the screen as desired.

Turning on screenshare in Vesktop

Launch Vesktop (I have the .deb version of the package installed), enter a voice chat, then click Share Your Screen. When the screensharing popup window appears, check Allow a restore token, then click the desired source to stream from.

Speculation, Documentation, & Help

Can't seem to locate where the information found was sourced from; currently the commentary posted probably isn't the most correct regarding commands or programs do what. Please feel free to correct comment corrections or point newer users to the right direction for any mistakes made causatively in this post.

There's also the official Screen sharing - Hyprland documentation on this topic.

Happy to help!

I've been trying to, on-and-off, get Hyprland to be able to screenshare sound and windows/screens. The primary way that I have historically done this on systemd based Linux distributions (OpenMandriva Lx) is via Vesktop.. This has also been an issue with things like attempting to stream or record video on things like OBS.

In Vesktop, when I click the screenshare button in `i3` on XLibre, it simply works now that I am able to launch `pipewire` properly on boot. However, when I switch to Hyprland, when I click the screenshare button on Vesktop, the program simply refuses to open/display the window to display the possible sources for sharing at all. Peculiar.

In an earlier post, I shared that I was able to get Pipewire to work on Hyprland, which from my understanding is what is relied upon for the sound portion of the share for compositors:

I've been trying to further experiment, but I'm stuck.

In short, here are some relevant notes that could indicate the source of what the solution may be:

1. Created the scripts that the pipewire article on the Gentoo wiki suggests
2. Attempted to follow the GitHub Gist the Hyprland wiki (linked above) suggested
3. One output I do get whenever I stop Hyprland and get booted back into the TTY is the following:

dconf-WARNING **: 12:34:41:884: failed to commit changes to dconf: Cannot autolaunch without X11 $DISPLAY

    One thing I've seen suggested on the net a lot is to do something like the following:

export DISPLAY=:0

    I do not see a change as a result of this, at least from my understanding.