Opened 10 years ago

Closed 9 years ago

#2115 closed defect (fixed)

Memorize 34 does not share on 8.2.1

Reported by: carrott Owned by: erikos
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: Memorize Version: Unspecified
Severity: Unspecified Keywords:
Cc: humitos Distribution/OS: Unspecified
Bug Status: New

Description

Memorize on build 8.2.1 on XO-1. Access point networking but no school server or internet.

Load a game.
Share with neighbourhood.
Join on second XO.
Second XO loads Memorize, but cards never appear and game doesn't start.

Attachments (3)

org.laptop.Memorize-joiner.log (6.5 KB) - added by carrott 10 years ago.
org.laptop.Memorize-sharer.log (8.2 KB) - added by carrott 10 years ago.
org.laptop.Memorize-34-sharer.log (2.5 KB) - added by garycmartin 10 years ago.
Memorize-34 sharer traceback (build 301, Sugar 0.84.16)

Download all attachments as: .zip

Change History (11)

Changed 10 years ago by carrott

Changed 10 years ago by carrott

comment:1 Changed 10 years ago by carrott

see exception in sharer's log

comment:2 Changed 10 years ago by walter

Not sure of the root cause, but given the errors in the log, it seems v34 is depending on newer Sugar features than are present 0.82. It should be marked as 0.84-0.88 in ASLO so that people running older versions of Sugar will not be tempted to download it.

comment:3 Changed 10 years ago by garycmartin

  • Bug Status changed from Unconfirmed to New

Just testing v34 between two XO's using the recent 301 build running Sugar 0.84.16 and the joining laptop shows a blank grey tile area (but sees the other user in the left panel). No tracebacks from the joining user logs, but the original sharing user is getting a DBusException: org.free desktop.DBus.Python.KeyError: Traceback. Will post the full log after this.

Changed 10 years ago by garycmartin

Memorize-34 sharer traceback (build 301, Sugar 0.84.16)

comment:4 Changed 10 years ago by garycmartin

Just tested Memorize-33 between two XO's using the recent 301 build running Sugar 0.84.16. Exact same issue/traceback. Trying back a few more Memorize versions.

comment:5 Changed 10 years ago by garycmartin

OK very strange Memorize-32 fails like this as well. However I've just noticed sharing any of the demos works fine, but if you share a custom created game it fails...

comment:6 Changed 10 years ago by garycmartin

  • Component changed from sugar to Memorize
  • Owner changed from tomeu to erikos

Testing back in Memorize-34 (32-34 all behaved the same, didn't go back further). You can share custom games but there is a specific sequence needed to avoid the bug :( You must:

1) Start a new instance of Memorize
2) While in one of the demo games (the default one is OK too) enable sharing
3) On a second machine, join the shared demo game (after a short pause you should see 'Loading Game...' appear for a moment)
4) Now use the Load game toolbar on the first machine to pull in your custom game content
5) The second machine will update to the custom content

Summary: It appears if some one joins a custom game, their client will fail with a dbus traceback. You can only join demo games successfully, and then load in custom game content. Caveat; all my testing has been in 0.84.16 so far.

comment:7 follow-up: Changed 9 years ago by godiard

Can we close this ticket?

comment:8 in reply to: ↑ 7 Changed 9 years ago by humitos

  • Cc humitos added
  • Resolution set to fixed
  • Status changed from new to closed

Replying to godiard:

Can we close this ticket?

Yes, I'm going to close this ticket.

I'm testing this behavior between one XO 1.75 and another one XO 1.5 both with Maze 41 (os8) and it's working properly.

Note: See TracTickets for help on using tickets.