Eos-update-notifier requires manual intervention

There’s a small (i.e. non-fatal) bug in the timer setting of eos-update-notifier, before version 0.9.17-1.
The timer setting initiates an extra update check at first login, and that extra check will typically fail.

The bug should not cause any further trouble, but may show an unnecessary update failure at login, and is visible if you check the journal right after boot and login.

Version 0.9.17-1 removes that extra check.

To get rid of the bug, you need to run the following terminal commands:

    sudo pacman -Syu                  # need to update 'eos-update-notifier'
    eos-update-notifier -init-force

The second command will modify and fix your update notifier timer file.

Note that if you have changed the checking schedule and want to re-use your changes, run command

    eos-update-notifier -conf

to change the scheduling to your liking.

3 Likes

this is on a fresh install from 2 days ago. seems no file existed before? just wanted to make sure things went well:

Summary

sudo pacman -Syu # need to update ‘eos-update-notifier’
:: Synchronisiere Paketdatenbanken…
core ist aktuell
extra ist aktuell
community ist aktuell
multilib ist aktuell
endeavouros ist aktuell
:: Starte vollständige Systemaktualisierung…
Es gibt nichts zu tun

eos-update-notifier -init-force
Unit eos-update-notifier.timer could not be found.
eos-update-notifier.timer.pacnew: OK
eos-update-notifier.service.pacnew: OK
Created symlink /home/user/.config/systemd/user/timers.target.wants/eos-update-notifier.timer → /home/user/.config/systemd/user/eos-update-notifier.timer.
New ‘/home/user/.config/systemd/user/eos-update-notifier.service’ successfully set up.
New ‘/home/user/.config/systemd/user/eos-update-notifier.timer’ successfully set up.
eos-update-notifier service initialized for user ‘user’.

Look OK to me!

You can also check the timer file listed there. And look at the EndeavourOS wiki about the update notifier.

1 Like