Bug 8900 - on Mageia 3 beta 2 - conflict between mageia network utility and networkmanager when 'allow users to control' is ticked
Summary: on Mageia 3 beta 2 - conflict between mageia network utility and networkmanag...
Status: RESOLVED DUPLICATE of bug 7317
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-30 12:00 CET by sreejiraj eluvangal
Modified: 2013-02-01 01:22 CET (History)
0 users

See Also:
Source RPM: networkmanager drakx-net
CVE:
Status comment:


Attachments

Description sreejiraj eluvangal 2013-01-30 12:00:20 CET
Description of problem:
Fresh install of Mageia 3 beta 2, installed 4 hours ago, and fully updated 3 hours ago. 

Cannot connect to Wifi if 'allow users to control network interface' and 'allow networkmanager to manage the interface' are both ticked in 'configure' option of the interface. 

Version-Release number of selected component (if applicable):

How reproducible: Yes

Steps to Reproduce:
1.Check both 'allow users to control network interface' and 'allow networkmanager to manage the interface' (dhcp enabled)
2.Try to connect to a WPA-PSK network (fails to connect)

COMMENT/HACK

I was able to connect to Wifi by unchecking "allow users to manage interface" box. However, turning the box off does not result in loss of interface management rights for users.
I tried disabling Networkmanager by unchecking the box for the relevant interface. However, at that point, the network was being wrongly identified as WEP type, while it was WPA-PSK.
Comment 1 sreejiraj eluvangal 2013-01-30 12:01:58 CET
"However, turning the box off does not result in loss of interface management rights for users." -- here 'box' means the 'check box', and turning it off means keeping it unchecked (unselected).
Comment 2 Manuel Hiebel 2013-02-01 01:22:01 CET

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


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