Bug 33481

Summary:	tp-ring: assert when closing text channels
Product:	Telepathy	Reporter:	Kai Vehmanen <kai.vehmanen>
Component:	ring	Assignee:	Kai Vehmanen <kai.vehmanen>
Status:	RESOLVED FIXED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	minor
Priority:	medium
Version:	git master
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Kai Vehmanen 2011-01-25 08:58:15 UTC

When closing text channels, the following assert is emitted:

(telepathy-ring:16807): Ring-DEBUG: ring_text_channel_receive_deliver: message mixin received with id=0
(telepathy-ring:16807): Ring-DEBUG: on_text_channel_closed: : /org/freedesktop/Telepathy/Connection/ring/tel/ring/text4 is destroyed
process 16807: arguments to dbus_connection_unregister_object_path() were incorrect, assertion "path != NULL" failed in file dbus-connection.c line 5607.
This is normally a bug in some application using the D-Bus library.

Comment 1 Kai Vehmanen 2011-01-25 08:59:14 UTC

Setting myself as default assignee, but keeping as new.

Comment 2 Kai Vehmanen 2011-01-26 02:58:48 UTC

Taking the bug.

Comment 3 Kai Vehmanen 2011-01-26 03:39:30 UTC

Hmm, it seems this is actually regression added to 2.1.2 with commits:
- ring-text-manager: channels hash disposes channels
- ring-media-manager: channels hash disposes channels

Comment 4 Kai Vehmanen 2011-01-26 05:19:56 UTC

Hmm, this seems to be an issue with interacting with tp-glib base-channel.c. The destroyed() logic is not prepared for the case that the closed-callback handler will call g_run_dispose() (like tpring 2.1.2 now does).

My bugfix as a pull req to tp-ring:
http://meego.gitorious.org/meego-cellular/telepathy-ring/merge_requests/10

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.