- Get a Gabble account connected
- Try to connect another one having an untrusted certificate
- Empathy display a popup asking if you trust the certificate. DON'T reply
- Disable the account
- Empathy's dialog stay around
That's because the proxy on the TLSCertificate is not invalidated; the D-Bus object is still there.
Does the object really stay on the bus, or is it just that the proxy isn't listening to any signals besides the two on the TLSCertificate interface? The TLSCertificate proxy should presumably become invalidated when its parent channel dies. cf. bug 30460:
> > When a TLSCertificate's Channel (if any) closes, should it be invalidated?
You're right, the object disappears from the bus but invalidated isn't fired.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/158.