Opened 13 years ago

Closed 12 years ago

#2515 closed defect (obsolete)

Mesh network not showing in Neighborhood view-INDIA-Hyderabad

Reported by: KMRF Owned by: alsroot
Priority: Immediate Milestone: Unspecified
Component: Sugar Version: 0.82.x
Severity: Unspecified Keywords:
Cc: kmrfoundation@…, alsroot Distribution/OS: OLPC
Bug Status: New

Description

Hi!

Instead after Installing two times new Image in XO machine
Build: 802
Sugar: 0.82.1
firmware:Q2E41

  1. Mess Networks in Neighborhood is not showing
  2. circle icon specified connect to INternert is too not showing

looking for improvement in situation

My self Donthu from INDIA-Hyderabad working for Non Profitable Organization named "KMR Foundation" (more details pls Visit ​http://www.kmrfoundation.org/). 30 XO's Funded by KMRF, Programme implemented from past 10 months with government school children, acquired hands on experience on XO.

Smiley
Donthu

Change History (3)

comment:1 Changed 13 years ago by alsroot

  • Component changed from 0sugar to untriaged

I've changed Component to "untriaged" since "0sugar" is about ​http://wiki.sugarlabs.org/go/Platform_Team/Doers_environment.

KMRF: As far as I know 802 is too outdated, recent one is 825. You can get info about it on ​http://wiki.laptop.org/go/Release_notes/10.1.2#XO-1.

Also if you are using images from OLPC, you may consider posting bugs to OLPC bugs tracker at first (OLPC is more aware about their images related issues) on ​http://wiki.laptop.org/go/Reporting_bugs. The relations between SugarLabs and OLPC is, people within SugarLabs create sugar itself, OLPC gather all sugar related software and prepare it to be runned on your XO.

maybe for

comment:2 Changed 13 years ago by alsroot

  • Cc alsroot added

comment:3 Changed 12 years ago by sascha_silbe

  • Component changed from untriaged to sugar
  • Resolution set to obsolete
  • Status changed from new to closed

Sugar 0.82 isn't supported anymore. Feel free to reopen if the issue persists in a recent version of Sugar.
The most likely cause for this is deactivating the wireless device from the Network Control Panel (My Settings → Network → Radio).

Note: See TracTickets for help on using tickets.