Summary: | gabble crashes when trying to make a call | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Olivier Crête <olivier.crete> |
Component: | gabble | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | critical | ||
Priority: | medium | CC: | freedesktop-bugs |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Olivier Crête
2008-12-29 13:45:53 UTC
This is a bug in gabble jingle session handling code. The bug is triggered by Tp client removing one of the streams while the call was being established. On stream removal by the client, Gabble marked the streams as removed and signalled the peer, but in the meantime it got session-accept by the peer which included the zombie stream. Instead of ignoring it, gabble resurrected the stream and crashed shortly after. Fix merged to git, will be in the next gabble release. (In reply to comment #1) > the call was being established. On stream removal by the client, > Gabble marked the streams as removed and signalled the peer, but Ooops, my error, this is a different crash in jingle code. This crash was caused by having wrong signature for "new-content" signal. Fix for this is also already merged in git master and will be included in the next release. Fixed in 0.7.19. |
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.