Description of problem: The reactivated connection is not the one left before the application was quitted. Present issue is a variant of the issue #11.
Version-Release number of component in Fedora: dnscrypt-proxy-gui-1.11.11-1.fc27.x86_64
Steps to Reproduce:
In Application Settings view, option 'Run service at start' has to be checked.
Because of the still alive issue #11, in order to select e.g. the DNScrypt server 'cisco' as the connection to be established, select in the list the server name that is the immediate previous one to the entry 'cisco', which is currently 'adguard-dns-ns2' and then process the request.
Stop and restore system DNS resolver settings, –assuming that the settings related to component dnscrypt-proxy were left at default– then select the profile generated by NetworkManager that lists as the only IPv4 server entry 'nameserver 127.0.0.1' and as the IPv6 servers the ones applied by the option Automatic DNS.
Relaunch DNSCryptClient in same session or reboot system.
Actual results: The reactivated connection is not the one left before the application was quitted, but the one that corresponds to the immediate following DNScrypt server name in the list.
Expected results: The connection reactivated to remain the one that was activated before the application was quitted.
Description of problem: The reactivated connection is not the one left before the application was quitted. Present issue is a variant of the issue #11.
Version-Release number of component in Fedora: dnscrypt-proxy-gui-1.11.11-1.fc27.x86_64
Steps to Reproduce:
Actual results: The reactivated connection is not the one left before the application was quitted, but the one that corresponds to the immediate following DNScrypt server name in the list.
Expected results: The connection reactivated to remain the one that was activated before the application was quitted.