Bug 12852

Summary:	upgrade from mga4 to cauldron for networkmanager causes wifi connection failure
Product:	Mageia	Reporter:	Joseph Wang <joequant>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	Normal	CC:	marja11, nic, olav, thierry.vignaud
Version:	Cauldron	Keywords:	NEEDINFO, Triaged
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	networkmanager-0.9.9	CVE:
Status comment:

Description Joseph Wang 2014-02-22 15:01:52 CET

Description of problem:

When I upgrade my networkmanager from Mageia 4 to cauldron, the wifi connection does not work on boot.  I get a message saying that I need to type in root for any system changes, if I do that I get another dialog saying that networkmanager cannot connect to wifi.  The second dialog does not let me enter a password and the only option is cancel.

If I kill wpa_supplicant enough times I can sometimes get this to work.

Works fine with NM 0.9.8


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

NM 0.9.8

How reproducible:

Consist.


Steps to Reproduce:
1. Upgrade networkmanager to latest cauldron
2. use systemctl to set up network manager
3. See behavior noted


Reproducible: 

Steps to Reproduce:

Manuel Hiebel 2014-03-03 18:33:20 CET

Keywords: (none) => Triaged
CC: (none) => olav, thierry.vignaud
Source RPM: networkmanger-0.9.9 => networkmanager-0.9.9

Comment 1 Marja Van Waes 2015-04-06 22:45:32 CEST

Is this bug still valid for upgrading to 5bet3 or 5rc?

If so, please set it to block bug 15637 (the mageia 4 -> 5 upgrade issues tracker)

CC: (none) => marja11

Comment 2 Samuel Verschelde 2015-06-06 01:18:23 CEST

Joseph, could you answer comment #1?

Keywords: (none) => NEEDINFO

Comment 3 Nic Baxter 2016-01-04 04:05:26 CET

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
CC: (none) => nic
Resolution: (none) => OLD