Created attachment 1076255 [details] the chunk of the journalctl output from suspend to resume and NM restart Description of problem: Whenever I boot the system or resume it from a suspend, GNOME Network Manager's status icon shows the ethernet icon with a question mark as NM thinks it only has local connectivity. If I restart the NetworkManager.service, it the icon changes to the standard ethernet icon. Version-Release number of selected component (if applicable): NetworkManager-0.9.10.2-5.fc21.x86_64 How reproducible: 100 % Steps to Reproduce: 1. suspend and resume a machine with ethernet connection Actual results: NM thinks it only has local connectivity Expected results: NM reports global (Internet) connectivity Additional info: don't have another F21 machine to check it it's specific to my machine or not
On 2015-09-23 11:01:35 EDT Vratislav Podzimek wrote: > don't have another F21 machine to check it it's specific to my machine or not It's not just your machine. I started seeing this (the '?' instead of the usual WiFi strength indicator) yesterday after updating to kernel-4.1.8-100.fc21.x86_64. (FWIW updates to enca, epiphany-runtime, freedts, liberation-fonts, perl-Encode, python-pycurl, python3-pycurl, and sqlite came down at the same time.) As suggested, $ su -c 'service NetworkManager restart' clears the problem temporarily for me. However, suspending and resuming did not bring the problem back. (Perhaps because I resumed immediately after suspending.) I'd be happy to provide more information or perform tests if needed. N.
(In reply to Vratislav Podzimek from comment #0) > Created attachment 1076255 [details] > the chunk of the journalctl output from suspend to resume and NM restart > NetworkManager correctly auto-activates ethernet connection on resume (even if it takes some time due to computer slow wake up). Sep 23 07:29:21 workstation.podzimkovi.no-ip.biz NetworkManager[7425]: <info> waking up... ... Sep 23 07:29:26 workstation.podzimkovi.no-ip.biz kernel: ata6: link is slow to respond, please be patient (ready=0) Sep 23 07:29:26 workstation.podzimkovi.no-ip.biz kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 23 07:29:26 workstation.podzimkovi.no-ip.biz kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Sep 23 07:29:26 workstation.podzimkovi.no-ip.biz kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88040e0d1000), AE_NOT_FOUND (20150410/psparse-536) Sep 23 07:29:26 workstation.podzimkovi.no-ip.biz kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Sep 23 07:29:26 workstation.podzimkovi.no-ip.biz kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node ffff88040e0d1000), AE_NOT_FOUND (20150410/psparse-536) Sep 23 07:29:26 workstation.podzimkovi.no-ip.biz kernel: ata5.00: configured for UDMA/133 Sep 23 07:29:27 workstation.podzimkovi.no-ip.biz kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 23 07:29:27 workstation.podzimkovi.no-ip.biz kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Sep 23 07:29:27 workstation.podzimkovi.no-ip.biz kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88040e0d1078), AE_NOT_FOUND (20150410/psparse-536) Sep 23 07:29:27 workstation.podzimkovi.no-ip.biz kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20150410/psargs-359) Sep 23 07:29:27 workstation.podzimkovi.no-ip.biz kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node ffff88040e0d1078), AE_NOT_FOUND (20150410/psparse-536) Sep 23 07:29:27 workstation.podzimkovi.no-ip.biz kernel: ata6.00: configured for UDMA/133 Sep 23 07:29:31 workstation.podzimkovi.no-ip.biz kernel: alx 0000:03:00.0 p4p1: NIC Up: 100 Mbps Full Sep 23 07:29:31 workstation.podzimkovi.no-ip.biz NetworkManager[7425]: <info> (p4p1): link connected Sep 23 07:29:31 workstation.podzimkovi.no-ip.biz NetworkManager[7425]: <info> (p4p1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] Sep 23 07:29:31 workstation.podzimkovi.no-ip.biz NetworkManager[7425]: <info> Auto-activating connection 'Wired connection 1'. Anyway, can you get output of $ nmcli device $ nmcli general to see the NetworkManager state, because the issue can be just Gnome icon problem.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I neglected to report this before, but for me at least -- the situation may be different for the OP -- the problem lasted only a few days (during which time it happened absolutely consistently) and went away after an update, so it must have been very promptly fixed. So -- assuming I was experiencing the same issue as the OP (and it certainly seems that it was the same) -- this bug can indeed be safely closed. N.
This is what I got today after resume from suspend: [root@workstation koki]# nmcli device DEVICE TYPE STATE CONNECTION virbr0 bridge connected virbr0 p4p1 ethernet connected Wired connection 1 virbr0-nic tap connected virbr0-nic virbr1 bridge connecting (getting IP configuration) Bridge virbr1 lo loopback unmanaged -- [root@workstation koki]# nmcli general STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connecting none enabled enabled enabled enabled [root@workstation koki]# systemctl restart NetworkManager [root@workstation koki]# nmcli device DEVICE TYPE STATE CONNECTION virbr0 bridge connected virbr0 p4p1 ethernet connected Wired connection 1 virbr0-nic tap connected virbr0-nic virbr1 bridge connecting (getting IP configuration) Bridge virbr1 lo loopback unmanaged -- [root@workstation koki]# nmcli general STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected full enabled enabled enabled enabled
I just tried to suspend and resume a Fedora 23 system running on the same machine and everything works here as expected. So since F21 is almost EOL anyway, I don't think anybody should spend extra time tracking down this issue.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.