[Touch-packages] [Bug 1788659] Re: network manager assigns ethernet default route metric of 20100
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, so something is causing it to incorrectly fail the connectivity check. If I override the metric manually, it works and uses ethernet, so there is not a problem with the connection. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1788659 Title: network manager assigns ethernet default route metric of 20100 Status in network-manager package in Ubuntu: Incomplete Bug description: After upgrading from 16.04 to 18.04, when I boot with an ethernet cable connected, Ubuntu prefers to use the wifi interface over the ethernet interface. Wifi is assigned the normal metric of 600 for both of its routing table entries. However ethernet is assigned a metric of 20100. I edited the connection details via nmcli to manually set the ethernet metric to 100. After a reboot, the link route (for the LAN subnet) correctly has a metric of 100. But the default route for eth0 is still 20100. nm-applet shows the wifi icon, correctly indicating that the default route is over wifi rather than ethernet. The only fix is to manually set the route after every reboot, or turn off wifi. This is a regression from 16.04. network-manager 1.10.6-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1788659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788659] [NEW] network manager assigns ethernet default route metric of 20100
Public bug reported: After upgrading from 16.04 to 18.04, when I boot with an ethernet cable connected, Ubuntu prefers to use the wifi interface over the ethernet interface. Wifi is assigned the normal metric of 600 for both of its routing table entries. However ethernet is assigned a metric of 20100. I edited the connection details via nmcli to manually set the ethernet metric to 100. After a reboot, the link route (for the LAN subnet) correctly has a metric of 100. But the default route for eth0 is still 20100. nm-applet shows the wifi icon, correctly indicating that the default route is over wifi rather than ethernet. The only fix is to manually set the route after every reboot, or turn off wifi. This is a regression from 16.04. network-manager 1.10.6-2ubuntu1 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1788659 Title: network manager assigns ethernet default route metric of 20100 Status in network-manager package in Ubuntu: New Bug description: After upgrading from 16.04 to 18.04, when I boot with an ethernet cable connected, Ubuntu prefers to use the wifi interface over the ethernet interface. Wifi is assigned the normal metric of 600 for both of its routing table entries. However ethernet is assigned a metric of 20100. I edited the connection details via nmcli to manually set the ethernet metric to 100. After a reboot, the link route (for the LAN subnet) correctly has a metric of 100. But the default route for eth0 is still 20100. nm-applet shows the wifi icon, correctly indicating that the default route is over wifi rather than ethernet. The only fix is to manually set the route after every reboot, or turn off wifi. This is a regression from 16.04. network-manager 1.10.6-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1788659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
One other note, it appears that gsd-power might be blocking the suspend: josh@josh-ThinkPad-T460 ~ systemd-inhibit Who: gdm (UID 147/gdm, PID 3040/gsd-power) What: sleep Why: GNOME needs to lock the screen Mode: delay Who: NetworkManager (UID 0/root, PID 1524/NetworkManager) What: sleep Why: NetworkManager needs to turn off networks Mode: delay Who: josh (UID 1000/josh, PID 20754/gsd-power) What: sleep Why: GNOME needs to lock the screen Mode: delay Who: gdm (UID 147/gdm, PID 3037/gsd-media-keys) What: sleep Why: GNOME handling keypresses Mode: delay Who: Telepathy (UID 1000/josh, PID 4930/mission-control) What: shutdown:sleep Why: Disconnecting IM accounts before suspend/shutdown... Mode: delay Who: josh (UID 1000/josh, PID 20754/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Who: gdm (UID 147/gdm, PID 3040/gsd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Who: gdm (UID 147/gdm, PID 3037/gsd-media-keys) What: handle-power-key:handle-suspend-key:handle-hibernate-key Why: GNOME handling keypresses Mode: block Who: josh (UID 1000/josh, PID 20741/gsd-media-keys) What: handle-power-key:handle-suspend-key:handle-hibernate-key Why: GNOME handling keypresses Mode: block Who: UPower (UID 0/root, PID 2813/upowerd) What: sleep Why: Pause device polling Mode: delay Who: ModemManager (UID 0/root, PID 1466/ModemManager) What: sleep Why: ModemManager needs to reset devices Mode: delay Who: josh (UID 1000/josh, PID 20741/gsd-media-keys) What: sleep Why: GNOME handling keypresses Mode: delay Who: GNOME Shell (UID 1000/josh, PID 20651/gnome-shell) What: sleep Why: GNOME needs to lock the screen Mode: delay 13 inhibitors listed. And this related bug https://github.com/systemd/systemd/issues/7137 In the gnome power settings, on 16.04 there was a toggle to have it perform suspend with the lid closed while docked or while an external monitor was connected. That option is now gone. ** Bug watch added: github.com/systemd/systemd/issues #7137 https://github.com/systemd/systemd/issues/7137 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
I'm experiencing this issue after upgrading from 16.04 to 18.04 on a Thinkpad T460p. I have set the following in /etc/systemd/logind.conf and restarted systemd-logind.service (which logged me out of my session) HandleSuspendKey=suspend HandleHibernateKey=suspend HandleLidSwitch=suspend HandleLidSwitchDocked=suspend journalctl shows "systemd-logind[20403]: Lid closed." when I close the lid, but it does not take any action other than my external monitor shutting off briefly before turning back on. pm-utils is installed. There's nothing else in the system logs related to suspend, and the power light on the laptop lid does not start pulsing like it used to do when it began to suspend. So the lid closed event is not triggering it to attempt to suspend, despite the correct logind configuration. My laptop is in a docking station and also has an external monitor connected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
