Bug 3799 - cannot connect to wireless network using net_applet: constantly switches crda domain (to the same value)
Summary: cannot connect to wireless network using net_applet: constantly switches crda...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard: MGA2TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-17 21:00 CET by Christian Lohmaier
Modified: 2015-04-19 14:13 CEST (History)
1 user (show)

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


Attachments

Description Christian Lohmaier 2011-12-17 21:00:21 CET
GNOME Europe1 live iso of alpha2

Description of problem:
as crda is ignored/set to US by default, click on net-applet icon in the lower-right of the screen â network dialog comes up â configure button at the bottom â set CRDA domain to "DE" for example.

Now refresh the network list to make those networks available that are using frequencies that are restricted in US, setup a connection to your network and try to connect.

The connection attempt fails, and watching /var/log/messages you see the reason:
It keeps seeting the CRDA domain to DE ~ every second

Dec 17 13:52:12 localhost kernel: cfg80211: Calling CRDA for country: DE
Dec 17 13:52:12 localhost kernel: cfg80211: Regulatory domain changed to country: DE
[frequency table]

over and over again. When using network-manager instead, this problem does not occur.
Manuel Hiebel 2011-12-18 20:57:27 CET

Assignee: bugsquad => mageia
Source RPM: (none) => drakx-net

Comment 1 Marja Van Waes 2012-05-12 10:06:06 CEST
Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher.

Is this one still valid for Mageia 2 rc?

If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
If it wasn't assigned correctly, please assign back to Bug Squad and explain.
Comment 2 Christian Lohmaier 2012-05-17 19:29:40 CEST
still the same with the RC.

* boot to mageia 2rc (Europe 1, GNOME)
* netapplet-icon in the lower right
* switch crda-domain to the one that is actually used by the network
* expand wireless-section, click update/wait for the essid to appear
* configure (set password, set to static IP)
* click connect

â connection never succeeds, /var/log/messages shows the constant setting of CRDA domain.

(booting to mageia, setting CRDA-domain using net-applet, and then using network-manager to connect works, but network-manager won't cure the looping crda-setting when you try to connect with net-applet first - i.e. if you try to connect using net-applet, you're stuck in the loop. If you only use net-applet to set the crda-domain, then one can use network-manager to connect)
Comment 3 Marja Van Waes 2012-05-26 13:05:32 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 4 Christian Lohmaier 2012-06-15 14:44:49 CEST
aes it is still valid, the live-iso still exhibits the same problem.
Manuel Hiebel 2012-06-25 05:43:47 CEST

Keywords: NEEDINFO => (none)
Whiteboard: (none) => MGA2TOO

Comment 5 Marja Van Waes 2012-07-06 15:06:06 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 6 Marja Van Waes 2015-04-19 14:13:26 CEST
Sorry, but this bug saw no action since more than 2 yrs ago. 
No cauldron package has stayed the same since then.

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

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


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