Ticket #6989 (closed defect: fixed)

Opened 8 weeks ago

Last modified 5 weeks ago

Rainbow interferes with launching of Browse

Reported by: mikus Owned by: mstone
Priority: normal Milestone: Never Assigned
Component: security Version: Development build as of this date
Keywords: Cc: mikus@…
Action Needed: Verified: no
Blocked By: Blocking:

Description

G1G1, recent Joyride. Frequently, when I launch Browse, its icon pulses on the Frame for many many seconds, then vanishes.

In these cases (I think I used Browse earlier in the same boot), the Browse log identifies the problem as: 'File exists'. I believe this behavior started when I installed rainbow 0.7.12-1.olpc2.

Attachments

Web.log (5.9 kB) - added by mikus 8 weeks ago.
Browse log - Browse did not launch

Change History

Changed 8 weeks ago by mikus

Browse log - Browse did not launch

Changed 8 weeks ago by tomeu

  • owner changed from jg to mstone
  • component changed from distro to security

Changed 8 weeks ago by mstone

Mikus,

Thanks for filing this ticket with the log attached. Viewing the log with 'less -R' shows that I made false assumptions about the initial conditions of the spool and therefore attempted to create a symlink without checking that it was safe to do so. I'll think for a little bit about the proper way to resolve the issue.

Changed 6 weeks ago by mstone

I've created a sample RPM at http://teach.laptop.org/~mstone/rainbow.rpm that I think might fix this problem. I hope to test it myself in the next couple of days; however, you're welcome to do so before then if you want. The difference from rainbow-0.7.12 is minor, but I believe it will suffice.

Changed 6 weeks ago by erikos

I tested in joyride were I saw this issue before and your fix looks good. I could restart browse another time without restarting rainbow.

Thanks for the fix

Changed 5 weeks ago by mikus

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

The "could not restart Browse" problem appears to have been fixed in rainbow 0.7.13-1.olpc2.

Thanks.

Note: See TracTickets for help on using tickets.