[Bugs] #2187 UNSP: Sugar Ad-hoc network: reconnect after suspend
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Wed Sep 15 06:28:19 EDT 2010
#2187: Sugar Ad-hoc network: reconnect after suspend
------------------------------------------+---------------------------------
Reporter: erikos | Owner: erikos
Type: enhancement | Status: new
Priority: Unspecified by Maintainer | Milestone: 0.90
Component: sugar | Version: Unspecified
Severity: Major | Keywords: r?
Distribution: Unspecified | Status_field: Assigned
------------------------------------------+---------------------------------
Comment(by sascha_silbe):
Replying to [comment:1 erikos]:
> When we came out from suspend the method autoconnect was called [1].
[...]
I wonder why that happens in the first place. Shouldn't NetworkManager
just keep connected to the Ad-Hoc network (if the WiFi chip remains
powered) resp. reconnect to the Ad-Hoc network after resume?
> Result: the patch above. That always waits for 30 seconds, then checks
if we are in the state disconnected and if yes applies the autoconnect
logic. Simple, but handle all the cases :)
This is getting rather ugly, both from a code POV and from a usability one
(imagine an XO auto-suspending after 5 seconds idle-time and taking 30
seconds to reconnect to the network).
Can't we push the Ad-Hoc network handling to NetworkManager? Not only
would it make our life much easier in Sugar, I'm also worried that with
[http://live.gnome.org/NetworkManager/RemovingUserSettings upstream
removing user settings] our code might not be able to work this way in the
future.
> [1]
http://git.sugarlabs.org/projects/sugar/repos/mainline/blobs/master/src/jarabe/model/adhoc.py#line141
[...]
BTW, you can use [WikiFormatting Trac wiki syntax] in tickets.
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/2187#comment:2>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list