Bug 36012

Summary:	using ConnectionFactory with Features parameters results on a crash on first-start
Product:	Telepathy	Reporter:	Alvaro Soliverez <alvaro.soliverez>
Component:	tp-qt	Assignee:	Alvaro Soliverez <alvaro.soliverez>
Status:	RESOLVED FIXED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	CC:	ollisal
Version:	git master
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Alvaro Soliverez 2011-04-05 18:01:31 UTC

If we use the Connection with the Features parameters, we get a crash on the first run (when Telepathy is starting and the accounts are still connecting)

Here is the last part of the debug log, prior to the crash:

Debug: tp-qt4 0.5.13.1 DEBUG: Calling Connection::becomeReady() 
Debug: tp-qt4 0.5.13.1 DEBUG: Calling Connection::becomeReady() 
Debug: tp-qt4 0.5.13.1 DEBUG: Channel has 1 optional interfaces: ("org.freedesktop.Telepathy.Channel.Interface.Group") 
Debug: tp-qt4 0.5.13.1 DEBUG: Have initiator handle: no 
Debug: tp-qt4 0.5.13.1 DEBUG: Introspecting Channel.Interface.Group for "/org/freedesktop/Telepathy/Connection/haze/yahoo/marianmar/ContactListChannel/List/subscribe" 
Debug: tp-qt4 0.5.13.1 DEBUG: Calling Properties::GetAll(Channel.Interface.Group) 
Debug: tp-qt4 0.5.13.1 DEBUG: Channel has 1 optional interfaces: ("org.freedesktop.Telepathy.Channel.Interface.Group") 
Debug: tp-qt4 0.5.13.1 DEBUG: Have initiator handle: no 
Debug: tp-qt4 0.5.13.1 DEBUG: Introspecting Channel.Interface.Group for "/org/freedesktop/Telepathy/Connection/haze/yahoo/marianmar/ContactListChannel/List/publish" 
Debug: tp-qt4 0.5.13.1 DEBUG: Calling Properties::GetAll(Channel.Interface.Group) 
Debug: tp-qt4 0.5.13.1 DEBUG: Got reply to Properties::GetAll(Channel.Interface.Group) 
Debug: tp-qt4 0.5.13.1 DEBUG:  Found properties specified in 0.17.6 
Debug: tp-qt4 0.5.13.1 DEBUG: Request for attributes for 59 contacts 
Debug: tp-qt4 0.5.13.1 DEBUG: Introspection done before contacts done - contacts sets ready 
Debug: tp-qt4 0.5.13.1 DEBUG: Got reply to Properties::GetAll(Channel.Interface.Group) 
Debug: tp-qt4 0.5.13.1 DEBUG:  Found properties specified in 0.17.6 
Debug: tp-qt4 0.5.13.1 DEBUG: Introspection done before contacts done - contacts sets ready 
Debug: tp-qt4 0.5.13.1 DEBUG: Entering Chan::Priv::updateContacts() with 1 contacts 
Debug: tp-qt4 0.5.13.1 DEBUG: Both the MCD and the introspect queue empty for the first time. Ready! 
Debug: tp-qt4 0.5.13.1 DEBUG: Both the IS and the MCD queue empty for the first time. Ready. 
Debug: tp-qt4 0.5.13.1 DEBUG: Channel fully ready 
Debug: tp-qt4 0.5.13.1 DEBUG:  Channel type "org.freedesktop.Telepathy.Channel.Type.ContactList" 
Debug: tp-qt4 0.5.13.1 DEBUG:  Target handle 2 
Debug: tp-qt4 0.5.13.1 DEBUG:  Target handle type 3 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: flags 2048 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: Number of handle owner mappings 0 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: Number of current members 0 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: Number of local pending members 0 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: Number of remote pending members 0 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: Self handle 1 tracked: yes 
Debug: tp-qt4 0.5.13.1 DEBUG: ReadinessHelper::setIntrospectCompleted: feature: QPair("Tp::Channel",0) - success: true 
Debug: tp-qt4 0.5.13.1 DEBUG: Account::updateProperties: changed: 
Debug: tp-qt4 0.5.13.1 DEBUG:  Current Presence: 2 - "available" 
Debug: tp-qt4 0.5.13.1 DEBUG: Building self contact 
Warning: tp-qt4 0.5.13.1 WARN: ConnectionLowlevel::contactAttributeInterfaces() used with status 1 != ConnectionStatusConnected 
Debug: tp-qt4 0.5.13.1 DEBUG: 6 contact features supported using Tp::ContactManager(0x870c6d0) 
Debug: tp-qt4 0.5.13.1 DEBUG: Request for attributes for 1 contacts 
Warning: tp-qt4 0.5.13.1 WARN: ConnectionLowlevel::contactAttributes() used with status 1 != ConnectionStatusConnected 
Debug: tp-qt4 0.5.13.1 DEBUG: Building self contact: connected 
Debug: tp-qt4 0.5.13.1 DEBUG: PendingAttrs error "org.freedesktop.Telepathy.Error.NotAvailable" message "The connection isn't Connected" 
Debug: tp-qt4 0.5.13.1 DEBUG: Entering Chan::Priv::updateContacts() with 60 contacts 
Debug: tp-qt4 0.5.13.1 DEBUG: Both the MCD and the introspect queue empty for the first time. Ready! 
Debug: tp-qt4 0.5.13.1 DEBUG: Both the IS and the MCD queue empty for the first time. Ready. 
Debug: tp-qt4 0.5.13.1 DEBUG: Channel fully ready 
Debug: tp-qt4 0.5.13.1 DEBUG:  Channel type "org.freedesktop.Telepathy.Channel.Type.ContactList" 
Debug: tp-qt4 0.5.13.1 DEBUG:  Target handle 1 
Debug: tp-qt4 0.5.13.1 DEBUG:  Target handle type 3 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: flags 2055 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: Number of handle owner mappings 0 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: Number of current members 59 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: Number of local pending members 0 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: Number of remote pending members 0 
Debug: tp-qt4 0.5.13.1 DEBUG:  Group: Self handle 1 tracked: yes 
Debug: tp-qt4 0.5.13.1 DEBUG: ReadinessHelper::setIntrospectCompleted: feature: QPair("Tp::Channel",0) - success: true 
Warning: tp-qt4 0.5.13.1 WARN: Getting self contact failed with "org.freedesktop.Telepathy.Error.NotAvailable":"The connection isn't Connected"
Debug: tp-qt4 0.5.13.1 DEBUG: ReadinessHelper::setIntrospectCompleted: feature: QPair("Tp::Connection",1) - success: false 
Fatal: ASSERT: "pendingFeatures.contains(feature)" in file /root/repo/telepathy-qt4/TelepathyQt4/readiness-helper.cpp, line 243
Aborted

Comment 1 Olli Salli 2011-04-08 07:25:31 UTC

Worrying indeed. Probably due to the recent changes which enable Connections to become ready when still in the Connecting state.

Comment 2 Olli Salli 2011-04-11 10:16:52 UTC

I just merged loads of Connection and general introspection improvements to master. Could you please test again with those, or with the 0.5.15 release once that is out?

Comment 3 Olli Salli 2011-04-29 08:58:53 UTC

I fixed this properly in master a few days ago. Fix will be released in 0.5.16.

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.