[Bug 1106860] New: NetworkManager fails connecting after resuming from suspend to RAM: dhclient failed to start
http://bugzilla.suse.com/show_bug.cgi?id=1106860 Bug ID: 1106860 Summary: NetworkManager fails connecting after resuming from suspend to RAM: dhclient failed to start Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: opensuse.lietuviu.kalba@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 781643 --> http://bugzilla.suse.com/attachment.cgi?id=781643&action=edit journalctl -u NetworkManager output at resuming after suspend to RAM Quite often (though not always) NetworkManager fails to connect to Wifi network after resuming from suspend to RAM. Earlier I saw this bug older openSUSE versions and Tumbleweed too from time to time, however it seemed totally random and I did not associated this with suspending. In journal I see info about NetworkManager: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds) <warn> dhclient failed to start: 'Nepavyko atskirti (Nepavyko išskirti atminties)' <info> (wlan0): device state change: ip-config -> failed (reason 'dhcp-start-failed') [70 120 15] <info> NetworkManager state is now DISCONNECTED Here "Nepavyko išskirti atminties" means "Failed to allocate memory" in English Work around that always help: rcnetwork restart -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1106860
http://bugzilla.suse.com/show_bug.cgi?id=1106860#c1
--- Comment #1 from Mindaugas Baranauskas
http://bugzilla.suse.com/show_bug.cgi?id=1106860
http://bugzilla.suse.com/show_bug.cgi?id=1106860#c3
Tomáš Chvátal
participants (1)
-
bugzilla_noreply@novell.com