Your system information

• Steam client version (Build May 30 2023)
• Distribution (e.g. Ubuntu): Ubuntu 23.04
• Opted into Steam client beta?: No
• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

I use
/usr/games/steam -pipewire -pipewire-dmabuf 2>/dev/null
to stream games from Host (Ubuntu 23.04 / Wayland) to Client (Steam Deck or Nvidia Shield)

It works right after Steam client is started on Host, but it's too "unstable".
Everytime my screensaver is triggered and my session locked (on Host), the "share screen" permission (which I gave when Steam client started) is lost.
Then I cannot use Remote Play anymore, nor re-enable the "share screen" permission, until I fully restart Steam (which is quite long on my setup)

Describe what you expected should happen and what did happen.

I'm not sure if the "share screen" permission can be kept after session is locked (I guess it's a xdg-desktop-portal problem), but at least, Steam client could re-ask permission to share screen everytime Remote Play is started (It was discussed here : https://github.com/ValveSoftware/steam-for-linux/issues/8098#issuecomment-925952213 ), or/and with a button in Steam user interface (ideally).

=> It would save the time of restarting Steam client after unlocking session/screensaver.

Steps for reproducing this issue:

1. Start Steam on Ubuntu 23.04/Wayland with steam -pipewire -pipewire-dmabuf, accept to share screen (notice the permission notification in top-right of the screen)
2. Enjoy a bit of Remote Play from a Client
3. After the Remote Play session, let the screensaver locks the Ubuntu session on Host
4. Unlock the Ubuntu session : notice that the permission notification is gone
5. Try to Remote Play : sound is OK but screen is frozen and garbled.