Opened 14 years ago
Closed 10 years ago
#1802 closed defect (duplicate)
No way to tell Sugar not to connect to any network
Reported by: | sascha_silbe | Owned by: | tomeu |
---|---|---|---|
Priority: | Unspecified by Maintainer | Milestone: | Unspecified |
Component: | Sugar | Version: | Git as of bugdate |
Severity: | Major | Keywords: | |
Cc: | Distribution/OS: | Unspecified | |
Bug Status: | New |
Description
If a working network connection (at least WLAN, haven't tried wired LAN) is available, Sugar will use it no matter what. Choosing disconnect on the frame device will only cause it to reconnect.
Together with a set of other misbehaviours (will file separate bugs) and the unavailability of a way to power off the WLAN device from Sugar this is very annoying. Even when not considering interactions with other bugs it's very irritating that "Disconnect" actually causes a reconnect.
Change History (4)
comment:1 Changed 14 years ago by sascha_silbe
- Summary changed from No way to tell Sugar ''not'' to connect to any network to No way to tell Sugar not to connect to any network
comment:2 Changed 14 years ago by sascha_silbe
comment:3 Changed 13 years ago by quozl
Patch in #1673 will aid in solving this ticket, since choosing disconnect will prevent reconnect.
Actually, this is almost a duplicate. Review requested. ;-)
comment:4 Changed 10 years ago by dnarvaez
- Resolution set to duplicate
- Status changed from new to closed
For the mesh device this is even worse as it will start trying to connect directly after log-in and neither stop automatically nor offer the option to do so to the user.