I've been struggling with this nightmare since a long time, and I am ready to give up.
I have tried a plethora of drivers, from TP-Link themselves, the rtl8812AU driver included in Ubuntu, and a number of community forks, and nothing seem to help.
UPDATE 2: Yes, I've been looking at this askubuntu solution but it is several years old, and didn't help me anyway.
Regardless the driver, the USB adapter would connect to a specific network, named "Gasten" in the logs. It will NOT, however, connect to the other network named "test" in the logs. The most weird behaviour I have ever seen is that once the adapted failed to connect to a network, it wouldn't connect to the "Gasten" network anymore either! The only remedy to fix this would be to unplug and replug the adapter, and it then would connect just normal.
My wireless-info.txt is here.
UPDATE: I am currently using the driver found at this repo.
And an excerpt of syslog follows to illustrate failure to re-connect to "Gasten" after it failed to connect to "test" is here. This log excerpt is the result of:
- Connecting the adapter to USB, and automatically connecting to "Gasten" (timestamp Aug 21 14:39:23) on a FritzBox router.
- Trying to connect to network "test", on a D-Link DAP-2553 AP (Timestamp Aug 21 14:39:46)
- After that failed, the system automatically trying to connect to "Gasten" again (timestamp Aug 21 14:40:16) but eventually failing.
- Unplugging the adapter (timestamp Aug 21 14:40:46)
- Replugging the adapter and automatically connecting to "Gasten" again. (timestamp Aug 21 14:41:29)
Please pay special attention to log lines similar to this:
Aug 21 14:39:47 Dianas-Laptop wpa_supplicant: wlx503eaa6208a7: Association request to the driver failed
Google this and you'll find Launchpad bugs and other entries from as old as 10 years!
What the hell is going on!?
Needless to say, this bloody laptop (HP 250 G4) gave me grief with Linux connectivity since the most hellish decision ever to get this thing...
And of course, all other devices in my household are just fine connecting to the "test" network... :-(