Bug 588849 - knetworkmanager does not re-connect to NetworkManager
knetworkmanager does not re-connect to NetworkManager
Product: Fedora
Classification: Fedora
Component: kde-plasma-networkmanagement (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Rex Dieter
Fedora Extras Quality Assurance
: MoveUpstream
Depends On:
  Show dependency treegraph
Reported: 2010-05-04 13:43 EDT by Orion Poplawski
Modified: 2010-10-09 14:21 EDT (History)
3 users (show)

See Also:
Fixed In Version: 0.9-0.25
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-10-09 14:21:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
KDE Software Compilation 221393 None None None Never

  None (edit)
Description Orion Poplawski 2010-05-04 13:43:18 EDT
Description of problem:

It NetworkManager is restarted, knetworkmanager shows "Networking information is not available" and never re-connects.

Version-Release number of selected component (if applicable):
Comment 1 Rex Dieter 2010-05-04 13:59:16 EDT
OK, though restarting the nm service has always been one of those things I usually recommend:  don't do that!

(yes, I know NetworkManager-gnome aka nm-applet gracefully handles this situation... and knm probably should too).

In short, this is a feature request best sent upstream.
Comment 2 Orion Poplawski 2010-05-04 16:15:54 EDT
I've commented in the upstream bug.  Perhaps not quite the same thing, but related.
Comment 3 Fedora Admin XMLRPC Client 2010-09-11 19:52:03 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 4 Rex Dieter 2010-09-27 12:43:48 EDT
I can confirm this works with 
Comment 5 Orion Poplawski 2010-09-27 13:26:46 EDT
Appears to reconnect fine with knetworkmanager-0.9-0.22.20100830.fc13.kde45.i686 too.

Note You need to log in before you can comment on or make changes to this bug.