Bug 26527 - gabble unexpectedly closing d-bus muc tubes
Summary: gabble unexpectedly closing d-bus muc tubes
Status: NEW
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: 0.8
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-11 06:57 UTC by Philippe Normand
Modified: 2010-02-12 09:08 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Normand 2010-02-11 06:57:45 UTC
On the Maemo5 SDK, 2 clients in the room, each accepting/offering d-bus tubes, when one client accepts the tube, it gets closed and my app tries to connect to an invalid dbus-gabble unix socket file.

The other client uses gabble 0.8.7-1ubuntu1 on ubuntu karmic.

The log is there:
http://base-art.net/static/gabble.bz2 

You can grep for the tube 612614435 for instance.
Comment 1 Guillaume Desmottes 2010-02-12 05:26:56 UTC
404 when trying to download the logs :\
Comment 2 Philippe Normand 2010-02-12 05:32:53 UTC
(In reply to comment #1)
> 404 when trying to download the logs :\
> 

Sorry it is http://base-art.net/static/gabble.log.bz2 
Comment 3 Guillaume Desmottes 2010-02-12 09:08:14 UTC
Here are my partial observations from this log:

- You joined mirabeau@conference.jabber.org
- You created a tube T1 (1571899144) using the bytestream 1265898273-2625381383
- You created another tube T2 (1573115257) using the bytestream 1265898273-4088574537
- You created a third tube T3 (2143994341) using the bytestream 1265898273-1159475516
- Your app connected to these 3 D-Bus tubes

- "Coherence At Phil's" joins T2
- then T1
- then T3
- then created a new tube T4 1502302501 using 1265898368-3092784896

- You joined tube T4 and connect to it

- "Coherence At Phil's" created a new tube (T5) 1846207483 using 1265898368-3669707655
- You joined T5 and connect to it

- "Coherence At Phil's" created a new tube (T6) 612614435 using 1265898368-729463036
- You joined T6, connect to it and send one message to it

- You received one message on T3
- You sent one (big) message on T3

- A bit later mirabeau@conference.jabber.org/Coherence At Phil's left the room
- T4's bytestream is removed by Gabble and so T4 is closed.
- So is T5
- and T6

- "Coherence At Phil's" rejoins the room with his tubes (T2, T5, T1, T3, T6)

I stopped at this point. I'll check the code but it seens weird to my that T4 is closed because its initiator left. That shouldn't happen.


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.