MASTER - Network Manager sometimes has "enable networking" unchecked/disabled when resuming from suspend

[Andrew Paulin]

Binary package hint: network-manager

I've noticed that every few suspends, Network Manager will disable networking for no apparent reason. R-clicking the icon and checking "Enable networking" turns it back on, but Joe the User isn't going to realise what's going on. Hardware is a mostly stock Eee PC 701 (Celeron 630MHz, 4GB SSD, Atheros AR5007) with 2GB of RAM, running current Intrepid as of 8:18 AM, October 30 2008 (EDT)

[Alexander Sack (asac)]

this is most likely a race. i think we have another bug about this. so should be a dupe.

[Jack Deslippe (jdeslip)]

I have the exact same problem. Every few suspend/resumes NM disables networking. I have a Dell 1420n laptop with intrepid. THe problem did not exist in hardy.

Can you point me to the bug you think this is a duplicate of so that I can subscribe to it?

[Alexander Sack (asac)]

marking bug as SRU oppertunity for intrepid.

[Alexander Sack (asac)]

important for jaunty release as well.

[Elias K Gardner (zorkerz)]

This is happening to in intrepid 64 so far ever resume (about 3 or 4 times). I am not however able re-enable networking without restarting the computer. d

[Elias K Gardner (zorkerz)]

I must qualify my last comment I just resumed from suspend. As always networking was disabled but this time when I enabled networking again it was able to connect to my network. Using a laptop normally when I suspend it is because I am on the move. For my situation disabling networking on suspend may actually be a feature because I will need to connect to a different network anyway.

[Zach Tibbitts (zachtib)]

+1 Elias,

On a Thinkpad T61p with Intel 4965 AGN Wifi,
every few suspends NM is disabled, right clicking and enabling it causes the applet to freeze and I have to reboot.

[Elias K Gardner (zorkerz)]

This bug has been marked a duplicate of bug#293329 please have any discussion about this issue there. Your bug sounds different Zach, networking is only disabled for me after having suspended. If you still think your bug is the same please subscribe to #293329 or you can search for another bug that meets your symptoms or you can make a new bug.

[Patrick Wagstrom (pridkett)]

Elias, You have your dependencies backward -- bug#293329 is a duplicate of this bug. It appears that this is the tracking bug.

[Elias K Gardner (zorkerz)]

oh dear. Your are right Patrick. I wish my post could be deleted to prevent confusion.
my apologies

[Thomas Mayer (thomas303)]

After update from hardy to intrepid, I had the same problems:
- sometimes after resuming, network interface is disabled and can be enabled via network manager
- sometimes after resuming, network interface is disabled and can NOT be enabled via network manager. I have to restart then to enable it again.

The problems occur about every three resumes. With hardy, I did not have these problems at all.
I have a Dell Inspiron 6000 which uses b44 driver module for networking

[axx (axx)]

This also happens on a Sony Vaio VGN FZ31M with an intel 4965 agn chipset (driver: iwlagn).

[Oded Arbel (oded-geek)]

Same problem for me on a Thinkpad X61s with iwl3945 - when resuming from suspend, Network Manager has networking disabled and must be reenabled manually to connect.

I don't think this happened immediately after I installed Intrepid - I believe one of the updates brought this behavior. Not sure though so if my comment is confusing, disregard it.

[cornbread (corn13read)]

I have the same issue but with my desktop's wired connection. And when I click connect it won't ever until reboot.

[Alexander Sack (asac)]

when you wake up from suspend and see this issue, could you please attach your syslog capturing the complete wake up ... and also a bunch of context from before. Thanks!

[Jarno Suni (jarnos)]

Here is /var/log/syslog after resuming from suspend and manually enabling networking.

[DaveAbrahams (boostpro)]

Here's another one.

[DaveAbrahams (boostpro)]

By the way, I cannot recall this *ever* happening when resuming with a wired connection, and I do it both ways quite regularly.

[Jarno Suni (jarnos)]

DaveAbrahams, I can, but not when I use "deb http://ppa.launchpad.net/xubuntu-dev/ubuntu intrepid main" as software source.

[Jarno Suni (jarnos)]

This happened once even (for wired networking) when I use "deb http://ppa.launchpad.net/xubuntu-dev/ubuntu intrepid main" as software source.

[Jacob Godin (jacobgodin)]

+1 here. I've got 64-bit Intrepid running on an XPS 1530 with the 4965agn. Every few suspends, the app will freeze for a minute or two when I try to enable networking and will come back saying that networking is still disabled. A reboot is required to fix this issue. Also, attempting to kill the process freezes my terminal.

[Alexander Sack (asac)]

On Tue, Jan 06, 2009 at 06:29:17PM -0000, Jacob Godin wrote:
> +1 here. I've got 64-bit Intrepid running on an XPS 1530 with the
> 4965agn. Every few suspends, the app will freeze for a minute or two
> when I try to enable networking and will come back saying that
> networking is still disabled. A reboot is required to fix this issue.
> Also, attempting to kill the process freezes my terminal.
>

Could you plesae check whether the packages provided in
http://launchpad.net/~network-manager/+archive for intrepid/jaunty fix
the "disabled on resume" thing for you?

(the freeze is a driver thing and probably not directly involved)

 - Alexander

[AndyL (thelees-andy)]

I'm seeing similar symptoms in 64-bit Hardy on a Lenovo X61 laptop -- when I restore from a suspend, NM shows an exclamation point and networking is disabled. I can't re-enable it, and any sudo invocations hang.

[Alexander Sack (asac)]

On Thu, Jan 08, 2009 at 08:54:53PM -0000, AndyL wrote:
> I'm seeing similar symptoms in 64-bit Hardy on a Lenovo X61 laptop --
> when I restore from a suspend, NM shows an exclamation point and
> networking is disabled. I can't re-enable it, and any sudo invocations
> hang.
>

Can you please do a tail -n0 /var/log/syslog before you try to
reenable it and post the output you get there in response to your UI
action?

 - Alexander

[Steve Langasek (vorlon)]

Has anyone here affected by the "enable networking unchecked on resume" bug tested the packages in <http://launchpad.net/~network-manager/+archive>?

Issues which require a reboot to re-enable networking are probably a separate bug (and in the case of iwlagn, probably one of the known bugs in the wireless driver).

[Dominique Hazael-Massieux (dominique-hazael-massieux)]

I was affected by the "enable networking unchecked on resume" bug, and just installed the PPA packages which seem to fix the problem - I tried to suspend/resume quite a few times in a row, and the network stayed up each time; I'll report back if the problem re-appears,

[AndyL (thelees-andy)]

I tried the 'tail -n0 /var/log/syslog' suggestion, but there was not output to post.

I will try the packages at <http://launchpad.net/~network-manager/+archive>

[Alexander Sack (asac)]

On Sat, Jan 31, 2009 at 02:48:28PM -0000, Dominique Hazael-Massieux wrote:
> I was affected by the "enable networking unchecked on resume" bug, and
> just installed the PPA packages which seem to fix the problem - I tried
> to suspend/resume quite a few times in a row, and the network stayed up
> each time; I'll report back if the problem re-appears,
>

Did you ever see this again?

 - Alexander

[Alexander Sack (asac)]

On Fri, Feb 06, 2009 at 04:35:42AM -0000, AndyL wrote:
> I tried the 'tail -n0 /var/log/syslog' suggestion, but there was not
> output to post.
>
> I will try the packages at <http://launchpad.net/~network-
> manager/+archive>
>

Have you tried the packages from there? Does this still happen for
you?

 - Alexander

[AndyL (thelees-andy)]

I installed the PPA packages, but I still see the same issue. How can I tell if I have the iwlagn issue? Alternatively, what info should I be getting that would help me identify what bug I am seeing? (or if it is a new one, which I doubt)

[Alexander Sack (asac)]

On Sat, Feb 07, 2009 at 01:33:36AM -0000, AndyL wrote:
> I installed the PPA packages, but I still see the same issue. How can I
> tell if I have the iwlagn issue? Alternatively, what info should I be
> getting that would help me identify what bug I am seeing? (or if it is a
> new one, which I doubt)
>

if you can enable networking by simply checking that menu element you
are seeing this bug.

 - Alexander

[Joel Goguen (jgoguen)]

I have the package from the PPA installed and I'm still seeing this issue. I've attached /var/log/syslog from the point of resuming until my network was active (including a few minutes where I didn't notice it was down because I was opening/reading a document). I'm using ndiswrapper with a Broadcom BCM4328 chip. I've tried using the wl driver as well, but it constantly disconnects me and it's much slower than ndiswrapper so I don't know if this also occurs with that driver.

[jgoguen@hermes:~]$ apt-cache policy network-manager
network-manager:
  Installed: 0.7-0ubuntu1~nm1~intrepid1
  Candidate: 0.7-0ubuntu1~nm1~intrepid1
  Version table:
 *** 0.7-0ubuntu1~nm1~intrepid1 0
        500 http://ppa.launchpad.net intrepid/main Packages
        100 /var/lib/dpkg/status
     0.7~~svn20081018t105859-0ubuntu1.8.10.1 0
        500 http://gulus.usherbrooke.ca intrepid-updates/main Packages
     0.7~~svn20081018t105859-0ubuntu1 0
        500 http://gulus.usherbrooke.ca intrepid/main Packages
[jgoguen@hermes:~]$ uname -a
Linux hermes 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux

[Dominique Hazael-Massieux (dominique-hazael-massieux)]

As I reported earlier (https://bugs.launchpad.net/ubuntu/intrepid/+source/network-manager/+bug/291062/comments/27) I installed the PPA packages; I thought the problem had gone away, but it hasn't entirely; it seems to happen much less often than before, but it still happened a couple of times since then.

[Alexander Sack (asac)]

please try to replace /usr/lib/pm-utils/sleep.d/55NetworkManager with the file i attach here

[Alexander Sack (asac)]

On Tue, Feb 17, 2009 at 10:13:23AM +0100, Alexander Sack wrote:
> On Fri, Feb 13, 2009 at 06:50:45PM -0000, Alexander Sack wrote:
> > please try to replace /usr/lib/pm-utils/sleep.d/55NetworkManager with
> > the file i attach here
> >
> > ** Attachment added: "make dbus-send wait for reply in NM pm-utils script"
> > http://launchpadlibrarian.net/22587993/55NetworkManager
> >
> Could someone please test this? There was enough noise on thie bug
> report to think that you would be happy to get a proposed fix :)
> ... Thanks!
>
> - Alexander
>
>

 - Alexander

[Dominique Hazael-Massieux (dominique-hazael-massieux)]

Seems to be working fine with the new pm-utils script; I haven't had the network disabled for the past few days at least.

[Jack Deslippe (jdeslip)]

Doesn't Work for me. But I didn't have a 55NetworkManager file there
before adding it. Is this file supposed to be used after adding the
ppa? I never tried the ppa.

[Jack Deslippe (jdeslip)]

Doesn't Work for me (still resumed from suspend with networking disabled). But I didn't have a 55NetworkManager file there before adding it. Is this file supposed to be used after adding the ppa? I never tried the ppa.

[Alexander Sack (asac)]

On Tue, Feb 17, 2009 at 09:18:54PM -0000, jdeslip wrote:
> Doesn't Work for me (still resumed from suspend with networking
> disabled). But I didn't have a 55NetworkManager file there before
> adding it. Is this file supposed to be used after adding the ppa? I
> never tried the ppa.
>

pm-utils: /usr/lib/pm-utils/sleep.d/55NetworkManager

do you have pm-utils installed? why not?

 - Alexander

[Jack Deslippe (jdeslip)]

Yep, I have pm-utils installed (at least synaptic tells me so). But,
that file was not present... You sure it didn't come from the PPA?

-Jack

Alexander Sack wrote:
> On Tue, Feb 17, 2009 at 09:18:54PM -0000, jdeslip wrote:
>
>> Doesn't Work for me (still resumed from suspend with networking
>> disabled). But I didn't have a 55NetworkManager file there before
>> adding it. Is this file supposed to be used after adding the ppa? I
>> never tried the ppa.
>>
>>
>
> pm-utils: /usr/lib/pm-utils/sleep.d/55NetworkManager
>
> do you have pm-utils installed? why not?
>
> - Alexander
>
>

[Jack Deslippe (jdeslip)]

Ok. I found that there was a file called 10NetworkManager in that directory. I got rid of it and replaced with the new 55NetworkManager (and did chmod +x on it). It seems to be working. I have suspended quite a few times and the wireless network has come back each time (in record time actually).

[Benjamin Kraus (ben-benkraus)]

I just made the changes you suggested. I did *not* change the name of the file (it is still 10NetworkManager). I rebooted and so far so good. However, as the problem is sporadic, I'll post an update in a couple days to say whether the problem comes back.

[Joel Goguen (jgoguen)]

I'm using the stock package in Jaunty, and this seems to fix the issue. I had to change the command to dbus-send (instead of dbus_send...is that a typo in the script or a change made in Jaunty?) but I haven't had this problem in the 2 weeks since you posted the script.

[Benjamin Kraus (ben-benkraus)]

As promised, this is an update to say that I haven't had any problems since updating to the new pm-utils script posted by Alexander (a little over one week ago).

[Alexander Sack (asac)]

On Tue, Feb 17, 2009 at 11:06:23PM -0000, jdeslip wrote:
> Ok. I found that there was a file called 10NetworkManager in that
> directory. I got rid of it and replaced with the new 55NetworkManager
> (and did chmod +x on it). It seems to be working. I have suspended
> quite a few times and the wireless network has come back each time (in
> record time actually).
>

OK, are you running hardy or intrepid?

 - Alexander

[Bart Samwel (bart-samwel)]

I've been running with the changed 55NetworkManager file for a couple of days now, and it's not working properly for me.

Two symptoms:

Once I got a hang on resume, which is new. Perhaps there should be a timeout on the dbus-send call? Or better, perhaps the call on resume should be async, while the call on suspend should be sync!

Anyway, I also got a crash report for NetworkManager at that same time. I reported it, can't find the bug report now since apparently Launchpad has not connected it to me. :-/

The last time I resumed I got both a crash report for NetworkManager, plus I had to do a "sudo invoke-rc.d NetworkManager restart" to get networking back up. The fix is probably still correct, I may be suffering from a different problem (Samsung NC10 netbook).

[Michael Doube (michael-doube)]

I've tried 55NetworkManager script (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/291062/comments/34) on a Hardy installation, with interesting results:

If I haven't moved during a suspend-resume cycle, I get wifi back quickly, as my notebook remains associated with my home AP. But if I suspend at home (homeAP) then go to work (workAP; 1 hour away on the Tube), I resume and am still 'associated' with homeAP. To get workAP to show up in NM's list and to associate with workAP, I have to R-click->disable wireless and enable wireless. homeAP is still in the list for a couple of minutes.

So it seems that the behaviour is to assume that if we were associated with an AP at suspend then we are still associated at resume. Perhaps that is fair, but it would be worth doing an AP scan soon after resume to check if this is true, and if not, associate with an AP that is actually there.

[Alexander Sack (asac)]

fix will go into pm-utils package. Remember: if you just have problems with "scan results list", this is not your bug. this bug is solely about networkmanager having "enable networking" unchecked after resume.

[Alexander Sack (asac)]

not a NM issue.

[Launchpad Janitor (janitor)]

This bug was fixed in the package pm-utils - 1.2.2.4-0ubuntu3

---------------
pm-utils (1.2.2.4-0ubuntu3) jaunty; urgency=low

  * debian/patches/90-nm-proper-wakeup.patch,series: fix LP: #291062 - "MASTER
    Network Manager sometimes has "enable networking" unchecked/disabled when
    resuming from suspend"; problem was that NetworkManager did not get a dbus
    signal on wake up; underlying issue is that dbus-send randomly fails if
    you dont wait for confirmation of message delivery; using --print-reply
    seems to do the trick.

 -- Alexander Sack <email address hidden> Wed, 18 Mar 2009 21:27:11 +0100

[Alexander Sack (asac)]

no NM issue.

[Da CalebMan (caleb-trevatt)]

Hey Alex,

Actually, it's not that,

No matter what I do, I can't turn it back on, right click> enable wireless/enable networking, nothing works!
I've tried everything even rebooting! But it only works after rebooting twice! On the first try, it says USB device not recognized, (I use a wireless usb card) it then continues showing the same error all the time! But with different numbers in front...

What do I do?

> Date: Mon, 20 Jul 2009 08:03:41 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 291062] Re: MASTER - Network Manager sometimes has "enable networking" unchecked/disabled when resuming from suspend
>
> ** Changed in: pm-utils (Ubuntu Intrepid)
> Status: Triaged => Won't Fix
>
> --
> MASTER - Network Manager sometimes has "enable networking" unchecked/disabled when resuming from suspend
> https://bugs.launchpad.net/bugs/291062
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “network-manager” package in Ubuntu: Invalid
> Status in “pm-utils” package in Ubuntu: Fix Released
> Status in network-manager in Ubuntu Intrepid: Invalid
> Status in pm-utils in Ubuntu Intrepid: Won't Fix
> Status in network-manager in Ubuntu Jaunty: Invalid
> Status in pm-utils in Ubuntu Jaunty: Fix Released
>
> Bug description:
> Binary package hint: network-manager
>
> I've noticed that every few suspends, Network Manager will disable networking for no apparent reason. R-clicking the icon and checking "Enable networking" turns it back on, but Joe the User isn't going to realise what's going on. Hardware is a mostly stock Eee PC 701 (Celeron 630MHz, 4GB SSD, Atheros AR5007) with 2GB of RAM, running current Intrepid as of 8:18 AM, October 30 2008 (EDT)

_________________________________________________________________
Share your memories online with anyone you want.
http://www.microsoft.com/indonesia/windows/windowslive/products/photos-share.aspx?tab=1

[Alexander Sack (asac)]

On Mon, Jul 20, 2009 at 09:08:42AM -0000, Da CalebMan wrote:
>
> Hey Alex,
>
> Actually, it's not that,
>
> No matter what I do, I can't turn it back on, right click> enable wireless/enable networking, nothing works!
> I've tried everything even rebooting! But it only works after rebooting twice! On the first try, it says USB device not recognized, (I use a wireless usb card) it then continues showing the same error all the time! But with different numbers in front...
>
> What do I do?
>

When changing the dbus-send lines in
/usr/lib/pm-utils/sleep.d/55NetworkManager to "dbus_send --print-reply
..." (e.g. adding the "--print-reply") doesn't help then you most
likely see a driver bug (not this bug!!). Usually installing the
linux-backport-modules-xxx package is a firest thing to tr as it might
have newer drivers for your hardware; if installing that and rebooting
still does not help, then file a bug against the linux package.

If you dont run the latest stable ubuntu release, you could also try
to upgrade to it.

 - Alexander

[Jerry (jerry-redhat-bugs)]

Description of problem:
Networking is disabled by state file after power loss drained laptop battery

Version-Release number of selected component (if applicable):
NetworkManager-0.8.0-7.git20100422.fc13.i686

How reproducible:
always

Steps to Reproduce:
1.login to KDE on laptop
2.disconnect power, and let battery die
3.plugin power and boot - no network.

Actual results:
no network management

Expected results:
network management

Additional info:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571331

Note in step 3. above there are actually two boots as the resume from power mgmt suspend never works for me - I force power off and restart.

[Oded (oded-redhat-bugs)]

I have the same problem after trying to recover from a failed suspend.

Removing the state file at /var/lib/NetworkManager and restarting NetworkManager solved the problem for me.

[Justin (justin-redhat-bugs)]

Same issue here on a Dell Studio 1558, 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35), NetworkManager-0.8.0-13.git20100509.fc13

[Joel (joel-redhat-bugs)]

Additional evidence:

I had this happen to me, apparently when my daughter accidentally hit the sleep button on the keyboard or selected hibernate instead of shutdown from the shutdown menu.

The file mentioned above,

/var/lib/NetworkManager/NetworkManager.state

shows the wired network disabled and the wireless enabled.

The box is a desktop, by the way, not a laptop. No battery. No wireless hardware of any sort. 32 bit, single CPU Sempron. (Should I attach a dmesg?)

Oh, and it's running Fedora 12.

Editing the file instead of deleting it also seems to unclog the networking stuff.

[Dan (dan-redhat-bugs)]

*** Bug 592505 has been marked as a duplicate of this bug. ***

[Dan (dan-redhat-bugs)]

*** Bug 552233 has been marked as a duplicate of this bug. ***

[Richard (richard-redhat-bugs)]

When this symptom has happened to me, the following command instantly fixes it:
    nmcli nm wakeup

The circumstances seem to be that NM sets NetworkingEnabled to false in the /var/lib/NetworkManager/NetworkManager.state file but the situation can arise where NM cannot reset it.

My guess is that this flag is set at suspend time (and of course at 'nmcli nm sleep' time as well). Further, I guess that NM expects a 'suspend' to be followed by a 'resume', which should reset this flag to be NetworkingEnabled=true. But if the latter fails, as it stands manual intervention is reqired.

The failure can occur in at least these two ways: the hardware's suspend function is broken and a power-on reboot is required, and the battery discharges and a power-on reboot is required. The NetworkingEnabled=false flag remains set in these cases, and manual intervention is required. But a naïve user is at a complete loss what to do. Even sophisticated users, e.g., helpers on the #fedora channel of freenode, are at a loss, as I've seen. NM should perhaps set the flag to true when freshly started?

What are the exact and complete semantics of this NetworkingEnabled=false flag?

Is there a valid case where a freshly started NetworkManager service can expect NetworkingEnabled=false to be the proper setting? If there is, could a freshly started NM pop up a graphic window asking the user if enabling was okay?

[Jirka (jirka-redhat-bugs)]

(In reply to comment #6)
> When this symptom has happened to me, the following command instantly fixes it:
> nmcli nm wakeup

Yeah, this pokes NM to wake up via D-BUS.
The same effect can be reached by:
1. right clicking nm-applet and checking "Enable Networking"
2. directly via D-Bus call, e.g. with dbus-send:
dbus-send --system --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Sleep boolean:false

>
> The circumstances seem to be that NM sets NetworkingEnabled to false in the
> /var/lib/NetworkManager/NetworkManager.state file but the situation can arise
> where NM cannot reset it.
>
> My guess is that this flag is set at suspend time (and of course at 'nmcli nm
> sleep' time as well). Further, I guess that NM expects a 'suspend' to be
> followed by a 'resume', which should reset this flag to be
> NetworkingEnabled=true. But if the latter fails, as it stands manual
> intervention is reqired.
>
The flag is set by
/usr/lib64/pm-utils/sleep.d/55NetworkManager script when suspending. The same script is responsible for waking NM up on resume. But when resume fails, of course, the flag is not set to true again.
The whole problem is that suspend/resume should not reuse NetworkingEnabled flag, but it does at present. It's planned to change that in the future, though (see the duped bugs and some others on the issue).

> The failure can occur in at least these two ways: the hardware's suspend
> function is broken and a power-on reboot is required, and the battery
> discharges and a power-on reboot is required. The NetworkingEnabled=false flag
> remains set in these cases, and manual intervention is required. But a naïve
> user is at a complete loss what to do. Even sophisticated users, e.g., helpers
> on the #fedora channel of freenode, are at a loss, as I've seen. NM should
> perhaps set the flag to true when freshly started?
>
> What are the exact and complete semantics of this NetworkingEnabled=false flag?
>
The state file was introduced to retain setting during restarts. So that you can set the flags and see the same stuff over reboots.

> Is there a valid case where a freshly started NetworkManager service can expect
> NetworkingEnabled=false to be the proper setting? If there is, could a freshly
> started NM pop up a graphic window asking the user if enabling was okay?

There are valid cases.
You may manually disable wireless or whole networking (e.g via right-clicking nm-applet). And you want to have the same state after reboot, of course.
I am sure about a pop-up. I think that disabled state is already indicated via nm-applet icon. See attachment.

[Jirka (jirka-redhat-bugs)]

Created attachment 415400
nm-applet: NetworkManager in sleep state

[Oded (oded-redhat-bugs)]

The main problem with using nm-applet for waking up NetworkManager, is that if you use KDE then you don't have nm-applet, you have knetworkmanager which doesn't have that features.

When NetworkManager is sleeping, knetworkmanager shows a disabled menu entry saying "networking is disabled" and there is no way to enable it.

[Jirka (jirka-redhat-bugs)]

This is actually a deficiency of knetworkmanager.
I've submitted a patch for knetworkmanager to fix that:
https://bugs.kde.org/show_bug.cgi?id=238325

Btw, you can use nm-applet in KDE without any problem (I do that myself).

[Jirka (jirka-redhat-bugs)]

Created attachment 415484
knetworkmanager with added "Enable networking" checkbox

knetworkmanager with enable check boxes when NetworkManager is sleeping.

[Dan (dan-redhat-bugs)]

Upstream NetworkManager commits that fix this bug:

ee3ece9dac985034c5c1f81a6769b40fd7856579 (0.8.1)
fa70542c618665cf203a2b71fa0e504f759f7902 (master)

still need to hook the applet's Enable checkbox up to the new bits in a separate commit.

[Dan (dan-redhat-bugs)]

5ca1a9d546be81b54e57d525b54ff92597de6115 (0.7.x)

[Jerry (jerry-redhat-bugs)]

(In reply to comment #12)
> Upstream NetworkManager commits that fix this bug:
>
> ee3ece9dac985034c5c1f81a6769b40fd7856579 (0.8.1)
> fa70542c618665cf203a2b71fa0e504f759f7902 (master)

This is in my list of bugs to "Retest", but I see no way to do so. Please update accordingly. Thanks!

[Aigars Mahinovs (aigarius)]

Getting a very similar problem here in lucid - after suspend and resume the NetworkManager is disabled, if I enable it (by checking the 'enable networking' or by running 'dbus-send --print-reply --system --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.wake' it starts working again. A sure way to replicate this would be to suspend and then remove the laptops power supply and battery to force a shutdown, then when starting back up NetworkManager will be disabled. Maybe NM sleep status should be reset during boot?

[Oded Arbel (oded-geek)]

this is the same issue as explained in RedHat bug #589108 (linked):

 - when you suspend, network manager disables networking (otherwise there may problem suspending, at least as I understand it).
- Unfortunately it uses the same flag as what the user interface is using to disable networking when requested by the user.
- When the system loads after a failed resume, the flag stays on and Network Manager does not distinguish between "user asked us to stay off, so we'll stay off until the user says otherwise" and "we needed to go off for suspend, but resume failed and we need to enable networking".
- This will hopefully get fixed in the near future by adding the required extra flag in network manager for managing the suspend/resume state separately.

[Jerry (jerry-redhat-bugs)]

(In reply to comment #10)
> This is actually a deficiency of knetworkmanager.
> I've submitted a patch for knetworkmanager to fix that:
> https://bugs.kde.org/show_bug.cgi?id=238325
>
> Btw, you can use nm-applet in KDE without any problem (I do that myself).

That is a different problem, and solution, so I've cloned this as Bug #598765.

[Fedora (fedora-redhat-bugs)]

NetworkManager-0.7.2.997-2.git20100609.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/NetworkManager-0.7.2.997-2.git20100609.fc11

[Dan (dan-redhat-bugs)]

*** Bug 573799 has been marked as a duplicate of this bug. ***

[zorblek (zorblek)]

I am still experiencing this bug with the latest updates in Ubuntu 10.04 on a Dell XPS M1210.