Closed JimitSoni18 closed 2 months ago
You currently need to run pipewire before niri, spawn-at-startup is too late for that.
i tried pipewire before starting niri, but it did not work
That's weird, it should work I think.
yeah i'll try again and see if it works
now i am able to use screencast, previously i was spawning pipewire directly in the shell using nohup pipewire > /dev/null &
, now i an launching in a fish script, and it does seem to work.
i still think it is weird that it does not work when pipewire is spawned from the shell
System Information
void linux on thinkpad, glibc
i have observed that when i run niri in a dbus session, using
dbus-run-session niri --session
, then start a browser and try screensharing, in google meet or discord or anywhere else, the gtk window picker does not open. here is an image after i left the google meeting saying it could not share screen:however, if i exit niri (pressing super+shift+e) then run command
niri
(not running in a session, and not using flag --session), then exit that again (pressing super+shift+e), and run niri in a dbus session again, usingdbus-run-session niri --session
, the screen casting starts working, and the gtk window picker appears this time. see the picture attached:here are some spawn commands i run when i run niri, if it helps: spawn-at-startup "pipewire" spawn-at-startup "dunst" spawn-at-startup "swww-daemon" spawn-at-startup "swww img wallpapers.webp" spawn-at-startup "eww" "open" "bar"
i thought that maybe niri requires pipewire running on startup to cast screen, so i tried pipewire before starting niri, but it did not work.