|
|
Post by snugbug on Mar 9, 2022 16:26:02 GMT
Just tried to install Bodhi 6.0 AppPack 64 bit, but then, the first update didn't work. I tried both the update manager and the terminal, using the commands
sudo apt update
and
sudo apt dist-upgrade
The sudo apt update command didn't work, because of many server failures, i.e. they were unavailable, apparently. The sudo apt dist-upgrade would have worked, but i canceled it, because I want to find out first, why the sudo apt update command failed. Using the update manager, I couldn't even update the manage itself, when it told me there was a newer version available.
Also, the MD5 of the Bodi ISO was ok. Does anybody know, why I cannot perform the updates, please? My sources.list looks like this, currently:
# deb cdrom:[Bodhi 20.04 - Release amd64 (20210509.0)]/ focal main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://archive.ubuntu.com/ubuntu focal main restricted
# deb-src http://de.archive.ubuntu.com/ubuntu/ focal main restricted
## Major bug fix updates produced after the final release of the
## distribution.
deb http://archive.ubuntu.com/ubuntu focal-updates main restricted
# deb-src http://de.archive.ubuntu.com/ubuntu/ focal-updates main restricted
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu focal universe
# deb-src http://de.archive.ubuntu.com/ubuntu/ focal universe
deb http://archive.ubuntu.com/ubuntu focal-updates universe
# deb-src http://de.archive.ubuntu.com/ubuntu/ focal-updates universe
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://archive.ubuntu.com/ubuntu focal multiverse
# deb-src http://de.archive.ubuntu.com/ubuntu/ focal multiverse
deb http://archive.ubuntu.com/ubuntu focal-updates multiverse
# deb-src http://de.archive.ubuntu.com/ubuntu/ focal-updates multiverse
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
# deb-src http://de.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse
## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu focal partner
# deb-src http://archive.canonical.com/ubuntu focal partner
deb http://archive.ubuntu.com/ubuntu focal-security main restricted
# deb-src http://security.ubuntu.com/ubuntu focal-security main restricted
deb http://archive.ubuntu.com/ubuntu focal-security universe
# deb-src http://security.ubuntu.com/ubuntu focal-security universe
deb http://archive.ubuntu.com/ubuntu focal-security multiverse
# deb-src http://security.ubuntu.com/ubuntu focal-security multiverse
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual. |
|
|
|
Post by Hippytaff on Mar 10, 2022 7:33:50 GMT
Sounds like you didn’t have a working connection when you did apt update. Those servers are up. Maybe try again. Also the Bodhi sources list might be worth checking out in the sources.list.d folder. Check the url is not commented out, though that wouldn’t produce an error, but worth checking.
|
|
|
|
Post by snugbug on Mar 10, 2022 11:54:41 GMT
Mmmmh,...strange, isn't it?
sudo apt dist-upgrade
does work fine, which means it does find the according servers.
Only
sudo apt update
does not.
If the upper one does work, the connection should be fine actually.
At least, I cannot think of a reason why only one of the commands would work.
|
|
|
|
Post by Hippytaff on Mar 10, 2022 12:09:40 GMT
Can you post the error from apt update?
|
|
|
|
Post by snugbug on Mar 10, 2022 16:26:38 GMT
This is the output of both commands:
The one that doesn't work:
LC_ALL=C sudo apt update
[sudo] password for username:
Err:1 http://archive.ubuntu.com/ubuntu focal InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:2 http://packages.bodhilinux.com/bodhi focal InRelease
Temporary failure resolving 'packages.bodhilinux.com'
Err:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Temporary failure resolving 'archive.ubuntu.com'
Err:5 http://archive.ubuntu.com/ubuntu focal-security InRelease
Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done
Building dependency tree
Reading state information... Done
56 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-security/InRelease Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://packages.bodhilinux.com/bodhi/dists/focal/InRelease Temporary failure resolving 'packages.bodhilinux.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
And this is the one that does work. It's without password query, because I did it right after the first one:
LC_ALL=C sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
apturl-saf bodhi-chromium bodhi-skel bodhi-theme-moksha-arc-dark bodhi-theme-moksha-arc-green bodhi-theme-moksha-blingbling bodhi-theme-moksha-blueelectric bodhi-theme-moksha-crema
bodhi-theme-moksha-detour bodhi-theme-moksha-forum bodhi-theme-moksha-green bodhi-theme-moksha-japan bodhi-theme-moksha-kl4k bodhi-theme-moksha-moonlight bodhi-theme-moksha-passion
bodhi-theme-moksha-pink bodhi-theme-moksha-radiance bodhi-theme-moksha-seven bodhi-theme-moksha-sunshine bodhi-theme-moksha-viceversa discord ephoto-bl kernel-manager leafpad mintupdate
mintupdate-common moksha moksha-module-alarm moksha-module-calendar moksha-module-compton moksha-module-cpu moksha-module-deskshow moksha-module-diskio moksha-module-engage
moksha-module-flame moksha-module-forecasts moksha-module-mail moksha-module-mem moksha-module-net moksha-module-news moksha-module-penguins moksha-module-photo moksha-module-productivity
moksha-module-rain moksha-module-screenshot moksha-module-slideshow moksha-module-snow moksha-module-spellchecker moksha-module-stickynotes moksha-module-tclock moksha-module-wincontrol
moksha-module-winlist-ng moksha-module-winselector terminology terminology-data
55 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 320 MB of archives.
After this operation, 8204 kB of additional disk space will be used.
Do you want to continue? [Y/n]
|
|
|
|
Post by Hippytaff on Mar 10, 2022 17:17:04 GMT
That is bizarre. Not sure what to suggest. Anyone else know what’s going on here? To me it just looks like a lack of connection but the second command kind of rules that out. It could be there’s some kind of firewall or network setting preventing apt update, but again that would also affect dist upgrade…
|
|
enigma9o7
Crew Member
Posts: 1,427 
Likes: 1,336
|
Post by enigma9o7 on Mar 10, 2022 17:26:58 GMT
The second command doesn't prove he has network connection working until pressing Yes. At that point its using the last version of database it has, it hasnt done network yet....
|
|
|
|
Post by Hippytaff on Mar 10, 2022 18:10:16 GMT
The second command doesn't prove he has network connection working until pressing Yes. At that point its using the last version of database it has, it hasnt done network yet.... Good point…in that case apt update must have worked at some point to populate the database in the first place. |
|
|
|
Post by snugbug on Mar 10, 2022 18:53:13 GMT
I wonder, if Bodhi was just installed from the ISO, how can it know there are updates available, without connecting to the internet?
Installed right from the ISO, if the internet connection doesn't work already, it shouldn't know about updates yet, should it?
I also checked the connection with a ping command to 8.8.8.8 and it was ok.
|
|
|
|
Post by Hippytaff on Mar 10, 2022 20:32:40 GMT
Maybe you chose to install updates during install. You would also need a working connection for that…so I don’t know.
|
|
kev392
Crew Member
Posts: 356
Likes: 474
|
Post by kev392 on Mar 10, 2022 22:35:30 GMT
Since you installed AppPack, you should have Update Manager in Applications, System Tools.
You can set your download mirrors and have a nice GUI to download and install your updates.
|
|
|
|
Post by snugbug on Mar 11, 2022 0:55:23 GMT
@ Hippytaff
Yes, I did the updates during the installation, but no problems by then. Looks like the connection is ok.
I've got no idea why Bodhi doesn't connect to the update servers.
For a moment I had the idea, it might be the encrypted server of my ISP (*), which I've set my router to a few weeks ago, but I have other distros installed, where all the updates are done flawlessly.
@ kev392
I already tried the Update Manager and I also tried some other download mirrors... nothing changed. The updates are still being refused.
The only solution I can think of right now is to just repeat the installation of Bodhi using a freshly downloaded ISO, but I don't think, this will fix anything, because both the old and the new ISO have the very same MD5 hash.
Yet, I guess I should give it a try, just to see.
Another chance might be, if I try an installation without the updates during the installation.
(*) Note: I can choose between the standard server of my ISP and an encrypted one.
|
|
|
|
Post by snugbug on Mar 15, 2022 19:01:05 GMT
I just tried the Bodhi installation again.
I took a fresh ISO for my Ventoy drive, together with a fresh persistence dat file.
This time I unchecked the option for the updates during the installation.
Instead, I did the updates after the installation using the update manager.
Everything is ok, now.
|
|
|
|
Post by Hippytaff on Mar 15, 2022 20:12:13 GMT
Excellent, glad it’s up and running!
|
|
|
|
Post by snugbug on Mar 15, 2022 23:27:42 GMT
Yes, I'm very glad, too, but I don't understand why there is a difference between the updates being done during the installation and those being done afterwards.
Are there perhaps two versions of the server database, depending on when I'm accessing them, during the installation or afterwards?
|
|
