Bug 19977

Summary: Crash in main at stream-engine-main.c:335
Product: Telepathy Reporter: Connor Imes <connor.k.imes>
Component: stream-engineAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED WONTFIX QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: critical    
Priority: high CC: ernstp
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Connor Imes 2009-02-05 17:14:12 UTC 
There are two separate bug reports with different backtraces filed for Ubuntu Jaunty (development) on Launchpad, both of which start their crash at 
stream-engine-main.c:335
One was on i686, other was on x86_64

https://launchpad.net/bugs/322368
Backtrace: http://launchpadlibrarian.net/21723726/ThreadStacktrace.txt
"Tried calling someone using Empathy and Google Talk. I expected to be able to have a voice and video chat with other participant (who is using the Google Talk on Windows with the Gmail interface). What actually happened was that telepathy-stream-engine reported that it had crashed and the call did not go through."

https://launchpad.net/bugs/325903
Backtrace: http://launchpadlibrarian.net/22022825/ThreadStacktrace.txt
"Trying to start a voice/video conversation with someone."


Because of the multiple crashes I set High priority on this bug, please forgive me if I was wrong to do so.  I have linked to the backtraces, but if you need them attached here, just let me know.  If further information is required on either bug report, please post on the Launchpad report if possible so that the original reporter(s) can see your questions/responses.  Thank you.
Comment 1 Ernst Sjöstrand 2009-03-04 13:22:33 UTC 
This bug: https://bugs.launchpad.net/ubuntu/+source/telepathy-stream-engine/+bug/333032
got telepathy-stream-engine crashed with signal 5 in g_object_ref()
Both that guy and me on AMD64. Is it the same?
Comment 2 Olivier Crête 2009-03-04 13:27:42 UTC 
Stream-engine is no longer used in empathy 2.26.

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.