Bug 418531

Summary:	Knetworkmanager icon dosen't change after restarting the X environment
Product:	[openSUSE] openSUSE 11.0	Reporter:	Anshul Jain <anshulajain>
Component:	KDE3	Assignee:	Will Stephenson <wstephenson>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P4 - Low	CC:	helmut.schaa, wstephenson
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	openSUSE 11.0
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Screenshot-Knetworkmanager

Description Anshul Jain 2008-08-20 02:28:50 UTC

Hi,
A rather peculiar problem and couldn't put a proper summary above. I have a Thinkpad R61 and running Opensuse 11.0, KDE 3.5.9 with all the latest updates applied. This is regarding KNetworkmanager and the icon at the bottom, the green blob.

I perform the following steps to replicate my problem:-

1. Keep the ethernet cable jacked in. You will notice that the grey blob now turns into a small whitish ethernet like jack, indicating that the network is connected, all is good.

2. Now restart X, Ctrl-Alt-Backspace and login again

3. All this time the ethernet cable is kept jacked in

4. After login, the icon is a green blob, instead of the ethernet jack that I noticed in step 1. 

5. There is little way of knowing, other than looking carefully and noticing that it is a green blob instead of a grey one (when no network is connected)

6. This is observed for the wireless connection too.

-Anshul

Comment 1 Helmut Schaa 2008-08-20 08:54:32 UTC

Could you please attach /var/log/NetworkManager after performing your test case?

Comment 2 Anshul Jain 2008-08-20 10:11:18 UTC

Helmut,
The details of the log are as follows:-

Aug 20 15:28:44 sagarika NetworkManager: <info>  (eth0): carrier now OFF (device state 8)
Aug 20 15:28:44 sagarika NetworkManager: <info>  (eth0): device state change: 8 -> 2
Aug 20 15:28:44 sagarika NetworkManager: <info>  (eth0): deactivating device.
Aug 20 15:28:44 sagarika NetworkManager: <info>  eth0: canceled DHCP transaction, dhclient pid 28652
Aug 20 15:28:44 sagarika NetworkManager: <info>  Clearing nscd hosts cache.
Aug 20 15:28:45 sagarika NetworkManager: <info>  (eth0): carrier now ON (device state 2)
Aug 20 15:28:45 sagarika NetworkManager: <info>  (eth0): device state change: 2 -> 3
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) starting connection 'System eth0'
Aug 20 15:28:45 sagarika NetworkManager: <info>  (eth0): device state change: 3 -> 4
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Aug 20 15:28:45 sagarika NetworkManager: <info>  (eth0): device state change: 4 -> 5
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Aug 20 15:28:45 sagarika NetworkManager: <info>  (eth0): device state change: 5 -> 7
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
Aug 20 15:28:45 sagarika NetworkManager: <info>  dhclient started with pid 29267
Aug 20 15:28:45 sagarika NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Aug 20 15:28:45 sagarika NetworkManager: <info>  DHCP: device eth0 state changed normal exit -> preinit
Aug 20 15:28:53 sagarika NetworkManager: <info>  DHCP: device eth0 state changed preinit -> bound
Aug 20 15:28:53 sagarika NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Aug 20 15:28:53 sagarika NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Aug 20 15:28:53 sagarika NetworkManager: <info>    address 192.168.11.90
Aug 20 15:28:53 sagarika NetworkManager: <info>    netmask 255.255.255.0
Aug 20 15:28:53 sagarika NetworkManager: <info>    gateway 192.168.11.1
Aug 20 15:28:53 sagarika NetworkManager: <info>    nameserver '192.168.0.2'
Aug 20 15:28:53 sagarika NetworkManager: <info>    nameserver '192.168.0.4'
Aug 20 15:28:53 sagarika NetworkManager: <info>    domain name 'india.tejasnetworks.com'
Aug 20 15:28:53 sagarika NetworkManager: <info>    nis domain 'india.tejasnetworks.com'
Aug 20 15:28:53 sagarika NetworkManager: <info>    nis server '192.168.0.8'
Aug 20 15:28:53 sagarika NetworkManager: <info>    nis server '192.168.0.85'
Aug 20 15:28:53 sagarika NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Aug 20 15:28:53 sagarika NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Aug 20 15:28:53 sagarika NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Aug 20 15:28:54 sagarika NetworkManager: <info>  Restarting autofs.
Aug 20 15:28:54 sagarika NetworkManager: <info>  (eth0): device state change: 7 -> 8
Aug 20 15:28:54 sagarika NetworkManager: <info>  Clearing nscd hosts cache.
Aug 20 15:28:54 sagarika NetworkManager: <info>  Policy set (eth0) as default device for routing and DNS.
Aug 20 15:28:54 sagarika NetworkManager: <info>  Activation (eth0) successful, device activated.
Aug 20 15:28:54 sagarika NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.

Comment 3 Helmut Schaa 2008-08-21 13:30:00 UTC

Is the menu entry marked as activated after logging in again?

Comment 4 Anshul Jain 2008-08-26 09:26:40 UTC

Created attachment 235427 [details]
Screenshot-Knetworkmanager

Comment 5 Anshul Jain 2008-09-11 05:44:46 UTC

Hi Helmut,
Any update on how to resolve this?

-Anshul

Comment 6 Helmut Schaa 2008-09-11 06:21:40 UTC

No, not yet. The screenshot from comment #4 does not show any configured connections in the context menu. Is that correct? Did you configure the connections with Yast or with KNetworkManager before?

Comment 7 Anshul Jain 2008-09-11 06:27:48 UTC

Yes, the connections are all configured through Knetworkmanager. As you can see in the screenshot, I'm running a zypper dup on the background. Wouldn't be possible without being connected to the network :) I see this problem in KDE4 too. I'm running the latest KDE4- 4.1.1

-Anshul

Comment 8 Anshul Jain 2008-09-23 11:45:18 UTC

Helmut,
Any updates?

-Anshul

Comment 10 Christian Zoz 2008-10-16 10:27:10 UTC

Anshul, please stay tuned. We are currently very busy, but we will come back to this issue.

Comment 11 Anshul Jain 2008-10-23 04:31:58 UTC

Christian,
Thanks for the reply. I hope that this issue is fixed...as with a ton of other issues for the KNetworkManager. This is by far the weakest app in my KDE3/KDE4 install.

-Anshul

Comment 12 Christian Zoz 2009-07-02 09:46:35 UTC

KNetworkManager for KDE3 is not maintained any longer. Therefore I resolve all bugs that are still open as WONTFIX without looking at each single bug report.
If this bug deals already with KDE4 and is still in progress, then please apologize the mistake and feel free to reopen it.