Ticket #11782 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

Sometimes two icons are shown in the frame for the network

Reported by: manuq Owned by: erikos
Priority: normal Milestone: 12.1.0
Component: sugar Version: 1.5-C2
Keywords: Cc: dsd
Action Needed: no action Verified: no
Deployments affected: Blocked By:
Blocking:

Description

This is in the same machine with the issue in ticket #11778 . If I keep typing or moving the cursor, the machine doesn't fall in #11778 and keeps connected, but sometimes two icons appear:

Picture:

http://dev.laptop.org/~manuq/net-icon-twice.png

Attachments

shell.log (4.7 kB) - added by manuq 2 years ago.

Change History

Changed 2 years ago by dsd

Please capture sugar logs from when this happens.

Changed 2 years ago by dsd

  • component changed from not assigned to sugar

Changed 2 years ago by dsd

  • cc dsd added
  • next_action changed from never set to review

I had seen this as well, and I managed to reproduce it. If you wait approxiamtely 5 seconds at the naming screen before continuing you will see it - the network driver finishes loading right when Sugar is loading up. (its taking a long time due to #11710)

Diagnosed and sent a patch to fix this:

[PATCH] Prevent handling network devices twice (OLPC#11782)

Changed 2 years ago by manuq

Just for the record, seems that Daniel has a fix!

I got what seems another flavour of the same issue?

http://dev.laptop.org/~manuq/net-icon-twice2.png

One icon that shows no wireless network and the other that is connected. Log of Sugar attached.

Changed 2 years ago by manuq

Changed 2 years ago by dsd

  • next_action changed from review to add to build

Fixed in sugar-0.95.7

Changed 2 years ago by dsd

  • next_action changed from add to build to test in build

Test in 12.1.0 build 8.

Changed 2 years ago by manuq

Tested XO-1.5 and XO-1, no more twin network icons, great.

Changed 2 years ago by greenfeld

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

I could not reproduce this issue with 12.1.0 build 8, so I presume it is fixed.

Note: See TracTickets for help on using tickets.