No collaboration seen

[Saumya-Mishra9129]

Tested on 2 VMs with Sugar Live Build. After joining to a friend , activity doesn't share state with other one. It can caused by incomplete port or not tested collaboration properly in #25

[shaansubbaiah]

@Saumya-Mishra9129 Does the collaboration work in other activities in the 2 VM's you were testing?

Have also been testing collaboration recently, had some questions, did you clone the first VM or install sugar twice? I have tried cloning the first VM but have had issues during collaboration between 2 users.

[Saumya-Mishra9129]

@Saumya-Mishra9129 Does the collaboration work in other activities in the 2 VM's you were testing?

Have also been testing collaboration recently, had some questions, did you clone the first VM or install sugar twice? I have tried cloning the first VM but have had issues during collaboration between 2 users.

I tested with 2 VMs and with Live build of sugar, I am testing all the fructose activities, I have done with chat , pippy and write. Chat and pippy works fine. Just chat activities take some extra time in connecting. Also I have done with one clone and one without clone sugar, there also I found same issues.
What Activities you tested?

[shaansubbaiah]

I'm also trying the fructose activities. Using clones temporarily due to connection issues. Tried the Write, Chat and Calculator activities.

No successful results. Was not even able to add the other user as a friend.

If this did not happen to you while trying with a clone, it has to be an issue in the Debian packages, might be worth opening separately.

[Saumya-Mishra9129]

I'm also trying the fructose activities. Using clones temporarily due to connection issues. Tried the Write, Chat and Calculator activities.

No successful results. Was not even able to add the other user as a friend.

If this did not happen to you while trying with a clone, it has to be an issue in the Debian packages, might be worth opening separately.

I haven't checked with calculator, but chat works fine. Can you see what errors you get in shell.log while testing chat?

[shaansubbaiah]

Chat works to an extent, gets stuck while attempting to connect to a previously joined shared chat session. Works fine the first time. Nothing in the logs, have to investigate further.

Edit: Collaboration doesn't work on the Write Activity.

[shaansubbaiah]

Also, Nimbus Roman font is set as default when a user joins a public/collaborative Write Activity session. It is seen only in the guest user, not in the shared activity's host.

@Saumya-Mishra9129 can you check if this issue occurs on your setup as well?

I'll open an issue if it is not specific to Debian Buster.

[Saumya-Mishra9129]

@Saumya-Mishra9129 can you check if this issue occurs on your setup as well?

I'll open an issue if it is not specific to Debian Buster.

I am able to reproduce but different fonts are present here. In host it is Sans set by default and in guest user it is Serif.

[shaansubbaiah]

I am able to reproduce but different fonts are present here. In host it is Sans set by default and in guest user it is Serif.

Are you using Sugar Live Build or the Ubuntu packages?

[Saumya-Mishra9129]

I am able to reproduce but different fonts are present here. In host it is Sans set by default and in guest user it is Serif.

Are you using Sugar Live Build or the Ubuntu packages?

I am using packaged sugar with Ubuntu 20.04

[quozl]

Clones will not work. The Sugar user cryptographic key is identical, so the users are not separate. Workaround is to create a different account or delete the account and recreate it again. Correct procedure is to snapshot your VM before logging in to Sugar for the first time, when the key is created.

[quozl]

Please assess if anything is left in this issue after avoiding cloning. Chat activity is our usual activity for testing collaboration briefly; if Chat collaborates, but Write does not in the same circumstance, then that deserves more attention. Write uses AbiWord to collaborate, via the same underlying Telepathy layer.

[shaansubbaiah]

Tested again, without using clones.

Chat activity

• Works fine.

Write activity

• After guest joins the hosts activity, the 'connecting' spinner appears for a few seconds. Text typed is only seen locally, not by the other user. No errors in logs.
• Different font appears in the guest as reported in Default font is different for guest on joining collaboration session. #43

---

Aside, @Saumya-Mishra9129 on packaged Sugar in Ubuntu, do you have any errors when adding and removing another user as a friend?

[quozl]

Thanks. It is not working then. Can anyone else reproduce? What version of AbiWord?

[shaansubbaiah]

Debian 10.4, Sugar 0.117-3:
Write activity v101
gir1.2-abi-3.0 v3.0.2-10

[Saumya-Mishra9129]

Aside, @Saumya-Mishra9129 on packaged Sugar in Ubuntu, do you have any errors when adding and removing another user as a friend?

Yeah I got 3 errors.

• First one when I click on add friend button , Same error as mentioned in TypeError : section names must be strings sugar#921
• Second one when I click on neighbourhood icon in write activity , Same as mentioned in KeyError: 'type' sugar#924
• Third one when I exit after joining a share activity on guest as well as on host.

File "/usr/lib/python3/dist-packages/jarabe/desktop/meshbox.py" , line 409, in _buddy_removed_cb
   self._remove_buddy(buddy_model)
File "/usr/lib/python3/dist-packages/jarabe/desktop/meshbox.py" , line435, in _remove_buddy
   icon = self._buddies[buddy_model.props.key]
KeyError: dbus.ByteArray(b'AAAAB3NzaC1kc3....=' ,variant_level=1)

Thanks. It is not working then. Can anyone else reproduce? What version of AbiWord?

Ubuntu 20.04 - Sugar 0.117, Write activity v101