#1806 closed defect (notsugar)
Passphrase dialog presented even if the passphrase wasn't the problem
| Reported by: | sascha_silbe | Owned by: | tomeu |
|---|---|---|---|
| Priority: | Unspecified by Maintainer | Milestone: | |
| Component: | Sugar | Version: | Git as of bugdate |
| Severity: | Minor | Keywords: | |
| Cc: | Distribution/OS: | Unspecified | |
| Bug Status: | New |
Description
How to reproduce:
- Wait for an already successfully configured AP to appear in neighborhood
- Turn off AP. It will remain for some time in the neighborhood.
- Tell Sugar to connect to switched off AP.
Actual results:
Sugar tries to connect and after some time asks for the passphrase.
Expected results:
Fail silently.
Please note that this is the easiest way to reproduce the issue, not the only one to trigger it.
Change History (5)
comment:1 Changed 14 years ago by sascha_silbe
comment:2 Changed 14 years ago by sascha_silbe
comment:3 Changed 13 years ago by quozl
The symptom you describe only occurs if the AP has encryption. On an open AP that is powered off before Sugar connects, the expected result occurs.
When an AP with encryption is selected just after it is powered off, dbus-monitor --system shows the device enters NM_DEVICE_STATE_NEED_AUTH. Therefore it is a NetworkManager problem.
comment:4 Changed 10 years ago by dnarvaez
- Resolution set to notsugar
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
This might actually be a NetworkManager bug - I had a very similar experience on a Gnome-using system right now.