it's nice when you at least have/get an error message to check instead of your network manager just showing a progress bar and timing out. some other common possibles?
is the file you are copying possibly inserting a phantom carriage return due to being copied from a dos format text file? if the password is obfuscated you can always count the keystroke number of *s. or just type it in manually if possible...
is network manager fixed to actually manage the device? aka the "device not managed error" that is relatively common in debian.
if you if issue #ifconfig lo, does you loopback provide a valid localhost inet addr or is it all zeros?
have you given wicd network manager a try instead? since even mentioning this, since you said is you home network we can guess it is WPA2 but is it personal, enterprise? both wicd and network manager can be picky and cause a timeout no error symptom if not getting along,and by this point worth a look...
wicd previous versions would even do this if the interface was not brought up with /etc/init.d/wicd-client start before even starting x with certain configuration matches.
you know the wifi adapter is functional, but the usual basics lsusb,ifconfig,etc would probably start over here for me. maybe after firing up something like forkali.sh script.they can be very helpful with some post-install kali issue fixes; but can also quickly make things worse and only mentioned with the appropriate amount of reluctance.
just some things I could see being easy to overlook because they are common and "simple". hopefully they put your horse off in the direction of some water anyway :)
