Opened 10 years ago
Closed 10 years ago
#4430 closed defect (fixed)
AP name connected to when connecting the first time is "No Wireless Connection".
Reported by: | greenfeld | Owned by: | erikos |
---|---|---|---|
Priority: | Unspecified by Maintainer | Milestone: | Unspecified |
Component: | Sugar | Version: | 0.98.x |
Severity: | Unspecified | Keywords: | r+ |
Cc: | manuq | Distribution/OS: | OLPC |
Bug Status: | Unconfirmed |
Description (last modified by greenfeld)
- Connect to an open AP you never connected to before in OLPC 13.1.0 os30.
- Look at the network icon in frame after a few seconds. The connection information will show the IP address and channel, but will show "No Wireless Connection" instead of the SSID and may also not color the icon.
- Disconnect and reconnect to the AP. The name of the SSID for the network and the proper color for it in Sugar are now shown.
This may be related/identical to #4188 .
Attachments (1)
Change History (6)
comment:1 Changed 10 years ago by greenfeld
- Description modified (diff)
- Summary changed from AP name connected to when connecting the first time is "not connected". to AP name connected to when connecting the first time is "No Wireless Connection".
comment:2 Changed 10 years ago by dsd
Changed 10 years ago by erikos
Frame, Wireless Device icon: make sure the Ssid is displayed in the connected state
comment:3 Changed 10 years ago by erikos
- Cc manuq added
- Keywords r? added
In the connection status code we left out a few states of the connecting phase and therefore ended in the disconnected code path for those, hence giving false user feedback about the current state.
comment:4 Changed 10 years ago by manuq
- Keywords r+ added; r? removed
I have applied both patches, the one attached here and the one at #4188 in Sugar from git compiled in the XO with latest build, os30 .
The testcases succeed, I can't reach an inconsistent state of the icon or palette. Please push.
comment:5 Changed 10 years ago by erikos
- Resolution set to fixed
- Status changed from new to closed
master: e047cb093c76b83b0c94a05a97da7b377fa13425 0.98: c1cba44320b84f2e92576d67d6c9122e7b62e335
Any errors in the logs when this happens?