Bug 1765448

Description of problem:
There are several concerns with screen sharing experience revealed after rebase to a new version pipewire-0.2.7-1.el8.x86_64

Environment: RHEL-8.2.0-20191020.n.0, both VM and bare metal + updated pipewire

1. Reproducer (gating test which we used in past a quick verification in our CI)
a) enable screen sharing, set password
b) connect from the shared session from the very same machine -> vinagre localhost:0, fill password

Result; There was a nested sessions shown on the screen so we were able to verify that screen is shared

After rebase: Session is loaded but some click actions are ignored with following messages in journal shown later:
Oct 23 14:15:06 localhost.localdomain org.gnome.Shell.desktop[3547]: libinput error: client bug: timer event2 debounce short: offset negative (-8ms)
Oct 23 14:15:14 localhost.localdomain org.gnome.Shell.desktop[3547]: libinput error: client bug: timer event2 debounce: offset negative (-7ms)
Oct 23 14:15:15 localhost.localdomain org.gnome.Shell.desktop[3547]: libinput error: client bug: timer event2 debounce short: offset negative (-0ms)
Oct 23 14:15:16 localhost.localdomain org.gnome.Shell.desktop[3547]: libinput error: client bug: timer event2 debounce short: offset negative (-10ms)
Oct 23 14:15:18 localhost.localdomain org.gnome.Shell.desktop[3547]: libinput error: client bug: timer event2 debounce short: offset negative (-5ms)


I know that this is not a very good use case but it was working quite good in the previous version of pipewire (pipewire-0.2.5-1.el)
we were able to control the session and for a while than close the connection without the problems. After update, it is very hard to close the nested mess and it takes a while to force the event to close the remote viewer. Not to mention that if I kill the vinagre sometimes I completely loose the input for the session and I have to restart the gdm to bring it back.

Question:

Opinion on these errors from Peter Hutterer
"""
in short: mutter doesn't call libinput_dispatch() quickly enough because
it's stuck doing something else. There's some more info here:
https://wayland.freedesktop.org/libinput/doc/latest/faqs.html#what-causes-the-timer-offset-negative-warning

There isn't anything we can fix in libinput though because we rely on
the caller to provide the mainloop and in this case it's too slow.

Cheers,
   Peter
"""

2.Reproducer
Enabling sharing, connection from the different machine

Result: Connection is made, but the screen is black for as long as 60 seconds before it is shown to the user, the problem here is, remote-viewer screen is black, until I randomly do one of the following:
a) keep clicking on a blank black screen in vinagre
b) I click or press a key on a machine I am connected to I am getting the screen instantly after pressing the key

Sometimes I have to do just one of the above cases, sometimes I have to do both to get it working

3. Problem How long should password be saved ? Most of the time the password option in control-center only lasts for 1 connection,
then it clears the password and leave the form blank until it is updated by the user again. Sometimes it resets itself to:
"New connections must ask for access", it looks very inconsistent to me, I would expect that the remote access is configured once and worked until it
is turned off.