Ticket #6775 (new defect)

Opened 8 months ago

Last modified 4 months ago

Launching of KuKu fails

Reported by: mikus Owned by: mstone
Priority: normal Milestone:
Component: security Version: Development build as of this date
Keywords: Cc: mstone, tomeu
Action Needed: Verified: no
Deployments affected: Blocked By:
Blocking:

Description

G1G1, using Joyride at approximately version 1806.

[I believe that, just to have a clean slate, I first disabled rainbow (by erasing /etc/olpc-security). ]

Attachments

shell.log (0.9 kB) - added by mikus 8 months ago.
what got logged
kuku.log (13.9 kB) - added by mikus 8 months ago.
what got logged when trying to launch Kuku

Change History

Changed 8 months ago by mikus

what got logged

Changed 8 months ago by mikus

what got logged when trying to launch Kuku

follow-up: ↓ 2   Changed 8 months ago by cjb

Deleting that file doesn't do anything until you reboot, I believe.

Running "olpc-netlog" will get you a tarball with enough logs to debug this; the shell.log alone isn't enough.

in reply to: ↑ 1   Changed 8 months ago by mikus

Replying to cjb:

Deleting that file doesn't do anything until you reboot, I believe.

I no longer remember for sure, but I believe that the sequence I followed was 'rm /etc/olpc-security', then reboot, then *immediately* launch Kuku from the Frame.

Running "olpc-netlog" will get you a tarball with enough logs to debug this; the shell.log alone isn't enough.

It would take me much too long to recreate the situation so that I could run "olpc-netlog".

At the time I looked in the logs subdirectory -- I believe that none of the other logs there would help with this defect.

  Changed 8 months ago by mstone

  • cc mstone, tomeu added
  • owner changed from jg to mstone
  • component changed from distro to security

This is a combination of a bug in Rainbow (inadequate checking of preconditions) and possibly a bug in Kuku. You can read the log file with 'less -R <log>' to get the detailed traceback. Any of me, tomeu, or you can produce a patch to Rainbow that will detect this situation with a clearer error. I recommend trying it yourself or asking tomeu since I'm quite tied up with releasing U.1.

  Changed 4 months ago by gregorio

  • milestone deleted

Milestone Never Assigned deleted

Note: See TracTickets for help on using tickets.