#7181 NORM Never A: Unusual Chat behavior on joining a chat
Zarro Boogs per Child
bugtracker at laptop.org
Wed Jun 4 16:21:15 EDT 2008
#7181: Unusual Chat behavior on joining a chat
----------------------------+-----------------------------------------------
Reporter: Charlie | Owner: morgs
Type: defect | Status: new
Priority: normal | Milestone: Never Assigned
Component: chat-activity | Version: Build 703
Resolution: | Keywords:
Verified: 0 | Blocking:
Blockedby: |
----------------------------+-----------------------------------------------
Comment(by Charlie):
Replying to [comment:1 morgs]:
> Charlie, for all collaboration-related issues, it's critical that we
know the following details:
>
> * Were you collaborating via simple mesh (no access point), access
point with no jabber server, access point with jabber server, or mesh to a
schoolserver (no access point).
> * Especially, jabber server vs no jabber server. The difference is
whether telepathy-gabble (jabber server) or telepathy-salut (no jabber
server) is being used.
Both laptops were using salut and were on a schoolserver every time I
reproduced the bug, according to olpc-netstatus.
> * Log files. See
http://wiki.laptop.org/go/Attaching_Sugar_Logs_to_Tickets - in particular,
the log file from the relevant activity (org.laptop.Chat-1.log in this
case - or Chat-2 etc if you opened it multiple times) and
presenceservice.log. These should be from the XO that demonstrated the
problem, although we may ask for logs from the other machine too if
necessary.
I'm going to try reproducing the bug and will attach logs that are
generated. (Update: the bug occurred again and I'll be attaching the logs
-- hopefully they came out right.)
> * Activity version number, if the activity isn't installed in the build
(although in this case AFAIK it is in the build and is Chat-35.xo with
cscott's translation patch applied).
>
> That said, joining a shared Chat should show "_____ is here" for each
participant already in the shared activity when you join.
>
> "Charlie-Peru left the chat" indicates that subsequent to joining,
Presence Service detected that that XO had left the shared activity, and
then the next message shows that it joined again. This could be due to
network issues which caused the XO to vanish and reappear.
>
> The cause could be anywhere in the collaboration/presence/network stack,
so if you can reproduce the issue, we would need more log files - the
telepathy log files with LM_DEBUG and/or GIBBER_DEBUG as detailed in
http://wiki.laptop.org/go/Telepathy_debugging.
>
> If you can't reproduce the issue, then that's basically the state of our
collaboration system: strange things happen from time to time, due to
unreliabilities in multiple layers of the system... the problem you are
reporting isn't preventing actual collaboration, and isn't due to Chat
itself but other components of the system.
>
When I originally showed cscott and mstone the bug, I was already aware
that the first message was supposed to display; it was the second two
message that confused me.
> PS If you can't reproduce, please close the ticket, as this report alone
unfortunately isn't enough to take further.
Noted for future reference.
--
Ticket URL: <http://dev.laptop.org/ticket/7181#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list