| 2007-11-15 17:03:55 |
Diti Torterat |
bug |
|
|
added bug |
| 2007-11-28 15:39:50 |
Miguel Ruiz |
network-manager: status |
New |
Incomplete |
|
| 2007-11-28 17:01:46 |
Diti Torterat |
bug |
|
|
added attachment 'syslog' (/var/log/syslog) |
| 2008-05-26 21:11:10 |
BeBop |
bug |
|
|
assigned to network-manager-applet (Ubuntu) |
| 2008-10-15 19:02:02 |
Diti Torterat |
description |
I run on Ubuntu Gutsy for the moment. The nm-applet can get me connected to WPA2 networks, now (it didn't wirk on Feisty).
But as I can't specify a default wifi network, I used the manual configuration. To reproduce the bug :
• Select “manual configuration” on nm-applet ;
• Deactivate the automatic mode and enter the settings of a WPA2 network, where encryption is set to “WPA2 Personnal”. My password is an hexadecimal 10 characters-long ;
• You are connected. But now, logout, login a go on the Internet. It doesn't works ;
• Go in the settings like some minutes ago. Then you will see than the encryption is set to “WPA Personnal” and the password is very, very long (“•••••••••••••••••••••••••••••••••”). |
I run on Ubuntu Gutsy for the moment. The nm-applet can get me connected to WPA2 networks for now (it didn't work on Feisty).
But as I can't specify a default wifi network, I had to use manual configuration. To reproduce the bug:
• Select “manual configuration” on nm-applet ;
• Deactivate automatic mode and enter settings of a WPA2 network, while encryption is set to “WPA2 Personnal”. My password is an hexadecimal 10 characters-long ;
• You are connected. But now, log out, log in and go on the Internet. It doesn't works;
• Go to settings like some minutes ago. Then you will see that encryption is set to “WPA Personnal” and the password is very, very long (“•••••••••••••••••••••••••••••••••”). |
|
| 2009-02-10 01:09:11 |
Alexander Sack |
network-manager-applet: status |
New |
Invalid |
|
| 2009-02-10 01:09:11 |
Alexander Sack |
network-manager-applet: statusexplanation |
|
not an applet issue for sure. Most likely a driver timeout issue. |
|
| 2009-02-19 18:03:00 |
Martin Mai |
network-manager: status |
Incomplete |
Invalid |
|
| 2009-02-19 18:03:00 |
Martin Mai |
network-manager: statusexplanation |
|
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! |
|
