Opened 9 years ago

Last modified 20 months ago

#8533 new defect

8.2-760 olpc-update from 656 uninstalls core Activities, doubles sessions in Journal when reinstalled

Reported by: mchua Owned by: tomeu
Priority: high Milestone:
Component: journal-activity Version: not specified
Keywords: relnote cjbfor9.1.0 Cc: joe, mstone, kimquirk, marco, tomeu, cscott
Blocked By: Blocking:
Deployments affected: Action Needed: never set
Verified: no


Two strange things occurred while running the data integrity test (to see if pre-upgrade Activity sessions are still usable post-upgrade) for a build 656 to a release-candidate 8.2-760 upgrade.

Immediately after upgrading to 8.2-760 via olpc-update, the core Activities being tested (Browse, Write, TurtleArt, Record, EToys) were found to be no longer present in Sugar (strange thing #1).

Pre-upgrade sessions from these Activities were still in the Journal under their correct names with a generic "file" icon, and attempting to resume them failed (as expected, since the Activity that should be used to open them was not present), with the exception of the Record session, which displayed and was opened as a simple image.

When these Activities were reinstalled (via the Update option in the Control Panel), the Journal still displayed their pre-upgrade sessions with a generic "file" icon. Attempting to resume these pre-upgrade sessions now succeeded, with the correct Activity launching.

After launching the pre-upgrade sessions successfully with the reinstalled Activity, the Journal displayed two sessions for each pre-upgrade session (strange thing #2): one with the generic "file" icon and a timestamp dating to the last time it was resumed before the upgrade, and one with the correct Activity icon and a correct/recent timestamp from the resume that had just been carried out.

Again, the exception here was the pre-upgrade Record session, which still displayed and launched as a simple image. (Record sessions started after Record was reinstalled save/resume in the Journal as Record sessions.)

More investigation is needed to tell whether this is a 656 to 760 olpc-update issue, an Activities updating issue, something that can happen occasionally during upgrades from various builds, or something else. Will try to reproduce.

Attachments (1)

logs.SHF80701855.2008-09-17.18-30-10.tar.bz2 (239.0 KB) - added by mchua 9 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 9 years ago by joe

  • Cc kimquirk added
  • Component changed from not assigned to upgrade utility
  • Keywords 656 760 added
  • Owner set to cscott
  • Priority changed from normal to high

comment:2 Changed 9 years ago by mstone

  • Cc marco tomeu added

comment:3 Changed 9 years ago by cscott

This seems like the expected behavior to me. Didn't 760 prompt you to (re)install your activities on first boot?

comment:4 Changed 9 years ago by cscott

  • Cc cscott added

comment:5 Changed 9 years ago by mchua

The bug isn't that certain Activities didn't install during the upgrade (it did prompt me to reinstall Activities on first boot, but didn't download the core ones on the first pass - it did the second time I ran it).

The bug I think exists (trying to reproduce now) is the doubling of the Journal entries for saved sessions that initially didn't have Activities to open them. After installing the correct Activity and then using that Activity to resume an old pre-update session, I'd expect the resumed session to appear in the Journal once with a timestamp reflecting that it had just been used, instead of twice (once with a pre-update timestamp, once with a timestamp reflecting that it had just been used).

In other words, in your Journal before resuming the Activity...

  • [generic-file-icon] ---- 4 hours ago

In your Journal after resuming the Activity, what *should* happen, imo...

  • [Activity-icon] ---- Now

Instead, what you get...

  • [Activity-icon] ---- Now
  • [generic-file-icon] ---- 4 hours ago

comment:6 Changed 9 years ago by mstone-xmlrpc

  • Keywords relnote added; 656 760 removed
  • Milestone changed from 8.2.0 (was Update.2) to 8.2.1

changed by irc user m_stone:

We're in disagreement about how many people will update to 8.2.0; hence about how significant this bug is. For the time-being, I'm going to argue that we can fix it in 8.2.1 if it becomes a real problem.

comment:7 Changed 9 years ago by mstone-xmlrpc

changed by irc user cjb:

(FWIW, I agree with making this 8.2.1 even while disagreeing about how many people will upgrade.)

comment:8 Changed 9 years ago by cscott

  • Component changed from upgrade utility to journal-activity
  • Owner changed from cscott to tomeu

comment:9 Changed 8 years ago by mstone-xmlrpc

  • Keywords cjbfor9.1.0 added
  • Milestone changed from 8.2.1 to 9.1.0

Pushing out to 9.1.0, per edmcnierney's request.

comment:10 Changed 20 months ago by Quozl

  • Milestone 9.1.0-cancelled deleted

Milestone 9.1.0-cancelled deleted

Note: See TracTickets for help on using tickets.