After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 119471 - N/A when more than one interface
N/A when more than one interface
Status: RESOLVED DUPLICATE of bug 139336
Product: gnome-applets
Classification: Other
Component: wireless-applet
git master
Other Linux
: High normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 108565 133095 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-08-09 10:56 UTC by Fabrice Bellet
Modified: 2014-10-10 14:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Fabrice Bellet 2003-08-09 10:56:11 UTC
Hello,

The wireless applet fails to handle more than one interface properly. The
applet displays N/A in this case.

--- wireless-applet.c.orig      2003-07-23 10:49:45.000000000 +0200
+++ wireless-applet.c   2003-07-21 12:51:20.000000000 +0200
@@ -443,7 +448,7 @@
        if (g_list_length (applet->devices)==1) {
                wireless_applet_set_device (applet,
                                (char*)applet->devices->data);
-       } else {
+       } else if (g_list_length (applet->devices)==0) {
                wireless_applet_update_state (applet,
                                applet->device, -1, -1, -1);
        }
Comment 1 Kjartan Maraas 2003-10-26 17:11:51 UTC
*** Bug 108565 has been marked as a duplicate of this bug. ***
Comment 2 Kjartan Maraas 2003-10-26 17:19:33 UTC
We need to review this and get it in.
Comment 3 Kevin Vandersloot 2003-12-07 15:35:52 UTC
I don't understand how this fixes anything. If the list length is not
1 or 0 then in your patch the applet does not call
wireless_applet_update_state at all. Shouldn't we loop over all the
devices here and call wireless_applet_update_state on each device.
Comment 4 Fabrice Bellet 2003-12-08 10:19:16 UTC
wireless_applet_update_state() is called, as expected, in the while
loop above, if the device name read from the /proc file matches
applet->device, so the applet update is done at this level. The test
following this loop, is used for another purpose : to automatically
set the default device when only one is available from /proc, else to
return "N/A" (meaning here for me, when zero matching device is
available). For any other length (>1), the default device has to be
selected with the GUI.

According to the current code, in the case of two wireless interfaces,
if we suppose that one of them matches applet->device,
wireless_applet_update_state() gets called successfully in the while()
loop for this device. And when exiting from the loop, this update is
overwritten because g_list_length()==2. 
Comment 5 Vincent Untz 2004-03-14 16:15:54 UTC
*** Bug 133095 has been marked as a duplicate of this bug. ***
Comment 6 Bastien Nocera 2004-04-14 11:40:43 UTC

*** This bug has been marked as a duplicate of 139336 ***
Comment 7 Sebastian 2014-10-10 14:34:19 UTC
This component does not exist anymore so these bugs can be removed from their group.