[Bugs] #1882 Sugar LOW: cannot connect to wireless network after restarting NetworkManager
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Wed Apr 23 13:07:36 EDT 2014
#1882: cannot connect to wireless network after restarting NetworkManager
---------------------------+-------------------------------------
Reporter: sascha_silbe | Owner: tomeu
Type: defect | Status: new
Priority: Low | Milestone: Unspecified
Component: Sugar | Version: Git as of bugdate
Severity: Major | Resolution:
Keywords: | Distribution/OS: Unspecified
Bug Status: Unconfirmed |
---------------------------+-------------------------------------
\
\
\
\
Changes (by tch):
* priority: Unspecified by Maintainer => Low
\
\
\
Comment:
This is still present in Sugar 0.101.6 (tested with 34003xx4 from
Australia). Even though a little different behavior.
Steps to reproduce (pretty restart):
1. in sugar neighborhood view, connect to AP.
2. in terminal, $sudo service NetworkManager restart.
3. during the restart, AP icons disappear from neighborhood view.
4. once NetworkManager is back, the AP icons are visible again
5. at this point, sugar autoconnect to the AP properly (ie., try ping,
browse, etc).
6. BUT, if you explicitly disconnect from the AP, clicking on disconnect
option, you can no longer connect to the AP.
Steps to reproduce (ugly restart):
1. in sugar neighborhood view, connect to AP.
2. in terminal, $sudo killall NetworkManager.
3. during the restart, AP icons disappear from neighborhood view.
4. in terminal, $sudo service NetworkManager start.
5. at this point, sugar autoconnect to the AP properly (ie., try ping,
browse, etc).
6. 6. BUT, if you explicitly disconnect from the AP, clicking on
disconnect option, you can no longer connect to the AP.
The same happens in both cases.
I wonder if using NM bindings would make any difference.
\
\
\
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/1882#comment:3>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list