Whether it's been running for 30 minutes or not doesn't change much
though; the connection *can* fail, and the connectivity checking is a
pretty simple HTTP check.
Could you please attach debug logs for NetworkManager (with the
connectivity checking enabled) -- see
https://wiki.gnome.org/Projects/
I eventually figured out that's what was happening. However, the
connectivity check is not working correctly. In my case, there is indeed
ethernet connectivity, despite it thinking that there isn't. It will
assign the network "penalty" metric even when ethernet has been
connected for 30+ minutes, s
This is working as designed.
NetworkManager now uses a metric "penalty" when connectivity cannot be
detected as full for a connection, and reduces the metric accordingly.
This makes it so that if you're connected to both wired and wireless,
and your wired connection becomes bad but the wireless c
Marking Incomplete for now, in case there's more to it than a
connectivity checking issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1788659
Title:
network manager assign
I have seen this for quite some time as well. Usually connected to both
wifi and cabled network at work (while laptop is docked), which is quite
handy for when I go to meetings and undock my laptop, but will stay
online since I am also on wifi.
After a while though, and after re-docking the laptop
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchp
6 matches
Mail list logo
