Description of problem: Complete LAN devices get deactivated when doing a Suspend and Resume on my laptop (Acer TravelMate 5720) Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Suspend 2.Resume 3. Actual results: Disabled lan/wlan, having to enable network within network-manager-applet and doing a "sudo ifconfig wlan0 up" Expected results: (W-)LAN starting up automagically, getting back into the state it was, when the PC got suspended Additional info:
Can you attach your /var/log/messages file when this problem occurs? Thanks!
Created attachment 386427 [details] var log messages This is the /var/log/messages file It may contain the part to enable the Network by hand, as I needed to lookup again which fileyou requested. If the file is not usfull anymore by that reason, please tell. Sincerely
I have similar problem. It seems that nm doesn't wakeup after resume and even doesn't after reboot. # nmcli nm status RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running asleep disabled disabled enabled enabled I use "nmcli nm wakeup" as workaround. # nmcli nm wakeup # nmcli nm status RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running connected disabled disabled enabled enabled Version: NetworkManager-0.8.0-13.git20100509.fc13.i686
Does adding "--print-reply" to the start of the dbus-send statements in /usr/lib64/pm-utils/sleep.d/55NetworkManager help at all? ie for both of the two dbus-send statements in that file, adding --print-reply after the "dbus-send" like so: dbus_send --system --print-reply \ and then see if you can reproduce the issue. What version of the dbus package do you have installed too? The command "rpm -q dbus" in a terminal should tell you.
On successful suspend&resume, NetworkManager should be correctly disabled&enabled. This is done by /usr/lib64/pm-utils/sleep.d/55NetworkManager script. (In reply to comment #2) > Created an attachment (id=386427) [details] > var log messages > It appears you didn't resume successfully, rather rebooted later. In this case, the NM stays disabled (due to the state file). The issue is known; see bug 589108. (In reply to comment #3) Doesn't NM wake up on successful resume for you? It works for me on F13 even without updating the script as described in comment #4.
I'm seeing similar problems on a F13 (x86_64), Dell Vostro 1500. 'nmcli nm' said NetworkManager was still sleeping. Adding the '--print-reply' fixed the symptom, now NM wakes up. I'm not sure if that's actually the information you looked for but given the amount of time this bug is already NEEDINFO, I think I just 'take over' the reporter role ;-)
I just booted to F13 and my NM is activated but the box to 'enable networking' is greyed out, though it is checked. Since I don't want to disable it, it's not an issue in this case but I thought I'd add that I have a similar issue but there's no suspend / hibernate involved.
(In reply to comment #6) > I'm seeing similar problems on a F13 (x86_64), Dell Vostro 1500. 'nmcli nm' > said NetworkManager was still sleeping. Adding the '--print-reply' fixed the > symptom, now NM wakes up. > Hmm. Suspend and resume works correctly for me even without '--print-reply' in /usr/lib64/pm-utils/sleep.d/55NetworkManager in F13. I use: NetworkManager-0.8.1-4.git20100817.fc13.x86_64 dbus-1.2.24-1.fc13.x86_64 dbus-glib-0.86-4.fc13.x86_64 pm-utils-1.2.6.1-1.fc13.x86_64 Could you please paste your package versions (rpm -q <package_name>)? And also grab /var/log/messages to see whether there are some errors. It should contains something like this on successful suspend/resume cycle: Aug 30 09:31:21 gromit NetworkManager[1279]: <info> sleep requested (sleeping: no enabled: yes) Aug 30 09:31:21 gromit NetworkManager[1279]: <info> sleeping or disabling... Aug 30 09:31:21 gromit NetworkManager[1279]: <info> (eth0): now unmanaged ... ... Aug 30 09:31:58 gromit NetworkManager[1279]: <info> wake requested (sleeping: yes enabled: yes) Aug 30 09:31:58 gromit NetworkManager[1279]: <info> waking up and re-enabling... Aug 30 09:31:58 gromit NetworkManager[1279]: <info> (eth0): now managed > I'm not sure if that's actually the information you looked for but given the > amount of time this bug is already NEEDINFO, I think I just 'take over' the > reporter role ;-) Thanks for that!
(In reply to comment #7) > I just booted to F13 and my NM is activated but the box to 'enable networking' > is greyed out, though it is checked. Since I don't want to disable it, it's not > an issue in this case but I thought I'd add that I have a similar issue but > there's no suspend / hibernate involved. For grayed out checkboxes see bug 627365.
unfortuantly I can not provide any additional information as the laptop was sold some time ago and life kept me busy :/ feel free to take over the bug...
*** This bug has been marked as a duplicate of bug 627279 ***