Bug 1187 - perpetual unconnect on wifi
Summary: perpetual unconnect on wifi
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-07 12:38 CEST by y mun
Modified: 2011-05-08 15:16 CEST (History)
2 users (show)

See Also:
Source RPM: networkmanager-0.8.4.0-3.mga1.src.rpm
CVE:
Status comment:


Attachments

Description y mun 2011-05-07 12:38:55 CEST
Description of problem:
perpetual wifi unconnect with NetworkManager 


How reproducible:
Ever

Steps to Reproduce:
1. Install NetworkManager
2. Launch NetworkManager 
3. See

It's seems to be not a NetworkManager trouble. I don't, and never, have this trouble on my Fedora.

Please remove libnm-settings-plugin-ifcfg-mdv.so from Mageia NetworkManager.

As 'mandriva-plugin' say : "This is not a production-ready version, nor it is officially supported as of now. (blabla) - at least in theory - it should work (blabla)" Maybe a trouble with nm_inotify_helper_get() Dont know... 

Simply please drop it for Mageia stable.
Comment 1 y mun 2011-05-07 20:55:23 CEST
Not only libnm-settings-plugin-ifcfg-mdv.so

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

Comment 2 John Balcaen 2011-05-08 15:11:16 CEST
You should simply edit networkmanager configuration to not use this plugin.

CC: (none) => balcaen.john

Comment 3 Frank Griffin 2011-05-08 15:16:40 CEST
Yesterday, all of a sudden NM couldn't activate my RTL8192SE wlan0.  Comparing to an old working system, I found that in /etc/sysconfig/network-scripts/wireless.d, the script for the ESSID was missing WIRELESS_WPA_REASSOCIATE=no.  Adding it fixed things.

I also noticed that WIRELESS_WPA_DRIVER=wext wasn't there, but when I added it, ifcfg-mdv segfaulted.  I'm thinking maybe both of these were removed because of the segfault.

CC: (none) => ftg


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