Florian Müllner e2f6a1980d automountManager: Explicitly track active operations ... As a mount operation's UI may be reused (for example after mistyping the password), we only close the operation once the mount has finished (successfully or with error). We therefore need to track ongoing operations, which we currently do by monkey-patching the corresponding volume object. However while the underlying GVolume object indeed remains the same through-out the operation, the JS wrapper object isn't referenced anywhere and may thus be garbage collected, resulting in a stuck dialog. Fix this issue by tracking active operations explicitly, so that all involved objects are referenced until the end of the operation. https://gitlab.gnome.org/GNOME/gnome-shell/issues/565		2018-10-08 13:18:53 +00:00
..
__init__.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
automountManager.js	automountManager: Explicitly track active operations	2018-10-08 13:18:53 +00:00
autorunManager.js	dbus: Move all interface descriptions into the resource	2018-09-17 07:34:49 +00:00
keyring.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
networkAgent.js	networkAgent: Ask for wifi secrets in the hints paremeter	2018-09-26 00:34:22 +00:00
polkitAgent.js	polkitAgent: Guard against repeated close() calls	2018-04-21 18:42:15 +02:00
telepathyClient.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00