Opened 14 years ago

Closed 12 years ago

#2277 closed defect (fixed)

Log Collector: Send XO information, fails, server side issue

Reported by: quozl Owned by: wadeb
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: Log Version: Unspecified
Severity: Unspecified Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: New


Log activity has a button that attempts to upload data to which is currently not available.

Attachments (1)

0001-disable-default-server-for-log-submission-2277.patch (2.4 KB) - added by quozl 13 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 Changed 13 years ago by quozl

Server owner does not wish to reinstate the service.

comment:2 Changed 13 years ago by greenfeld

  • Bug Status changed from Unconfirmed to New

Still present in OLPC 11.2.0 os13.

Do we wish to move the handler somewhere, or remove the option?

If the option is kept, legal counsel may want to review the implications of collecting user-specific data from computers, as the laws regarding this in at least a few countries require out-of-band parental approval for children, privacy policies, and/or similar.

comment:3 Changed 13 years ago by quozl

I don't think this is a problem for Sugar Labs, except that the activity does not support a privacy policy that OLPC may want to adopt. OLPC needs to be clearer about the policy it wants, and this can be decided during olpc-os-builder. I've made a patch to the Log activity that:

  • removes the broken service URL from the embedded script,
  • removes the broken service URL from the activity,
  • disables the send information button,
  • provides a mechanism by which olpc-os-builder may configure gconf to restore the send information button and specify a service URL.

Log-24 is in OLPC OS 11.2.0 os13.

comment:4 Changed 13 years ago by quozl

... except my logic is entirely wrong, but I'm sure a Log developer will get the idea. ;-)

comment:5 Changed 13 years ago by RafaelOrtiz

Agree with this patch..Simon or Wade? can apply it. I see they have access to the repo.

Also a merge request could be handy.

comment:6 Changed 13 years ago by quozl

I've fixed and split the patch (d8f8d2c and b8030f6), created a personal clone and a merge request against your personal clone.

comment:8 Changed 12 years ago by godiard

  • Resolution set to fixed
  • Status changed from new to closed

Already disabled in version 27

Note: See TracTickets for help on using tickets.