Created attachment 756354 [details] the result of sudo grep NetworkManager /var/log/messages after resume but before manually enabling the network via NM Applet Description of problem: After I wake my desktop from sleep the internet doesn't re-connect. NM-Applet shows that it is 'off', I have to turn it on at which point it connects and works fine till the next sleep cycle. Version-Release number of selected component (if applicable): 0.9.8.1-4.git20130515-fc19 How reproducible: Always Steps to Reproduce: 1. Computer with wired connection 2. Suspend machine 3. Wake Actual results: Internet doesn't auto-resume and is marked as 'off' Expected results: Internet connection resumes as well. Additional info:
Created attachment 756355 [details] sudo grep NetworkManager /var/log/messages after manually enabling the network via nm-applet
Created attachment 756356 [details] output of sudo journalctl -x -n 300 prior to enabling network via nm-applet
Ok, when you wake up before you enable via nm-applet, can you run: nmcli dev list iface eth0 and we care about the AUTOCONNECT field. Thanks!
GENERAL.AUTOCONNECT: yes Full output: GENERAL.DEVICE: eth0 GENERAL.TYPE: 802-3-ethernet GENERAL.VENDOR: Realtek Semiconductor Co., Ltd. GENERAL.PRODUCT: -- GENERAL.DRIVER: r8169 GENERAL.DRIVER-VERSION: 2.3LK-NAPI GENERAL.FIRMWARE-VERSION: GENERAL.HWADDR: 1C:6F:65:3C:54:1C GENERAL.STATE: 30 (disconnected) GENERAL.REASON: 40 (Carrier/link changed) GENERAL.UDI: /sys/devices/pci0000:00/0000:00:1c.4/0000:07:00.0/net/eth0 GENERAL.IP-IFACE: GENERAL.NM-MANAGED: yes GENERAL.AUTOCONNECT: yes GENERAL.FIRMWARE-MISSING: no GENERAL.CONNECTION: not connected CAPABILITIES.CARRIER-DETECT: yes CAPABILITIES.SPEED: 100 Mb/s CONNECTIONS.AVAILABLE-CONNECTION-PATHS: /org/freedesktop/NetworkManager/Settings/{0} CONNECTIONS.AVAILABLE-CONNECTIONS[1]: 7e804f22-a220-4829-a8b8-6e3e1aaf1df5 | eth0 WIRED-PROPERTIES.CARRIER: on
Interesting; so the device is not blocked for autoconnect, but NM doesn't appear to try to autoconnect anything. The logs aren't going to help us here since they're not detailed enough, so we'll probably need some custom builds, or I'll have to see if I can reproduce the issue.
I should note I also just rebooted the machine and the network didn't come up in that scenario either. I can build or install whatever to test this out... you know where I am in IRC whenever you feel like tackling this.
Can you do the following for me? sudo dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.SetLogging string:"debug" string:"" and then suspend/resume and post the syslog/journal output for NM.
Created attachment 756884 [details] /var/log/messages with NM Logging set to Debug Oddly the network worked this time.
Ok, see if you can leave the debugging there and then paste the logs when it doesn't work. Thanks!
Created attachment 757271 [details] Failed resume
via IRC we discovered there's /etc/NetworkManager/system-connections/Auto Ethernet which has autoconnect=no, which is causing this. So that's one mystery down, but the next mystery is how that file got there in the first place.
More than likely this is user called issue. So I'll close this to knock one off your list.