Ticket #10347 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

Access Point signal strength update not seperate from state change

Reported by: erikos Owned by: erikos
Priority: normal Milestone: 10.1.3
Component: sugar Version: Development build as of this date
Keywords: Cc:
Action Needed: no action Verified: no
Deployments affected: Blocked By:
Blocking:

Description

Upstream bug: http://bugs.sugarlabs.org/ticket/2246

We do write the AP connection with every signal strength update!

Attachments

0001-Access-Point-signal-strength-update-not-seperate-fro.patch (4.3 kB) - added by erikos 4 years ago.
Separate the strength update from the state update
0001-AP-separate-signal-strength-from-status-10347.patch (5.0 kB) - added by erikos 4 years ago.
Rebased patch

Change History

Changed 4 years ago by erikos

Separate the strength update from the state update

Changed 4 years ago by erikos

  • next_action changed from review to package
  • milestone changed from Not Triaged to 10.1.3

Changed 4 years ago by erikos

Rebased patch

Changed 4 years ago by erikos

|TestCase|

- does connecting to an AP work? - is the signal strength of an AP updated correctly?

Changed 4 years ago by greenfeld

Test RPMs were installed: sugar-0.84.22-2.fc11.i586.rpm sugar-artwork-0.84.2-2.fc11.i586.rpm sugar-presence-service-0.84.1-2.fc11.noarch.rpm sugar-toolkit-0.84.12-2.fc11.i586.rpm

Tested using various 802.11 Access Points. Signal levels, connection status, etc. updated as expected.

Changed 4 years ago by erikos

  • next_action changed from package to test in build

Is available in os350.

Changed 4 years ago by greenfeld

  • status changed from new to closed
  • next_action changed from test in build to no action
  • resolution set to fixed

Tested in 10.1.3 os351 that one can connect/disconnect to APs and that signal strength updates appear both in the Network view as well as Sugar's frame.

Note: See TracTickets for help on using tickets.