I'm glad it worked for you (I knew it would). The ridiculous thing about this is that probably 50% of the users and developers following this knows exactly how to fix it, but no suggested fix is accepted.
If you was able to connect, you're no longer affected by this bug. My guess is that what you're now experiencing is a WIFI-driver bug, and my best guess is that your WIFI card is a Broadcom. You could try the following (NOTE: this is NOT related to this bug)
1) enable the proprietary Broadcom driver
2) (lol-option) disable 1) and opt for kernel support might work
3) Upgrade kernel. You might want to try kernel 3.13. That fixed it for me.
Try this at YOUR OWN RISK:
cd /tmp
wget http://goo.gl/x4JYAz -O kernel-3.13
chmod +x kernel-3.13
sudo sh kernel-3.13
sudo reboot
The above is NOT related to the bug described in this thread, and I will not provide further advise here!
@Jan Hauke Maase (h-maase+dev)
I'm glad it worked for you (I knew it would). The ridiculous thing about this is that probably 50% of the users and developers following this knows exactly how to fix it, but no suggested fix is accepted.
If you was able to connect, you're no longer affected by this bug. My guess is that what you're now experiencing is a WIFI-driver bug, and my best guess is that your WIFI card is a Broadcom. You could try the following (NOTE: this is NOT related to this bug)
1) enable the proprietary Broadcom driver
2) (lol-option) disable 1) and opt for kernel support might work
3) Upgrade kernel. You might want to try kernel 3.13. That fixed it for me.
Try this at YOUR OWN RISK:
cd /tmp goo.gl/ x4JYAz -O kernel-3.13
wget http://
chmod +x kernel-3.13
sudo sh kernel-3.13
sudo reboot
The above is NOT related to the bug described in this thread, and I will not provide further advise here!