gryf/wicd - wicd

5 Commits

Author	SHA1	Message	Date
Tom Van Braeckel	04dd18bed9	wicd-curses: catch unhandled exception when automatically starting the wicd daemon fails	2014-12-19 11:52:22 +01:00
Tom Van Braeckel	754d8e0fa3	Merge "Javier P.L. 2013-12-06 allow wicd daemon to start even if /etc/resolv.conf is a relative symlink" https://code.launchpad.net/~chilicuil/wicd/wicd/+merge/198057 Bugreports: https://bugs.launchpad.net/wicd/+bug/1193856 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691973 https://bugs.launchpad.net/wicd/+bug/1171296	2014-12-11 14:50:12 +01:00
Tom Van Braeckel	1301433fb8	Merge "Ben the Pyrate 2014-08-19 The exit status should indicate whether or not the connection was successful" Exit with a non-zero status (6) when a connection attempt does not succeed.	2014-12-11 13:41:56 +01:00
Tom Van Braeckel	285122d01f	Merge "Tom Van Braeckel 2014-11-05 Automatic reconnect: honour the automatic reconnect configuration, even if the GUI interface is open"	2014-12-11 12:59:28 +01:00
Tom Van Braeckel	d32482afb9	Automatic reconnect: honour the automatic reconnect configuration, even if the GUI interface is open When a user actives "automatic reconnnect" and then tries this out, he will be staring at the GUI interface, waiting for a reconnect. But wicd-daemon refuses to reconnect when the GUI interface is open, and fails to reports this to the GUI user. Hence users assume that this feature does not work properly (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582567). This commit fixes that by doing a reconnect, no matter whether the GUI is open or not, thus taking the path of "least surprise". The original rationale for not reconnecting when the GUI is open was never stated in the comments, nor in the commit message.	2014-11-05 07:32:28 +01:00