Bug 221393 - knetworkmanager should try to wake up NetworkManager if it is not available
Summary: knetworkmanager should try to wake up NetworkManager if it is not available
Status: RESOLVED FIXED
Alias: None
Product: Network Management
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-05 14:22 UTC by Dan
Modified: 2010-10-09 20:22 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Dan 2010-01-05 14:22:28 UTC 
Version:           svn (using KDE 4.3.4)
Compiler:          gcc 4.3.4 
OS:                Linux
Installed from:    Compiled From Sources

If knetworkmanager cannot talk to NetworkManager it simply says "Networking information not available". 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
Comment 1 Orion Poplawski 2010-05-04 22:15:10 UTC 
I'm not sure it should start it.  But it definitely should reconnect if NM is restarted - which it currently does not.  Let me know if you want a separate bug for that.
Comment 2 Rex Dieter 2010-05-05 00:13:58 UTC 
Fwiw, nm-applet reconnects when nm service is restarted, so doing as orion suggested would help bring knm one step closer to parity.
Comment 3 Rex Dieter 2010-10-09 20:22:17 UTC 
Support for this was added recently, since 2010-08-30 at least, a possible side effect of bug #238325