Florian Müllner 199b556b5d 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> (cherry picked from commit 593f659a73)		2023-07-04 18:12:51 +02:00
..
dbusServices	screencastService: Handle case where no videos directory exists	2023-02-13 12:47:14 +01:00
gdm	gdmUtil: Fix SignalTracker leak in ShellUserVerifier	2023-02-13 16:58:11 +01:00
misc	parentalControlsManager: Don't log error when disabled	2023-07-04 18:12:51 +02:00
perf	perf/basic: Toggle quick settings instead of old menu	2022-12-05 23:41:27 +01:00
portalHelper	portalHelper: Switch to soup3-based WebKitGTK	2022-06-21 19:29:02 +00:00
ui	magnifier: Fix cursor offset	2023-07-04 18:12:42 +02:00
js-resources.gresource.xml	status/power: Merge with system indicator	2022-08-03 12:41:05 +00:00
meson.build	extensions-app: Move Extensions app to new subproject	2020-03-27 23:33:30 +00:00
portal-resources.gresource.xml	js/portal-resources: Add missing fileUtils to js path	2022-11-03 18:02:27 +00:00