Automatic upgrade starts right after resume, before the network is up, and installs nothing

Abierto
  • ¿Algo no está bien?
#1,109 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
linux, python
Área
backend, devops

Línea de trabajo

Start by reading the mintupdate-automation-upgrade.timer and service configuration, then trace how the upgrade is triggered after suspend or hibernate and how it depends on NetworkManager. The journal and mintupdate.log examples show the failure window and the misleading successful exit status. Done means an automatic run waits until networking is usable after resume and reports or handles a failed cache refresh appropriately.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Linux Mint 22.3, mintupdate 7.1.4, laptop on Wi-Fi that is usually asleep or hibernated at midnight.

When the daily time passes while the machine is asleep, mintupdate-automation-upgrade.timer (Persistent=true) starts the service as soon as it wakes up. On this laptop that is 0.1 to 0.2 seconds after resume, while NetworkManager is still disconnected. mintupdate-cli then can't resolve any repository and nothing gets installed. The next attempt is the following day.

The service has After=network-online.target, but that target is reached once at boot and stays active through suspend, so it doesn't hold the service back on resume.

One example from the journal:

Oct 22 13:51:22.693 systemd-sleep: System returned from sleep operation 'hibernate'.
Oct 22 13:51:22.829 systemd: Starting mintupdate-automation-upgrade.service - Update Manager automatic upgrades...
Oct 22 13:51:24.282 NetworkManager: manager: NetworkManager state is now DISCONNECTED
Oct 22 13:51:28.059 NetworkManager: manager: NetworkManager state is now CONNECTED_GLOBAL
Oct 22 13:51:35.931 systemd: Finished mintupdate-automation-upgrade.service - Update Manager automatic upgrades.

and the matching part of /var/log/mintupdate.log:

W:Failed to fetch https://mirror.vnet.sk/ubuntu/dists/noble/InRelease  Could not resolve 'mirror.vnet.sk'
[same for every other repository]
Error: mint-refresh-cache could not update the cache.

Between Oct 5 and Oct 29 there were 25 automatic runs. 10 failed like this, and 9 of those 10 started within 0.2 s of a resume from suspend or hibernate. Four days in a row (Oct 22 to 25) got no updates.

The service still exits with status 0 after these runs, so systemctl reports them as successful and the only trace is in mintupdate.log.

Lenguaje dominante
Python
Estrellas
425
Forks
191
Merge medio
23 d 14 h
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de linuxmint/mintupdate

Todos los issues de linuxmint/mintupdate

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.