Bug 210342

Summary:	knetworkmanager can't control NetworkManager after that's restarted
Product:	Network Management	Reporter:	Tamás Németh <nt1277>
Component:	knetworkmanager	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	salim
Priority:	NOR
Version:	0.9
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Tamás Németh 2009-10-12 18:19:39 UTC

Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    SuSE RPMs

After I restart NetworkManager (by issuing /etc/init.d/network restart in openSUSE 11.2) knetworkmanager still has some knowledge of the network but it's not willing to control it. For example when I plug in my USB GSM modem I get KDE messages that serial port is attached, and knetworkmanager even changes its systray icon to look like a cellular phone, but it informs me that the networking system is down (which is obviously not true since NetworkManager is running again).

All I have to do is to kill knetworkmanager and then start it again. The new knetworkmanager process will be able to manage the network. Gnome's nm-applet doesn't lose control this way.

Comment 1 Will Stephenson 2010-01-05 17:39:19 UTC

I can't reproduce this with trunk or openSUSE 11.2 with updates, please reopen if it's still a problem.

Comment 2 Will Stephenson 2010-01-05 17:40:00 UTC

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