I’ve just received the message from update manager that I can finally update to 26.04 but when I try to update I receive this error:
/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py:178: Warning: W:Lo scaricamento è eseguito come root, ma non in una sandbox, poiché l’utente “_apt” non ha accesso al file “resolute.tar.gz.gpg”. - pkgAcquire::Run (13: Permesso negato)
result = fetcher.run()
autenticazione di «resolute.tar.gz» con «resolute.tar.gz.gpg»
estrazione di «resolute.tar.gz»
Sorry, the message is in italian but it simply say that _apt user has no grants to access that file.
i’ve of course do the usual apt update, apt full-upgrade. I’ve also tried apt clean.
I’ve disabled all third parties repositories. No luck
On another machine everything worked as expected
Since I did have funny errors because of permissions, you might want to check the UMASK of the root user (should be 022), most probably in a sudo context, which can alter that mask. In my paranoia, I had set UMASK 027 in /etc/login.defs. There are also sudoers settings, which have a bearing on that.
The only solution (for me) is to patch DistUpgradeController.py in ubuntu-release-upgrader-<version_created_by_do_release_upgrade> and then execute dist-upgrade.py using sudo su
Have you actually checked the permissions of said file? Because I don’t think root as the sandbox user is the intended use of said sandbox; usually root is the only user standing a chance to escape sandboxes, i.e. it’s rather trivial for root to escape a chroot, IIRC.
Of course, it can be a workaround; nobody actually expects the release upgrader to do anything malevolent like trying to escape a sandbox. But if APT had some yet unknown RCE vulnerability, giving the attacker root privileges would be a gift they’d gladly accept, I guess.
There is your issue I bet… as that detail shows an non-updated package
A quick CLI scan here shows results
distro-info-data | 0.66 | questing | source, all
distro-info-data | 0.66ubuntu0.1 | questing-security | source, all
distro-info-data | 0.66ubuntu0.2 | questing-updates | source, all
where you’re not your 0.66 matches the initial ISO media, but NOT and updated system using -updates or -security. You should NOT have the first line of output on anything but a new install; as it’ll get upgraded by the higher-value packages from other repositories when upgrades are applied.
I’d check you’ve NOT disabled your sources; as your details match either problems that would show in sudo apt update (such as errors, warnings or just missing lines!) and thus subsequent commands are not actually updating packages.
This is the same problem discussed in link I provided earlier, ie.
You mention running
but do realize this command only updates software lists, but DOES NOT apply any upgrades to your system; it needs to be followed by an apt upgrade or better an apt full-upgrade command to apply the upgrades found by updating your software lists.
Your output shows you’ve not applied updates, either as you’ve disabled sources; or haven’t dealt with warnings/errors or any missing lines of output from the command like sudo apt update in my opinion, or just not run any apt upgrade type of command.
It wasn’t a problem of updates (and of course I did a apt upgrade) or permissions. The problem was in the script. The DistUpgradeFetcherCore python script wasn’t recognize the NEW version at all. fromVersion, fromDist and toDist variables were correct while toVersion was empty! Setting manually toDist variable make the script work correctly
I wouldn’t be so sure about that. It may just mean that is has to be explicitly set or the code will fall back on toVersion = max(availableVersions) or something like that. But I also don’t have the script in front of me.
But if it’s truly a bug in said script you should report it.
There are plenty more updated packages in -security and -universe that might have essential changes that are relevant for the upgrade … just hacking around in the upgrade script will have made you bypass these possibly essential changes so I’d expect more issues further down the road on this machine …
It was Ubuntu that was show me the update to 26.04. I didn’t it myself.. So I was expecting a no-problem update like the other machine were 25.10 was installed.
In any case except for a Nautilus graphic problem everything is working correctly and also the update went fine with no warnings or errors.