Opened 9 years ago

Closed 8 years ago

#2808 closed defect (fixed)

Network not reconnected on lid close/open on XO-1

Reported by: hal.murray Owned by: erikos
Priority: Low Milestone: Unspecified
Component: Sugar Version: 0.92.x
Severity: Minor Keywords: 11.3.0
Cc: dsd Distribution/OS: OLPC
Bug Status: Needinfo

Description

GNOME automatically reconnects to my AP but Sugar doesn't. I assume Sugar is missing a few lines of code someplace.

[Opening the lid doesn't automatically wakeup on XO-1 or XO-1.5
You have to poke the power button. Details in:

http://dev.laptop.org/ticket/10402 ]

After wakeup, my XO-1 goes through the following sequence:

(I had it showing the Network Neighborhood when I closed the lid.)
It comes back showing no APs and no Mesh circles.
It blinks the WiFi LED a few times, then shows the Mesh circles.

Sometimes it shows an AP.
(I normally have several APs visible.)

Then it scans for mesh networks.
Then it blinks again and shows some (more) APs, including mine
It doesn't reconnect to my AP. The WiFi LED stays off.
If I poke my AP, it reconnects.

This happens on os16 which includes Sugar 0.92.0

http://build.laptop.org/11.2.0/os16/

Attachments (1)

shell.log (17.4 KB) - added by hal.murray 9 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 Changed 9 years ago by greenfeld

  • Keywords 11.2.0 added
  • Owner set to erikos
  • Status changed from new to assigned

comment:2 Changed 9 years ago by erikos

  • Bug Status changed from Unconfirmed to Needinfo

Can you restest with build 22?

To related tickets, that come to my mind.

http://dev.laptop.org/ticket/10672

http://dev.laptop.org/ticket/10725

comment:3 Changed 9 years ago by hal.murray

Can you restest with build 22?

Sure. No change.

comment:4 Changed 9 years ago by erikos

Ok, I just tested the following:

  • connected to my AP with an XO-1 running os22
  • use the power button to send the laptop to sleep
  • woke it up using the power button
  • the laptop did automatically reconnect to my AP

Any other hints why it does fail in your case? Encryption? Anything in the logs (shell.log or /var/log/messages)?

Changed 9 years ago by hal.murray

comment:5 Changed 9 years ago by hal.murray

[Sorry for the delay.]

I'm using os23 now. Everything I've tried confirms that Sugar requires a poke and Gnome works OK.

Any other hints why it does fail in your case? Encryption? Anything in the
logs (shell.log or /var/log/messages)?

shell.log attached. As far as I can see, it never tries my AP until I poke that icon.

My AP is on channel 6.
I'm using a Linksys/Cicso WRT54GL with vanilla firmware and all the encryption stuff turned on.

comment:6 Changed 9 years ago by sascha_silbe

  • Component changed from untriaged to sugar

comment:7 Changed 9 years ago by erikos

  • Cc dsd added
  • Keywords 11.3.0 added; 11.2.0 removed

Daniel, I copied you as you wanted to look at connectivity during that cycle.

comment:8 Changed 8 years ago by hal.murray

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

I just tried again with 12.1.0 (build 9), Sugar 0.96.1, firmware Q2F11

It's working correctly now.

Note: See TracTickets for help on using tickets.