[Bug 43733] Re: knetworkmanager does not update network strength live

Jocke Andersson jocke at firetech.nu
Wed Jan 2 15:07:51 UTC 2008


I'd like to reopen this bug as it still happens for me in gutsy (also
with the package from hardy ("backported" to gutsy) and upstream SVN). I
also have an ipw3945, and the bug appears both with the ipw3945 and the
iwl3945 drivers.

I did some investigation last night and found that the problem is that
knetworkmanager, as opposed to nm-applet, primarily uses Network Signal
Strength (Signal from NetworkManager is called
"WirelessNetworkStrengthChanged") if available (doesn't evaluate to
false). After "sniffing" the dbus traffic using dbus-monitor, I found
that only the Device Signal Strength (signal "DeviceStrengthChanged")
changes. Since the Network Strength seems to be set during connection
(and then never changes), it doesn't evaluate to false and is therefore
used as the signal strength value.

nm-applet only uses the network strength for the network selection menu
(I.E. network I'm not connected to), and always use the device strength
for the current connection. If I simply comment out the code in the
setStrength() function in knetworkmanager-network.cpp, the strength
updates as it should. However, that way I can't see the strength for
networks I'm not connected to. (I mostly only see one network here, so
it's a bit hard to test, but the testing I have been able to do seems to
agree with my theory.)

This is a bug upstream, but knetworkmanager doesn't seem to be a very
active project, especially since KDE 4's solid has gotten NM support. As
long as (k)ubuntu wants to continue using knetworkmanager (I.E. until
KDE 4 becomes the default), this bug should be fixed.

I'm going to make an attempt to fix the bug using the hardy sources and
then (if successful) attach a debdiff here.


** Changed in: knetworkmanager (Ubuntu)
       Status: Fix Released => Incomplete

-- 
knetworkmanager does not update network strength live
https://bugs.launchpad.net/bugs/43733
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for knetworkmanager in ubuntu.




More information about the kubuntu-bugs mailing list