no autoconnect when GUI is open

Bug #1709593 reported by Vincent Lefevre on 2017-08-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd
Undecided
Unassigned

Bug Description

Under Debian/unstable with wicd 1.7.4+tb2-4:

After the connection is lost (e.g. router switched off and on again a bit later), wicd does not attempt to reconnect. For instance, the logs end with:

2017/08/07 00:05:46 :: DHCP connection successful
2017/08/07 00:05:46 :: not verifying
2017/08/07 00:05:46 :: Connecting thread exiting.
2017/08/07 00:05:46 :: Sending connection attempt result success

i.e. with the last successful connection. The cause may be that wicd did not notice that the connection was lost. It seems that closing the GUI allows wicd to reconnect (though the bug related to that was supposed to be fixed), as I mentioned on:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833929

After some tests and a look at the code, it is actually

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582567

that has reappeared! In wicd-daemon.py,

        if self.GetAutoReconnect() and not self.CheckIfConnecting() and \
           not self.GetForcedDisconnect() and not self.auto_connecting and \
           not self.gui_open:

the "and not self.gui_open" should be removed.

summary: - does not attempt to reconnect after connection loss
+ no autoconnect when GUI is open
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.