Bug 526569

Summary: Network Settings is set to use NetworkManager but this service doesn't start.
Product: [openSUSE] openSUSE 11.1 Reporter: Ladislav Nesnera <nesnera>
Component: NetworkAssignee: E-mail List <gnome-bugs>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: hans, nesnera
Version: Final   
Target Milestone: ---   
Hardware: 64bit   
OS: openSUSE 11.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 527587    
Attachments: screenshot

Description Ladislav Nesnera 2009-07-29 22:16:33 UTC
Created attachment 309135 [details]
screenshot

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090714 SUSE/3.5.1-1.1 Firefox/3.5.1

As you can see at the attached screenshot, knetworkmanager runs but NetworkManagere doesn't and device wlan0 is down. The picture shows state immediately after boot and login to KDE.

Reproducible: Always

Steps to Reproduce:
1. set Network Setup Method to "User Controlled with NetworkManager"
2. reboot and open KDE session
3.
Actual Results:  
I must start NetworkManager manually as a root or set network configuration by command like ip, iwcofnig, dhcpcd

Expected Results:  
Manage network setting only by knetworkmanager.
Knetworkmanager should be notify NetworkManager doesn't work.

KDE: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3)) "release 147"
Linux 2.6.27.25-0.1-default #1 SMP 2009-07-01 15:37:09 +0200 x86_64 x86_64 x86_64 GNU/Linux
Comment 1 Will Stephenson 2009-07-30 12:13:02 UTC
The knetworkmanager UI needs a better indicator when NM is down, the icon is provisional though and will change.  

Reassigning to Network because it is more significant that NM doesn't start after changing network config.
Comment 3 Hans Benker 2010-08-15 10:25:44 UTC
If I understand this correctly, this is a duplicate of 619934.

knetworkmanager now (openSUSE 11.3) indicates if the network is disabled, but it still does not allow the user to easily enable it. This is the issue of 619934.

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