ebe1a4d303
If an interface has any signals, we don't want to auto-shutdown while a caller is still connected to a signal. Unfortunately we can't tell whether there are any signal connections, so we track all callers instead, and keep the service alive while any of them is still on the bus. For services that we call from gnome-shell itself - like screencasts or extensions - this has the unintended side effect of effectively disabling auto-shutdown. Address this by exempting the org.gnome.Shell name from sender tracking. Services that we expect to keep running for the lifetime of the shell already disable auto-shutdown, so the only downside is a small startup delay to resolve the well-known shell name. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7250 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3052> |
||
|---|---|---|
| .. | ||
| extensions | ||
| notifications | ||
| screencast | ||
| screensaver | ||
| dbus-service.in | ||
| dbus-service.service.in | ||
| dbusService.js | ||
| meson.build | ||
| org.gnome.ScreenSaver.src.gresource.xml | ||
| org.gnome.Shell.Extensions.src.gresource.xml | ||
| org.gnome.Shell.Notifications.src.gresource.xml | ||
| org.gnome.Shell.Screencast.src.gresource.xml | ||