5f223e0bd8
Otherwise the session could outlive the dialogue, emit a subsequent signal, and its callback would reference finalised objects/widgets from the dialogue. The PolkitSession object is implemented by libpolkit-gobject, so we have no guarantees about its reference counting — the session object could keep itself alive in another thread, or be a singleton. In all likelihood, the session hangs around for longer than the dialogue due to differences in when the two objects are garbage collected. This can be triggered by running `pkexec true` from a gnome-terminal window, then calling `pkill pkexec` from another terminal (on a different VT or via SSH). This causes the dialogue to be cancelled by polkitd. Signed-off-by: Philip Withnall <withnall@endlessm.com> https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/357 |
||
---|---|---|
.. | ||
__init__.js | ||
automountManager.js | ||
autorunManager.js | ||
keyring.js | ||
networkAgent.js | ||
polkitAgent.js | ||
telepathyClient.js |