Indeed. :-)
What Debian did for Lilypond looks like the way to go. It prevents newly
installed systems and systems that were not updated during the past week to
suffer from the problem. For those who updated, I suggested in
> 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
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. The problem
looks widespread: besides those who expressed themselves in this
> 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
If I 'sudo apt-mark unhold network-manager', the Update Manager still
proposes me the version 1.10.6-2ubuntu1+8.0trisquel2 of NetworkManager...
The newer version does not solve the problems for me: using Ethernet, the DNS
server is not automatically set (I can only contact IP addresses, not domain
names) and, I believe, I cannot establish a wireless connection to a network
(using an adpater with the AR9271 chipset). I write "I
> 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
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:
wifi-nl80211:
> 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
Since the log has several errors that mention your MAC address, I think the
problem might have to do with the new randomization of mac addresses.
Given the problem with DNS, I would bet on a problem relating to "disabling
sending hostname on DHCP requests". Indeed, a DHCPOFFER message
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
I tried deleting only one of the two sections. I tried rebooting after
deleting both sections too. Nothing led to any improvement w.r.t. the faced
problems.
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 the network). Should I still try to
Hopefully reinstalling the previous version of network-manager and
wpasupplicant will fix your system.
It did:
https://trisquel.info/forum/internet-connection-problem#comment-144131
Thank you.
I think that GNOME's graphical frontend to network-manager might allow you to
change it
> 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
That works here. However, the package had to be downloaded (sorry about the
French, I should have set LC_ALL=C):
$ sudo apt install network-manager=1.2.6-0ubuntu0.16.04.3
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les
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:
Start-Date: 2019-10-20 11:24:20
Commandline: aptdaemon role='role-commit-packages' sender=':1.183'
Install: libteamdctl0:amd64 (1.23-1, automatic),
18 matches
Mail list logo
