Thanks.
Successful tests are also useful because (a) it helps others see how to test,
(b) it helps others see what has been tested. It is difficult to know how much
testing is done based only on problem reports.
Please do continue to report the problems briefly, regardless of if they are
assessed as Debian or Sugar Labs. What I was trying to say is that I won't
work on or investigate the problems based on your reports here, as that would
distract from your reporting, my mentoring, and create two places for technical
discussion; the GitHub issue and the thread here.
On Mon, Jun 15, 2020 at 11:16:12AM +0000, shaansubbaiah.c...@bmsce.ac.in wrote:
> Yes, the testing of Sugar 117-3 on Debian 10.4 Buster/Stable was done to
> establish a baseline. This should help in determining if issues are due to
> Sugar or Debian while testing on Debian 'testing' and 'unstable'. I will
> include the successful tests next time, might take a little longer.
>
> I'll report Debian issues through the mailing list, Sugar issues through
> Github.
> On Monday, June 15, 2020, 6:23:36 AM GMT+5:30, James Cameron
> <qu...@laptop.org>
> wrote:
>
> Thanks.
>
> I'm taking no action here, I'll use the GitHub issues once I get to them later
> today.
>
> I note your project updates almost entirely deal with test faiures. Could you
> please also include a separate section which lists the successful testing and
> how it was performed? This is likely to be much larger, but easier to prepare
> because it can come from your test plan.
>
> Also, you say you tested Sugar 0.117 on Debian 10.4. This is not a
> combination
> available to users of Debian 10.4 (Buster), as it has Sugar 0.112. Please
> remind me why you tested it? I guess to establish a baseline before testing
> Sugar 0.117 on Debian Testing or Debian Unstable. It is easy to miss the
> overall project plan during small updates.
>
> On Sat, Jun 13, 2020 at 02:59:50PM +0000, [1]shaansubbaiah.c...@bmsce.ac.in
> wrote:
> > Hello all,
> > Project update; almost done with testing the fructose set of activities in
> > Sugar 117-3 on Debian 10.4, issues found so far:
> >
> > Debian Related:
> >
> > 1. glib-compile-schemas not found. Due to missing libglib2.0-bin package
> >
> > Sugar Related:
> >
> > 1. Write Activity -> Default font is different for guest on joining
> > collaboration session. [1]#43
> >
> > 2. Sugar 117-3 on Debian - AttributeError: ‘str’ object has no attribute
> > ‘decode’ [2]#923
> >
> > 3. Error set_active() failed: org.freedesktop.DBus.Error.NoReply: Message
> > recipient disconnected from message bus without replying as seen in [3]
> > issue #840 is reproducible on Sugar 117-3, Debian 10.4 by closing any
> > activity.
> >
> > 4. Found on Sugar 117-3, Debian 10.4. (Not reproducible on OLPC OS 18.04):
> >
> > Adding another user as a friend produces the error:
> >
> > Traceback (most recent call last):
> > File "/usr/lib/python3/dist-packages/jarabe/view/buddymenu.py", line
> 205, in _make_friend_cb
> > friends.get_model().make_friend(self._buddy)
> > File "/usr/lib/python3/dist-packages/jarabe/model/friends.py", line
> > 130,
> in make_friend
> > self.save()
> > File "/usr/lib/python3/dist-packages/jarabe/model/friends.py", line
> > 160,
> in save
> > cp.add_section(section)
> > File "/usr/lib/python3.8/configparser.py", line 1207, in add_section
> > self._validate_value_types(section=section)
> > File "/usr/lib/python3.8/configparser.py", line 1180, in
> _validate_value_types
> > raise TypeError("section names must be strings")
> > TypeError: section names must be strings
> >
> > Similar to [4]sugar PR #921
> >
> >
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> > Removing the same user as a friend produces:
> >
> > Traceback (most recent call last):
> > File "/usr/lib/python3/dist-packages/jarabe/desktop/groupbox.py", line
> 67, in _friend_removed_cb
> > icon = self._friends[key]
> > KeyError: "b'AAAAB3NzaC1kc3MAAACBAP1g0TB6F/
> q8LSrX2APaHBJm89b+IocnRJVovwu4pEMVlLmg5fScoXUZ1qi8l04hQOxetyWmc4wYiFMS/
> 2MXmb7PvWT0Mlmx1y9A3Am3y0XP5870uYNgXJ4UgL9lGX6uz3ExsqcG9X5X5wbwIJ1ckQxXnxf2VxwUxBd2p4B
> /tPG1AAAAFQCN1CuSl6JjCOm4RS+nCuI3mIlalwAAAIEA6YEg849ugww7gpmT7aUHl3qetdtl+/
> fkL8BxyYnOeaR2Mcs3phrYQNvm2/ac0HA16TqJOoVatoPpD/Z84IBQxU2wNQilhU9VEwiP/
> +Wrukg3LbU/oyEPnOOJfasR0lgzLL+RR20zLtixer3irlsv2wvZU/
> 9PFbZvuCEzbB3LiC0AAACBAOWzSUShSPWHQGKALTyWTvl481IIxPwizbKmraEeKm3xvqB8dP5Hy2QQlRXZrb1QgMDoARRYxzUoO8
> /
> PKzLSpFYoQvF9v31DtJGkNilNdfRuiJTWZJah3DBYMAiPHU478DH3zcHbRYI4Prkmu00v+smv7qSUhDQrClMF+ka6mJN4'"
> >
> > Somewhat similar to [5]sugar-toolkit-gtk3 issue #433
> >
> >
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> >
> > Edge case; while trying to add the user as a friend using a VM clone.
> > (Not
> > important)
> >
> > Error.NoReply: Message recipient disconnected from message bus without
> replying
> > Traceback (most recent call last):
> > File "/usr/lib/python3/dist-packages/jarabe/view/buddymenu.py", line
> 205, in _make_friend_cb
> > friends.get_model().make_friend(self._buddy)
> > File "/usr/lib/python3/dist-packages/jarabe/model/friends.py", line
> > 126,
> in make_friend
> > buddy = FriendBuddyModel(key=buddy.key, nick=buddy.nick,
> > File "/usr/lib/python3/dist-packages/jarabe/model/friends.py", line 49,
> in __init__
> > self._set_online_buddy(buddy)
> > File "/usr/lib/python3/dist-packages/jarabe/model/friends.py", line 64,
> in _set_online_buddy
> > if buddy.contact_id != self.contact_id:
> > AttributeError: 'OwnerBuddyModel' object has no attribute 'contact_id'
> >
> >
> ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> >
> > Best,
> > Shaan
> >
> >
> >
> > References:
> >
> > [1] [2]https://github.com/sugarlabs/write-activity/issues/43
> > [2] [3]https://github.com/sugarlabs/sugar/issues/923
> > [3] [4]https://github.com/sugarlabs/sugar/issues/840
> > [4] [5]https://github.com/sugarlabs/sugar/pull/921
>
> > [5]
> [6]https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/433
>
> --
> James Cameron
> [7]http://quozl.netrek.org/
>
> References:
>
> [1] mailto:shaansubbaiah.c...@bmsce.ac.in
> [2] https://github.com/sugarlabs/write-activity/issues/43
> [3] https://github.com/sugarlabs/sugar/issues/923
> [4] https://github.com/sugarlabs/sugar/issues/840
> [5] https://github.com/sugarlabs/sugar/pull/921
> [6] https://github.com/sugarlabs/sugar-toolkit-gtk3/issues/433
> [7] http://quozl.netrek.org/
--
James Cameron
http://quozl.netrek.org/
_______________________________________________
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
