Unable to screenshare in Niri

[ConsularParadi]

I wasn't aware that niri did not have screensharing built in and just installed xdg-desktop-portal-gnome and rebooted my system but the service fails with
Dependency failed for Portal service (GNOME implementation).
Also I was running the cmd niri when entering through greetd-tuigreet but have changed it to niri --session.
Are there any troubleshooting steps that I should go through?

[YaLTeR]

Installing xdp-gnome and starting niri through niri-session script should be sufficient. Also make sure pipewire is running before niri

[YaLTeR]

When it takes you to the terminal, does it say anything? Anything in journalctl --user-unit=niri -b?

[ConsularParadi]

It says No Entries.
I'm not sure if this is relevant but in both cases (the original script and the wrapper script) systemctl --user status niri also returns inactive (dead).
Also I was using tuigreet --cmd niri in greetd config file which I assume first runs niri-session upon login as mentioned in the desktop entry and then runs niri command to directly throw me into the GUI

[YaLTeR]

Seems like systemd never starts it?

[ConsularParadi]

It seems so. I'll hop onto tuigreet's repo to inquire on how to setup niri with greetd.
Just to be clear, when running in absence of a display manager, niri-session is a binary that needs to be run to setup all related services and environment variables for the system to function?
And should the GUI be automatically accessible or the niri command needs to be run to access that?

[YaLTeR]

You can cat the niri-session. It's a shell script that more or less boils down to starting niri.service, which itself runs niri. You should be able to run it on the tty. I use GDM with the .desktop file from this repo (same as you showed above).

[BRS5672023]

It seems the first part about SHELL in the niri-session script is causing boot loop when I use the following fish script to start session..

if [ -z $WAYLAND_DISPLAY ] && [ $XDG_VTNR -eq 1 ]
    niri-session
end

[YaLTeR]

niri-session is not the only script that does that. Seems you're missing some check in this condition.

[BRS5672023]

Sorry I'm not familiar with shell scripts but using the fish script so that it will automatically start niri session when I login in tty1.. and I'm not seeing the reason why this will cause a bootloop while I used to start the session with niri --session which is totally fine but having the same issue with @ConsularParadi encountered here..