After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 686951 - NetworkManager vs Sleep Mode
NetworkManager vs Sleep Mode
Status: RESOLVED DUPLICATE of bug 683206
Product: NetworkManager
Classification: Platform
Component: general
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-10-26 18:04 UTC by Harry Monroe
Modified: 2013-05-11 09:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Harry Monroe 2012-10-26 18:04:18 UTC 
When i'm going to sleep mode NetworkManager takes the eth0 device down.
Result: WakeOnLan won't work
Workaround: disable NetworkManager, manually edit /etc/network/interfaces, ifup eth0, WOL works.

log:
*sleepbutton*
Oct 26 15:54:05 ubuntu NetworkManager[2554]: <info> sleep requested (sleeping: no  enabled: yes)
Oct 26 15:54:05 ubuntu NetworkManager[2554]: <info> sleeping or disabling...
Oct 26 15:54:05 ubuntu NetworkManager[2554]: <info> (eth0): now unmanaged
Oct 26 15:54:05 ubuntu NetworkManager[2554]: <info> (eth0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Oct 26 15:54:05 ubuntu NetworkManager[2554]: <info> (eth0): deactivating device (reason 'sleeping') [37]
Oct 26 15:54:05 ubuntu NetworkManager[2554]: <info> (eth0): cleaning up...
Oct 26 15:54:05 ubuntu NetworkManager[2554]: <info> (eth0): taking down device.
Comment 1 Pavel Simerda 2013-05-09 10:53:09 UTC 
I think this has been fixed in master:

commit ce4f2a4bd6270400e9d32c98ceaf8fa8f0b5df8c
Author: Dan Winship <danw@gnome.org>
Date:   Wed Apr 17 10:41:15 2013 -0400

    core, libnm-glib: add NMDeviceGeneric
    
    Add NMDeviceGeneric, to provide generic support for unknown device
    types, and create NMDeviceGenerics for those devices that NM
    previously was ignoring. Allow NMSettingGeneric connections to be
    activated on (managed) NMDeviceGenerics.

Assigning to Dan Winship and closing.
Comment 2 Pavel Simerda 2013-05-09 10:56:56 UTC 
(In reply to comment #1)
> I think this has been fixed in master:
> 
> commit ce4f2a4bd6270400e9d32c98ceaf8fa8f0b5df8c
> Author: Dan Winship <danw@gnome.org>
> Date:   Wed Apr 17 10:41:15 2013 -0400
> 
>     core, libnm-glib: add NMDeviceGeneric
> 
>     Add NMDeviceGeneric, to provide generic support for unknown device
>     types, and create NMDeviceGenerics for those devices that NM
>     previously was ignoring. Allow NMSettingGeneric connections to be
>     activated on (managed) NMDeviceGenerics.
> 
> Assigning to Dan Winship and closing.

Wrong bug, please ignore.
Comment 3 Pavel Simerda 2013-05-09 10:58:37 UTC 
(In reply to comment #0)
> Workaround: disable NetworkManager, manually edit /etc/network/interfaces, ifup
> eth0, WOL works.

A better workaround might be upping the interface via dispatcher.d scripts.
Comment 4 Pavel Simerda 2013-05-11 09:00:15 UTC 
Marking as duplicate as this bug report just describes a reason to avoid taking devices down. The discussion can be just as well done in the remaining bug report.

*** This bug has been marked as a duplicate of bug 683206 ***