FS#29632 - [networkmanager] After update to 0.9.4.0-4 wireless strength fails to show in KDE panel
Attached to Project:
Arch Linux
Opened by Mike Cloaked (mcloaked) - Thursday, 26 April 2012, 21:22 GMT
Last edited by Ionut Biru (wonder) - Saturday, 01 September 2012, 09:26 GMT
Opened by Mike Cloaked (mcloaked) - Thursday, 26 April 2012, 21:22 GMT
Last edited by Ionut Biru (wonder) - Saturday, 01 September 2012, 09:26 GMT
|
Details
Description:
Networkmanager 0.9.2 was working fine with ipw2200 in a Dell D610 running KDE as the desktop - upgrading networkmanager initially to 0.9.4.0-2 failed with ipw2200 until wext was re-enabled in version 0.9.4.0-4 when wireless again worked. However the wireless signal strength indication in the KDE panel did not show at all despite a strong signal. The appearance of the icon can be seen in the attached screenshot image as a "dot" with greyed out arcs above it instead of the arcs showing as bright with the strong signal. Additional info: * package version(s) * config and/or log files etc. The wireless detail listed by iwconfig looks OK despite the networkmanager icon showing incorrectly. eth1 IEEE 802.11bg ESSID:"xxxxxxxx" Mode:Managed Frequency:2.422 GHz Access Point: xx:xx:xx:xx:xx:xx Bit Rate:36 Mb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx Security mode:open Power Management:off Link Quality=86/100 Signal level=-29 dBm Noise level=-90 dBm Rx invalid nwid:0 Rx invalid crypt:1 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:2 sensitive data above have been replaced with "x"s. This appears to be a display bug specifically for the ipw2200 wireless chip since another laptop also running the same setup but with a different wireless chip works without any problem and displays the signal strength correctly at the same physical location. Steps to reproduce: |
This task depends upon
Closed by Ionut Biru (wonder)
Saturday, 01 September 2012, 09:26 GMT
Reason for closing: Fixed
Additional comments about closing: 0.9.4
Saturday, 01 September 2012, 09:26 GMT
Reason for closing: Fixed
Additional comments about closing: 0.9.4
[mike@lapmike2 ~]$ nm-applet
** Message: applet now removed from the notification area
(nm-applet:4863): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed
** Message: applet now embedded in the notification area
Does this output give any useful clues to what is happening?
No icon signal and no showing connected network on extended panel info. Just like on your pictures.
Please developers fixing this issue. Thank you very much.
kdeplasma-applets-networkmanagement 1:0.9.0.2-1
systemd-tools 185-1
upower 0.9.16-1
kdelibs 4.8.3-3
linux 3.4-1
I believe it started after a recent update which included kdelibs
gene/
gene/
gene/
It seems to be intermittent.
linux 3.4.2-2
networkmanager 0.9.4.0-5
kdeplasma-applets-networkmanagement 1:0.9.0.2-1
ipw2x00 supports minimal bits of the nl80211 API, basically just capability
reporting. It does not actually support anything useful with nl80211, so we
should still really be using WEXT with it. Arguably the switch for nl80211
shouldn't have been thrown for ipw2x00 until it was actually usable with
nl80211, but it was.
So NM detects that the driver supports nl80211 and then asks for the associated
AP, signal strength, etc using nl80211, which the driver doesn't actually
support. NM needs to match the logic that wpa_supplicant uses to determine
whether to fall back to WEXT.
Fix is on the 'wifi-fallback' branch in git.
I wonder if the same issue is now re-appearing in networkmanager 0.9.4.0-6 or if this is a new issue?
0.9.4.0-4 - does not show signal strength
0.9.4.0-5 - show signal strength
0.9.4.0-6 - does not show signal strength again
The 0.9.4.0-5 version was the fixed. Why do you crash signal strength showing in 0.9.4.0-6 ? Please fix it again. Thanks.
(I have to use "pacman -Syu --ignore networkmanager" now to keep 0.9.4.0-5)
linux 3.4.5-1
networkmanager 0.9.4.0-6
kdeplasma-applets-networkmanagement 1:0.9.0.3-1
It is working in networkmanager 0.9.6.0-1 so this bug is resolved now.