14968 – mission-control crash on incoming/outgoing SIP calls

Bug 14968 - mission-control crash on incoming/outgoing SIP calls

Summary: mission-control crash on incoming/outgoing SIP calls

Status:	RESOLVED NOTOURBUG

Alias:	None

Product:	Telepathy
Classification:	Unclassified
Component:	general (show other bugs)
Version:	unspecified
Hardware:	Other All

Importance:	medium major
Assignee:	Telepathy bugs list
QA Contact:	Telepathy bugs list

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2008-03-12 05:15 UTC by Jan Oravec
Modified:	2008-03-12 05:42 UTC (History)
CC List:	0 users

See Also:
i915 platform:
i915 features:

Attachments
Crash on initiating call. (9.46 KB, application/octet-stream) 2008-03-12 05:15 UTC, Jan Oravec	Details
Crash on incoming SIP call. (2.54 KB, application/octet-stream) 2008-03-12 05:16 UTC, Jan Oravec	Details
View All

Description Jan Oravec 2008-03-12 05:15:38 UTC

Created attachment 15062 [details]
Crash on initiating call.

I am using these package versions:

empathy-0.22.0
telepathy-mission-control-4.63
libtelepathy-0.3.3
telepathy-glib-0.7.5
sofia-sip-1.12.8
telepathy-sofiasip-0.5.5
farsight-0.1.25
gst-plugins-farsight-0.12.6
telepathy-stream-engine-0.4.0

When I try to use empathy to initiate SIP call, mission-control crashes (strace attachment foo.7764). When someone tries to call me, sofia-sip responds with RINGING and mission-control crashes (attachment foo.15367).

Also, I have never seen stream-engine running.

Comment 1 Jan Oravec 2008-03-12 05:16:11 UTC

Created attachment 15063 [details]
Crash on incoming SIP call.

Comment 2 Simon McVittie 2008-03-12 05:42:54 UTC

Mission Control is a third-party project on Sourceforge. I've filed a bug there:

http://sourceforge.net/tracker/index.php?func=detail&atid=932444&aid=1912653&group_id=190214

Please reopen this bug and assign to an appropriate component if it turns out to be partly our fault (MC should not crash regardless of what any other process does, though).

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.