Hello, I have come to ask for a little help, for a few days (week?) My KDE Neon refuses to update!

Code: Select all

Erreur fatale: E: http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd-dev amd64 237-3ubuntu10.41 is not (yet) available (Could not connect to 23.19.10.92:8118 (23.19.10.92). - connect (113: No route to host))
E: http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.41 is not (yet) available (Unable to connect to 23.19.10.92:8118:)
E: http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libudev1 amd64 237-3ubuntu10.41 is not (yet) available (Unable to connect to 23.19.10.92:8118:)
E: http://fr.archive.ubuntu.com/ubuntu bionic-updates/main i386 libudev1 i386 237-3ubuntu10.41 is not (yet) available (Unable to connect to 23.19.10.92:8118:)
E: http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libudev-dev amd64 237-3ubuntu10.41 is not (yet) available (Unable to connect to 23.19.10.92:8118:)
E: http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 udev amd64 237-3ubuntu10.41 is not (yet) available (Unable to connect to 23.19.10.92:8118:)
E: http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.41 is not (yet) available (Unable to connect to 23.19.10.92:8118:)
E: http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.41 is not (yet) available (Unable to connect to 23.19.10.92:8118:)
E: http://fr.archive.ubuntu.com/ubuntu bionic-updates/main i386 libsystemd0 i386 237-3ubuntu10.41 is not (yet) available (Unable to connect to 23.19.10.92:8118:)
E: http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.41 is not (yet) available (Unable to connect to 23.19.10.92:8118:)
E: http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd-sysv amd64 237-3ubuntu10.41 is not (yet) available (Unable to connect to 23.19.10.92:8118:)
foul@Foulnux:~$

Forced to reboot from time to time it goes .. no idea why ... All the rest of the network works, I post here from my PC, everything is fine ... just these pesky update ... an idea

ps: of course no proxy and nothing in /etc/apt/sources.list and /etc/hosts

What exact commands do you use for the update?

sudo apt update
sudo pkcon update

for exemple, just now :

Code: Select all

foul@Foulnux:~$ sudo pkcon update
Obtention des mises à jour   [=========================]         
Terminé                      [=========================]         
Chargement du cache           [=========================]         
Test des changements          [=========================]         
Terminé                      [=========================]         
Mise à jour des paquets      [=========================]         
Chargement du cache           [=========================]         
Téléchargement des paquets  [=========================]         
Terminé                      [=========================]         
Erreur fatale: E: https://download.virtualbox.org/virtualbox/debian bionic/contrib amd64 virtualbox-6.1 amd64 6.1.10-138449~Ubuntu~bionic is not (yet) available (Could not connect to 23.19.10.92:8118 (23.19.10.92). - connect (113: No route to host))

foul@Foulnux:~$

up !

How is this a Neon problem when you obviously try to install a Virtualbox version that is not yet available? The package sources you try to access are not from Neon but are Ubuntu sources.
If this persists trying to access a french archive mirror, maybe try switching to the main archive.

The package sources are not the problem... if i reboot my system... the update is working for some seconds... and juste after... same problem...



All my packages are up to date for now... but next update... same problem... it try reach 23.19.10.92:8118 ip ... but i can't find why !?!

Just a thought but have you tried a different update server? I hate to mention this again but for KDE neon you should use the pkcon commands as suggested by the devs because using apt commands might not get all packages and dependencies. Discover uses pkcon not apt like with Kubuntu.

kdeoldster wrote:Just a thought but have you tried a different update server? I hate to mention this again but for KDE neon you should use the pkcon commands as suggested by the devs because using apt commands might not get all packages and dependencies. Discover uses pkcon not apt like with Kubuntu.

Not true. Discover uses Packagekit no matter which sort of disto used. Packagekit then uses apt behind the scenes on distros that use Deb files.
Neon and Kubuntu are identical when it comes to Discover. it is the incorrect usage of apt that caused Neon push the use of pkcon. it also is cross-distro as the commands used with pkcon are the same everywhere.

with pkcon, you don't always get all the errors or warnings and the like when something goes wrong, so using apt is still a helpful thing to use.


Also, using a different source/mirror was already suggested