mirror of
https://github.com/brl/mutter.git
synced 2024-11-26 01:50:42 -05:00
a2a4067e07
When a stream is destroyed by a consumer, mutter won't be able to recognize that. For mutter, the stream just paused, but did not disconnect, because the connection state of a PipeWire stream only represents, whether the respective PipeWire context is connected to PipeWire. In addition to that, it may be the case, that the stream consumer just recreates the stream. So even if mutter would be able to know, when the stream consumer destroyed a stream, but not the whole screencast or remote-desktop session, then mutter would not know, whether the stream will be resumed eventually or not. So, add an explicit API call to the screencast interface to stop a stream. For virtual streams, this also means, that the respective virtual monitor is destroyed. Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/2889 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3307> |
||
|---|---|---|
| .. | ||
| dbus-interfaces | ||
| 50-mutter-navigation.xml | ||
| 50-mutter-system.xml | ||
| 50-mutter-wayland.xml | ||
| 50-mutter-windows.xml | ||
| 61-mutter.rules | ||
| default_icon.png | ||
| meson.build | ||
| mutter-schemas.convert | ||
| org.gnome.mutter.gschema.xml.in | ||
| org.gnome.mutter.wayland.gschema.xml.in | ||
