05-14-2021, 06:28 PM
I recently noticed a quirk with post update wifi connections which I believe is connected to timeshift and I think some users are attempting to solve it via network settings which have nothing to do with the quirk. I have three/four different LL 5.x installations and only one exhibits the loss of and inability to re-connect to a saved wifi connection after rebooting after updates and it is the one where timeshift is auto-scheduled. I don't use timeshift at all on the others. Also none of my connections are set to auto-connect. The quirk exhibits itself in the following ways:
The user runs updates normally and reboots the machine. The user selects the previous wifi connection that worked before and attempts to connect. The connection fails and after failing is no longer displayed in nm's connection list. Logging out and back in again does not make it reappear in the list. Editing the connection manually and saving it has no effect. All that works, I have discovered after experimenting a bit, is to log out to the login screen and then select shutdown and shut down the system. When booting again all will be normal. I do believe this is related to timeshift auto-scheduling usage and maybe a case where normal reboot code and systemd network management settings are not allowed to reset because of timeshift. As I have explained, logging out and shutting the system down after a normal update reboot alleviates the quirk.
TC
The user runs updates normally and reboots the machine. The user selects the previous wifi connection that worked before and attempts to connect. The connection fails and after failing is no longer displayed in nm's connection list. Logging out and back in again does not make it reappear in the list. Editing the connection manually and saving it has no effect. All that works, I have discovered after experimenting a bit, is to log out to the login screen and then select shutdown and shut down the system. When booting again all will be normal. I do believe this is related to timeshift auto-scheduling usage and maybe a case where normal reboot code and systemd network management settings are not allowed to reset because of timeshift. As I have explained, logging out and shutting the system down after a normal update reboot alleviates the quirk.
TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.