Bug 552862

Created attachment 350225 [details]
NM status

Created attachment 350226 [details]
KDE message

Sometimes after boot NetworkManeger not work and gives a message "NetworkManger is disabled". Installed all the updates.

KDE 4.3.5

Created attachment 350289 [details]
messages log

Created attachment 350292 [details]
NM log

If knetworkmanager cannot talk to NetworkManager it simply says that. It should rather try to activate NetworkManager, which can be done issuing the following command:

dbus-send --system --dest=org.freedesktop.NetworkManager
/org/freedesktop/NetworkManager org.freedesktop.NetworkManager.wake


Can you try to connect with another applets: nm-applet or cnetworkmanager?

http://ru.opensuse.org/KNetworkManager
http://userbase.kde.org/NetworkManagement_(ru)

2 bugs then: 

1) NM should not be asleep on resume

2) KNM should not just show the 'NM is disabled' dummy menu entry when NM is asleep when KNM starts up, but show the 'Enable networking' entry too to wake NM.

>>dbus-send --system --dest=org.freedesktop.NetworkManager
/org/freedesktop/NetworkManager org.freedesktop.NetworkManager.wake


This console command not helped

Device info:

03:00.0 Ethernet controller [0200]: Broadcom Corporation BCM4401-B0 100Base-TX [14e4:170c] (rev 02)
        Subsystem: Dell Device [1028:01f1]                                                         
        Flags: bus master, fast devsel, latency 64, IRQ 17                                         
        Memory at f9bfe000 (32-bit, non-prefetchable) [size=8K]                                    
        Capabilities: [40] Power Management version 2                                              
        Kernel driver in use: b44  

0c:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] (rev 01)
        Subsystem: Dell Wireless 1390 WLAN Mini-Card [1028:0007]
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at f9ffc000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 2
        Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Express Legacy Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel <?>
        Kernel driver in use: b43-pci-bridge

NetworkManedger    - 0.7.1_git20090811-4.2
NetworkManedger-kde4 - 0.9.svn1043876-4.11
NetworkManedger-openvpn - 0.7.1-2.4.1

How's this working in newer versions of KDE?

Thanks

I have the same problem in opensuse 11.3 FC1 when I suspend to RAM.

Performing the command: dbus-send --system --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.wake

..from a root prompt solves the problem.

Info provided

Maybe same problem here.

Notebook doesn't wake up from suspend-to-ram (although i don't know if that is related to networkmanager).

After hardresetting (turn power off) and restart, nm-tool shows

"State: asleep"

Following a hint in http://forums.opensuse.org/english/get-help-here/pre-release-beta/439460-11-3-m7-network-manager-broken.html#post2182518, the command


"solid-network set networking enabled"

provides on a shell as the user that is currently logged into the graphical system, wakes up nm again.

Hope this helps.

Regards.

Same here with 11.3 RC2. How can we debug what causes NM to not be active anymore? A normal user should not have to mess with the command line after resuming or some other actioon that makes NM fail. Especially since not even rebooting helps.

For me nm-applet fails as well, so it's not a knetworkmanager issue.

Just hit this issue, however:

killing knetworkmanager and starting nm-applet works just great.
right-click on nm-applet and choose "Enable Networking" (which is a checkbox and is unchecked).  After that, everything works peachy.

I see this as two issues:

1. networkmanager asleep and not woken up (indeed, even after *failed* suspend-to-ram!)

2. knetworkmanager has no way to /enable/ networking once it is disabled, but nm-applet does. 

Happened 15 minutes apart on two totally different machines, a laptop (coming back from failed suspend-to-ram) and a *workstation* (coming back after suspend-to-disk).

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

(In reply to comment #14)
> Following a hint in
> http://forums.opensuse.org/english/get-help-here/pre-release-beta/439460-11-3-m7-network-manager-broken.html#post2182518,
> the command
> 
> 
> "solid-network set networking enabled"

Just ran into this problem, happened after a failed s2ram attempt.  Neither a reboot nor restart of networkmanager fixed this.  Disabling networkmanager and using ifup did work.  The above quited command did in fact kick networkmanager back into shape and all is good again.

Running 11.3, updated with all current patches from the channel.

Same problem here...

Had opensuse 11.2 with latest KDE 4.4.95
I upgraded to 11.3 Now if have serious trouble with my network!
I'm using KDE 4.4 stable (opensuse buildservice repository)

I always have the problem at startup, not only after standby or sleep.
when networkmanager is selected in YAST
ETH0 is not working 
WLAN0 is not working

with ifup selected
my ETH0 is working immediatly
WLAN0 is available but needs authentication (iwlist scan works)

rcnetwork restart does not work!

Only thing that does work for nog is the following command
"solid-network set networking enabled" (as root)
then everything works as should and like it working on opensuse 11.2

Is there a way to make this command permanent over a reboot?

Same problem here on a Samsung NC10. Fresh install from KDE-LiveCD (11.3 Final)+all updates.
After a failed resume from a suspend to RAM, knetworkmanager could not be re-enabled.
The dbus-send command mentioned in Comment 12 worked for me but that's not really very user-friendly. The frustrating bit is that even a reboot does not solve this.

A fix for knetworkmanager is in the pipeline. Please be patient.

I tried this today on my Samsung NC10, after installing the recommended update to NetworkManager (0.8-7.4-i586 to 0.8-8.1.1-i586 from openSUSE-11.3-Update).

Result: NetworkManager connected with no problem, both after Hibernate (suspend to disk), and Sleep (suspend to RAM).

Conclusion: this has now been fixed and is a duplicate of 585433

Hint: if you are stuck with a disabled network, installing the update will not unblock it. You have to enable networking in 

/var/lib/NetworkManager/NetworkManager.state

If you find this:

[main]
NetworkingEnabled=false
WirelessEnabled=true
WWANEnabled=true

As root, change it in an editor of your choice to:

/var/lib/NetworkManager/NetworkManager.state

[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true

I tried this today on my Samsung NC10, after installing the recommended update to NetworkManager (0.8-7.4-i586 to 0.8-8.1.1-i586 from openSUSE-11.3-Update).

Result: NetworkManager connected with no problem, both after Hibernate (suspend to disk), and Sleep (suspend to RAM).

Conclusion: this has now been fixed and is a duplicate of 585433

Hint: if you are stuck with a disabled network, installing the update will not unblock it. You have to enable networking in 

/var/lib/NetworkManager/NetworkManager.state

If you find this:

[main]
NetworkingEnabled=false
WirelessEnabled=true
WWANEnabled=true

As root, change it in an editor of your choice to:

/var/lib/NetworkManager/NetworkManager.state

[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true

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

You should test with _failed_ suspends etc.

I tested the following:
- suspend to RAM
- remove batteries (such that blue light on NC10 stops flashing)
- put batteries back in and start the machine
- instead of resuming, it now boots normally, because it has lost the RAM contents

Is that what you mean by failed suspend?
If so, I can confirm it now works, i.e. NetworkManager connects correctly after the new boot, whereas previously I regularly had a problem on resume, whether failed or not.

On Acer Aspire one 1551 (http://www.linlap.com/wiki/acer+aspire+1551) knetworkmanager is inactivated after successful resume from suspend to ram/disk.
Icon shows Unavailable upon left click and Networkmanager disabled on right click.
Activity can be restored by killing knetworkmanager and starting a new instance.

"dbus-send" ... does NOT work
"solid-network set networking"... does NOT work

Note: In this machine the wireless card is not active (light is off) after boot, it is not controllable by hardware button but it can be activated via knetworkmanager (turns light on). On resume, card is not active, restarting knetworkmanager shows that wireless is not active, status can be toggled, but light does not come on, now the hardware button is needed to turn it on, but it would not toggle the status on knetworkmanager, so both are needed.
Maybe all this has something to do with the need to pass noapic to the kernel on boot?

Making a wired connection will also activate the disabled knetworkmanager (no kill required). However this option is not always available :)

This bug is still present in the WHERE 4.6

On my DELL Inspiron 1520 knetworkmanager corresponding icon does not appear in the tray at boot time, run knetworkmanager not get help only a few rebooting

Works for me with 12.1. If you still have problems please reopen.