Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#27323 - [NetworkManager] No sync of NM wifi state and wifi led

Attached to Project: Arch Linux
Opened by Alexandr Fedorchuk (KOL-93) - Tuesday, 29 November 2011, 08:46 GMT
Last edited by Allan McRae (Allan) - Saturday, 28 April 2012, 14:58 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ionut Biru (wonder)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
There are no sync of wifi state in NM with led state.(I don't know about i686)
Additional info:
* package version(s): networkmanager == 0.9.*, kdeplasma-applets-networkmanagement == 1:*.*, linux == 2.6 - 3.1.*
* config and/or log files etc:
When changing state of wifi by NM, there are no sync with led state.(only NM state is changed)
When changing state on wifi by led, it change wifi state of led and of NM to oopposites with no checks
and kernel says only this 'iwlagn 0000:05:00.0: RF_KILL bit toggled to disable radio.' or this 'iwlagn 0000:05:00.0: RF_KILL bit toggled to enable radio.'

Steps to reproduce:
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 28 April 2012, 14:58 GMT
Reason for closing:  No response
Additional comments about closing:  Upstream issue. Should be repprted there.
Comment by Alexandr Fedorchuk (KOL-93) - Tuesday, 29 November 2011, 08:50 GMT
HW:
Notebook: Acer Aspire 5739G
CPU: Intel Core 2 Duo T6600
RAM: 4Gb
VGA: Nvidia GT240M
WiFi: Network controller: Intel Corporation WiFi Link 5100
PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)

If need more information, just say.
Comment by Ionut Biru (wonder) - Tuesday, 29 November 2011, 10:10 GMT
is either a bug in the kernel or nm. try to report this upstream
Comment by Alexandr Fedorchuk (KOL-93) - Tuesday, 29 November 2011, 11:49 GMT
I think it's a bug of NM. Because when NM is stopped all is ok. But I'm not sure.
Comment by Jelle van der Waa (jelly) - Sunday, 18 December 2011, 17:12 GMT
Did you contact the networkmanager developers already? They have a bugtracker

Loading...