Ticket #427 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

Doesnt shutdown or restart, when an activity shows `all changes will be lost` error message

Reported by: HoboPrimate Owned by: alsroot
Priority: High Milestone: 0.86
Component: Sugar on a Stick (SoaS) Version: 0.84.x
Severity: Critical Keywords: r+
Cc: Distribution/OS: Unspecified
Bug Status: New

Description

When I go and choose to Restart or Shutdown Sugar, I am switched to a Browse instance, with the error message saying that all changes will be lost, stop anyway or not. Whatever choice you make does not continue the shutdown/restart operation.

Attachments

sugar-427.patch Download (1.4 KB) - added by alsroot 4 years ago.

Change History

Changed 4 years ago by tomeu

  • priority changed from Unspecified by Maintainer to High
  • status_field changed from Unconfimed to Assigned
  • severity changed from Unspecified to Critical
  • version changed from Unspecified to Git as of bugdate
  • milestone changed from Unspecified by Release Team to 0.84

Changed 4 years ago by erikos

  • owner changed from marcopg to erikos
  • status changed from new to assigned
  • status_field changed from Assigned to Needinfo

Can you give some steps to reproduce this bug? What Image are you using? I use latest Soas to reproduce it.

Changed 4 years ago by tomeu

  • severity changed from Critical to Blocker

Changed 4 years ago by erikos

See as well #246

Changed 4 years ago by homunq

  • keywords sugar-love added

Changed 4 years ago by erikos

  • milestone changed from 0.84 to 0.86

Still present - let's move it.

Changed 4 years ago by erikos

  • keywords sugar-love, 0.84 added; sugar-love removed
  • version changed from Git as of bugdate to 0.84.x

Changed 4 years ago by gregorio

Hi Guys,

Just touching this one since I read it. Does someone still need info to reproduce this?

I can't tell from the bug if this always happens or exactly what steps are needed to reproduce.

Looks like Erikos has the last open question...\

If it can't be reproduce maybe it should be retired. With severity blocker it probably needs a final word of one kind or another.

Thanks,

Greg S

Changed 4 years ago by HoboPrimate

Have been using intensively sugar-jhbuild and haven't come across a situation where an activity gives out the error that 'all changes will be lost' so if you want you may close this bug, and if it appears to me again I'll file a more detailed bug.

Changed 4 years ago by tomeu

  • status_field changed from Needinfo to New

I think this should be kept open, it's easy to reproduce by hacking an activity to always fail when saving. Removing Needinfo because this one is just waiting for a developer to have time to look at it.

Changed 4 years ago by erikos

  • keywords sugar-love, 0.84 removed
  • severity changed from Blocker to Critical

Serious, but can go into 0.86.1 as well.

Changed 4 years ago by alsroot

Changed 4 years ago by alsroot

  • keywords r? added

The problem was triggered when activity raises exceptions in write_file() function and sugar stop quit procedure despite of answer to error alert.

Changed 4 years ago by tomeu

  • keywords r+ added; r? removed
  • owner changed from erikos to alsroot

Changed 4 years ago by alsroot

  • status changed from assigned to closed
  • resolution set to fixed

looks like I pushed patch with #1423 commit
 http://git.sugarlabs.org/projects/sugar-toolkit/repos/mainline/commits/8f52b0a8f4a0c8381dd23435eb73d640a698d07f

Changed 3 years ago by sascha_silbe

  • distribution changed from SoaS to Unspecified
  • component changed from sugar to SoaS

Bulk change distribution=SoaS -> component=SoaS

Note: See TracTickets for help on using tickets.