Ticket #2588 (closed defect: worksforme)

Opened 7 years ago

Last modified 3 years ago

Sugar fails to start; infinite loop

Reported by: Zack Owned by: ixo
Priority: high Milestone: 9.1.0-cancelled
Component: network manager Version:
Keywords: cjbfor9.1.0 Cc: Zack, gregorio, dsd
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

After rebooting, sugar failed to start (and kept trying to, forever). I passed the laptop to Dan and I do believe he fixed it, but I'm opening this just to keep track.

Change History

Changed 7 years ago by Zack

  • cc Zack added
  • status changed from new to closed
  • resolution set to fixed

Changed 7 years ago by dcbw

Turned out to be a sugar bug in saved network config handling, fixed in sugar commit dbe8a6eeff7e2f42c309ba709038d568246f0853

Changed 7 years ago by kimquirk

  • status changed from closed to reopened
  • resolution deleted
  • milestone changed from Untriaged to Trial-2

Not fixed in 540. What build did this get into? How do I fix it until the appropriate build gets released?

Changed 7 years ago by jg

  • milestone changed from Trial-2 to Trial-3

Has this gotten in a build, Dan?

Changed 7 years ago by jg

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

Changed 6 years ago by ixo

  • status changed from closed to reopened
  • resolution deleted
  • milestone changed from Trial-3 to Retriage, Please!

I had a report of a user having this problem, when XO was auto-updated from 650 to 656. Luckily, they were experienced enough to help track it down part of the way. A file permissional problem in .sugar/default/ directory. (i.e. they can rename the directory, and boots fine).

I can contact the user (was "User" in IRC) for more specific details, if need be.

Changed 6 years ago by gregorio

  • cc gregorio added
  • owner changed from dcbw to ixo
  • next_action set to never set
  • status changed from reopened to new
  • priority changed from blocker to high

Hi Ixo,

Looks like Jim closed this as resolved. Can this be reproduced? I think many XOs were updated this way so let us know if you have exact steps to reproduce it.

Also, if its a problem only with 656 only and not with the latest, we probably have to let it go and say its fixed in the 8.2.0.

Thanks,

Greg S

Changed 5 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.

Changed 3 years ago by dsd

  • cc dsd added
  • status changed from new to closed
  • resolution set to worksforme

Need exact steps to reproduce this as requested above, if still valid.

Note: See TracTickets for help on using tickets.