Opened 7 years ago
#4964 new defect
Can't have 2 instances of same activity in collab
| Reported by: | sam | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | Unspecified |
| Component: | Sugar | Version: | Git as of bugdate |
| Severity: | Unspecified | Keywords: | |
| Cc: | Distribution/OS: | Fedora | |
| Bug Status: | Unconfirmed |
Description
Steps to reproduce:
- Open Chat on Alice's computer
- Invite Bob to the chat
- Bob accepts the invitation, sees that Chat activity start and work as expected
- Open a NEW Chat instance on Alice's computer
- Invite Bob to the new chat instance
- Bob accepts the invitation
Expected result: New chat instance works as expected - they now have 2 chat activities
Actual result: New chat instance hangs on startup (stays on the pulsing icon screen).
Why?
Activities are given telepathy client names like "org.freedesktop.Telepathy.Client.org.laptop.Chat". Therefore, when you open 2 chat instances, they are assumed to have the same client name. When Sugar gets an invite, it sends it to "org.freedesktop.Telepathy.Client.org.laptop.Chat", which is actually the first activity.
We need to add something else into the client id (journal object_id?) so that it is universally unique!
Note: See
TracTickets for help on using
tickets.
