Sebastian Keller 54ee728aa0 signalTracker: Don't try to create a new SignalTracker for disconnecting ... After the next commit, when some classes, such as PopupMenuManager try to disconnect via a destroy handler, the SignalTracker might have already been destroyed, so trying to get it from the SignalManager will cause it to create a new one, which will then try to connect to the destroy signal of the already destroyed object. This could for example be triggered by changing backgrounds. Fix this by not doing anything in disconnectObject if there is no SignalTracker for that object. Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2466>		2022-09-03 15:11:46 +00:00
..
dbusServices	cleanup: Use deepUnpack() intead of deep_unpack()	2022-08-10 10:29:24 +00:00
gdm	cleanup: Use deepUnpack() intead of deep_unpack()	2022-08-10 10:29:24 +00:00
misc	signalTracker: Don't try to create a new SignalTracker for disconnecting	2022-09-03 15:11:46 +00:00
perf	cleanup: Use new indentation style for object literals	2022-02-23 12:23:52 +00:00
portalHelper	portalHelper: Switch to soup3-based WebKitGTK	2022-06-21 19:29:02 +00:00
ui	status/bluetooth: Indicate progress on toggle	2022-09-03 15:05:57 +00: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	dbusServices: Refactor service utilities from fileUtils into dbusUtils	2022-07-05 03:41:41 -04:00