Florian Müllner 593f659a73 parentalControlsManager: Don't log error when disabled ... We currently special-case the DISABLED error when initializing filtering, but not on app filter changes. While it seems reasonable that Malcontent.Manager wouldn't emit the signal while disabled, that's not actually true: It is emitted when any user account information tracked by AccountsServices changes. Even if the signal were limited to changes of the ParentalControls extension, it would still get emitted when app filtering *becomes* disabled. So regardless of potential improvements in libmalcontent itself, we should filter out the DISABLED consistently, both when creating the initial filter and when updating it. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6749 Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2796>		2023-06-09 16:37:36 +02:00
..
dbusServices	screencastService: Fix 'pipeline' option	2023-05-30 22:21:12 +00:00
gdm
misc	parentalControlsManager: Don't log error when disabled	2023-06-09 16:37:36 +02:00
perf	init: Move Meta main loop into JavaScript after GJS context is initialized	2023-06-07 19:23:27 +00:00
portalHelper	portalHelper: Use libadwaita instead of plain Gtk4	2023-04-25 10:45:19 +00:00
ui	magnifier: Fix cursor offset	2023-06-07 22:52:27 +02:00
js-resources.gresource.xml	tests/perf: Add test for shutdown with open window	2023-04-20 14:49:38 +02:00
meson.build
portal-resources.gresource.xml