Bug 5948 - network Center reporting wrong and bizarre information about the ssids available, and the connection status
Summary: network Center reporting wrong and bizarre information about the ssids availa...
Status: RESOLVED DUPLICATE of bug 3888
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-17 08:40 CEST by w unruh
Modified: 2013-05-08 09:01 CEST (History)
1 user (show)

See Also:
Source RPM: drakx-net-1.12-1.mga2
CVE:
Status comment:


Attachments
screenshot after connection to lynksys SSID Note no indication of that connection (63.93 KB, image/png)
2012-05-18 00:47 CEST, w unruh
Details
screenshot after connection and after closing and then reopening network manager (63.50 KB, image/png)
2012-05-18 00:50 CEST, w unruh
Details

Description w unruh 2012-05-17 08:40:00 CEST
Description of problem:The report of the state of the network connection in the network center is wrong and bizarre. I had three ssid's reported. I selected one and pressed connect. The wireless connected, but the button remained at "connect" as if I was not connected, and there was no indication that there was any connection on the left side of the line. However on one of the other essids there was the green counterclockwise circle indicating that tghere was a connection to that other essid. I closed the netword center, and reopened it. I now had the globe on the left side to indicate a connection, but suddenly the security type of that essid changed from open (a green unlocked lock) to WEP (an orange lock)
(of course the essid had not changed at all. )




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


How reproducible: a few times. 




Steps to Reproduce: See above. 

Computer is a Panasonic Toughbook CF-S10 with and Intel 6205 wireless card (iwlwifi driver)
Comment 1 w unruh 2012-05-17 08:42:28 CEST
PS version of Mageia is the Mageia One release candidate downloaded on May 14 and installed and then the system was updated on May 15.
Comment 2 Manuel Hiebel 2012-05-17 10:06:17 CEST
seems a  duplicate

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

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

Comment 3 w unruh 2012-05-18 00:47:10 CEST
Created attachment 2335 [details]
screenshot after connection to lynksys SSID Note no indication of that connection
Comment 4 w unruh 2012-05-18 00:49:05 CEST
This is not a duplicate It is for Mageia 2 live CD which was installed on May 15 and then updated. Thus this should be the Mageia 2 RC as of May 15.

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

Comment 5 w unruh 2012-05-18 00:50:58 CEST
Created attachment 2336 [details]
screenshot after connection and after closing and then reopening network manager
Comment 6 w unruh 2012-05-18 00:54:18 CEST
I called it Mageia One because Mandriva and some at Mageia call the live CD by the name ONE.(note spelled out, not digit)
Comment 7 Manuel Hiebel 2012-05-18 02:03:50 CEST
(In reply to comment #5)
> Created attachment 2336 [details]
> screenshot after connection and after closing and then reopening network
> manager

even if it's in mageia2/cauldron, its the same origin bug anywhy...

Assignee: bugsquad => mageia

Comment 8 Marja Van Waes 2012-05-26 13:08:40 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 9 w unruh 2012-05-26 15:20:36 CEST
Valid for Mageia 2.

Version: Cauldron => 2

Sander Lepik 2012-05-26 16:24:52 CEST

Keywords: NEEDINFO => (none)
CC: (none) => sander.lepik

Comment 10 Marja Van Waes 2012-07-06 15:05:10 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 11 w unruh 2013-05-08 09:01:37 CEST
This is a duplicate of 3888 which is now fixed. (/usr/sbin/mdv-network-event should have had org.mageia rather than com.mandriva as the dbus signal name.)

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

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


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