Bug 38308

Summary:	Authentication.TLSCertificate stay around after connection disappear
Product:	Telepathy	Reporter:	Guillaume Desmottes <guillaume.desmottes>
Component:	gabble	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Guillaume Desmottes 2011-06-14 09:29:09 UTC

- 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.

Comment 1 Will Thompson 2011-11-01 09:48:11 UTC

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?
> 
> Yes.

Comment 2 Guillaume Desmottes 2011-11-02 01:14:15 UTC

You're right, the object disappears from the bus but invalidated isn't fired.

Comment 3 GitLab Migration User 2019-12-03 19:52:37 UTC

-- 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.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.