> I really meant "unhold" (no typo).I do not think it is OK to still
> have the normally proposed version of NetworkManager (well, normal for
> those who enabled flidas-backports) "break the Internet" of many
> users.
Sorry, I misunderstood you. It sounds you had already successfully
"held" the
> If I 'sudo apt-mark unhold network-manager', the Update Manager still
> proposes me the version 1.10.6-2ubuntu1+8.0trisquel2 of
> NetworkManager...
If you really did use "unhold", then this is the expected behavior.
Change it to "hold" in order to prevent upgrades to network-manager.
If you
> Nothing unexpected: I have to choose the GVT-989C_nomap network by
> hand, the password is asked but, again, the connection is never
> established. I see no relevant difference in dmesg's output. I
> detect no relevant difference in NetworkManager's log either but maybe
> you will:
Neither do
> Given the problem with DNS, I would bet on a problem
> relating to "disabling sending hostname on DHCP
> requests".
In that case, it is the changes made to nm-setting-ip4-config.c and
nms-ifcfg-rh-writer.c that are causing the issue, which can only be
reverted by recompiling.
What happens if
On 10/20, lc...@dcc.ufmg.br wrote:
> Deleting both sections of
> /etc/NetworkManager/NetworkManager.conf and executing
> 'systemctl restart NetworkManager' does not solve any
> of the two problems (the DNS not being automatically
> configured with Ethernet, the Wifi adapter never
> connecting to
> Since I have the same Wifi chipset (AR9271), I installed the latest
> updates to see. Here is the related entry in
> /var/log/apt/history.log:
Thanks for saving me the trouble of breaking my own Internet in order to
get this information. Hopefully reinstalling the previous version of