Ticket #5829 (closed defect: invalid)

Opened 7 years ago

Last modified 6 years ago

Chat Activity displays other users names weird

Reported by: martianpenguin Owned by: Collabora
Priority: high Milestone: 8.2.0 (was Update.2)
Component: presence-service Version: Build 653
Keywords: chat Cc:
Action Needed: Verified: no
Deployments affected: Blocked By:


See screen shot. The user's name is displayed as a hex string when the person joins and then displayed as ??? when they type. It also seems as though the colors are not displayed properly either.

Version info: I think this was version 653, however i was using this file with it:  http://dev.laptop.org/~morgan/chat.py which is supposed to fix the scrolling bug.


xochat1.png Download (68.4 KB) - added by martianpenguin 7 years ago.
screenshot of problem

Change History

Changed 7 years ago by martianpenguin

screenshot of problem

Changed 7 years ago by martianpenguin

I seem to have figured that this bug appears when two people are in a chat, but they can't see each other in the neighborhood. Perhaps the jabber server is overloaded.

Changed 7 years ago by jg

  • priority changed from normal to high
  • milestone changed from Never Assigned to Update.1

Morgan, is this a problem in current joyride?

Changed 7 years ago by morgs

  • cc Collabora added
  • status changed from new to assigned
  • component changed from chat-activity to presence-service

jg, it's an exceptionally rare problem that is hard to duplicate. It was reported by somebody before Trial 2 but we couldn't find a specific cause other than network unreliability causing a D-Bus call to timeout when trying to retrieve buddy properties.

I'll look into it again.

Changed 7 years ago by marco

  • milestone changed from Update.1 to Update.2

From morgs comment, I don't think this is critical for Update.1.

Changed 7 years ago by daf

Another problem where logs would be valuable. :(

Changed 6 years ago by morgs

  • owner changed from morgs to Collabora
  • cc Collabora removed
  • status changed from assigned to new

Changed 6 years ago by marco

  • status changed from new to closed
  • resolution set to invalid

Closing as invalid because it appears that without logs we can't do anything about the problem.

Note: See TracTickets for help on using tickets.