Sounds like a logic issue in de-duplicating APs, but that shouldn't happen unless there were more than one access point with teh same name in the vicinity... Regardless, I'm marking this a Triaged/Medium against network-manager-applet so that I can get back to look at it, but it doesn't sound like something very straigthforward to fix -- it could be due to the drivers misreporting wifi networks.
As an additional point of information, could you please provide a screenshot that shows the three (or more) entries, so we can clearly see how they're divided, their signal level, etc ?
If possible, could you also attach full debug logs for NM (although you might want to look quickly through them in case they contain sensitive information). Here's how you can do that:
sudo stop network-manager
sudo /usr/sbin/NetworkManager --no-daemon --log-level=DEBUG | tee -a /tmp/nm.log
Reproduce the issue, then Control-C in the terminal to stop NM again (which can then be restarted normally with "sudo start network-manager"). The full debug log will be in /tmp/nm.log; just attach that file to this report after reviewing it.
Sounds like a logic issue in de-duplicating APs, but that shouldn't happen unless there were more than one access point with teh same name in the vicinity... Regardless, I'm marking this a Triaged/Medium against network- manager- applet so that I can get back to look at it, but it doesn't sound like something very straigthforward to fix -- it could be due to the drivers misreporting wifi networks.
As an additional point of information, could you please provide a screenshot that shows the three (or more) entries, so we can clearly see how they're divided, their signal level, etc ?
If possible, could you also attach full debug logs for NM (although you might want to look quickly through them in case they contain sensitive information). Here's how you can do that:
sudo stop network-manager NetworkManager --no-daemon --log-level=DEBUG | tee -a /tmp/nm.log
sudo /usr/sbin/
Reproduce the issue, then Control-C in the terminal to stop NM again (which can then be restarted normally with "sudo start network-manager"). The full debug log will be in /tmp/nm.log; just attach that file to this report after reviewing it.