LINUX LITE 7.2 FINAL RELEASED - SEE RELEASE ANNOUNCEMENTS SECTION FOR DETAILS


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Install Updates could not successfully download
#1
Reply
#2
Can't see the actual error messages there, it looks like the log may be truncated.
You can manually re-run the update process and record the process to text files.
If you post the resulting text files back here it might show what is happening.

To do this, open a terminal by pressing 'Ctrl' 'Alt' and 'T' keys together.
In the terminal window, type or paste in
Code:
sudo apt-get update | tee ~/"$(date +"%Y_%m_%d_%T")-apt-get-update.txt"
followed by return/enter.  Enter your password if asked.
Then type or paste in
Code:
sudo apt-get upgrade | tee ~/"$(date +"%Y_%m_%d_%T")-apt-get-upgrade.txt"
followed by return/enter. Press 'y' at the prompt 'Do you want to continue?'.

Running those commands should carry out the update/upgrade process and create two files called apt-get-update.txt and apt-get-upgrade.txt in your home directory.
The filenames will be prefixed with date and time information.
You can watch the screen or open the files when done to confirm they have captured the error information.

Post back and attach the files.

Note that 'apt-get' may not attempt all the possible upgrades.
If the errors aren't in the two apt-get files then you may need to use the similar apt commands.
Code:
sudo apt update | tee ~/"$(date +"%Y_%m_%d_%T")-apt-update.txt"
Code:
sudo apt upgrade | tee ~/"$(date +"%Y_%m_%d_%T")-apt-upgrade.txt"
Again, you may need to enter your password and any answer confirmations.
stevef
clueless
Reply
#3
stevef, thanks for your very helpful post.

I ran the two commands you gave me. Here are the results.

Output from the command sudo apt-get update | tee ~/"$(date +"%Y_%m_%d_%T")-apt-get-update.txt":
Code:
cat 2023_11_10_12:38:55-apt-get-update.txt
Hit:1 http://repo.linuxliteos.com/linuxlite fluorite InRelease
Hit:2 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Get:4 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Hit:6 http://archive.canonical.com/ubuntu jammy InRelease
Get:7 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]
Fetched 338 kB in 1s (363 kB/s)
Reading package lists...

Output from the command sudo apt-get upgrade | tee ~/"$(date +"%Y_%m_%d_%T")-apt-get-upgrade.txt":
Code:
Installing new version of config file /etc/java-11-openjdk/jfr/profile.jfc ...
Installing new version of config file /etc/java-11-openjdk/security/default.policy ...
Installing new version of config file /etc/java-11-openjdk/security/java.policy ...
Installing new version of config file /etc/java-11-openjdk/security/java.security ...
Setting up libssl3:i386 (3.0.2-0ubuntu1.12) ...
Setting up openjdk-11-jre:amd64 (11.0.20.1+1-0ubuntu1~22.04) ...
Setting up python3-distupgrade (1:22.04.17) ...
Setting up ubiquity (22.04.20) ...
Setting up libkrb5support0:i386 (1.19.2-2ubuntu0.3) ...
Setting up ubuntu-release-upgrader-core (1:22.04.17) ...
Setting up libk5crypto3:i386 (1.19.2-2ubuntu0.3) ...
Setting up update-manager-core (1:22.04.10) ...
Setting up libkrb5-3:i386 (1.19.2-2ubuntu0.3) ...
Setting up update-notifier-common (3.192.54.6) ...
update-notifier-download.service is a disabled or a static unit not running, not starting it.
update-notifier-motd.service is a disabled or a static unit not running, not starting it.
Setting up libgssapi-krb5-2:i386 (1.19.2-2ubuntu0.3) ...
Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.8+dfsg-1ubuntu0.2) ...
Processing triggers for install-info (6.8-4build1) ...
Processing triggers for menu (2.1.47ubuntu4) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for fontconfig (2.13.1-4.2ubuntu5) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
Processing triggers for libglib2.0-0:amd64 (2.72.4-0ubuntu2.2) ...
Processing triggers for libc-bin (2.35-0ubuntu3.4) ...
Setting up libmetacity3:amd64 (1:3.44.0-1ubuntu1) ...
Processing triggers for gconf2 (3.2.6-7ubuntu2) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for cracklib-runtime (2.9.6-3.4build4) ...
Processing triggers for plymouth-theme-ubuntu-text (0.9.5+git20211018-1ubuntu3) ...
update-initramfs: deferring update (trigger activated)
Setting up metacity (1:3.44.0-1ubuntu1) ...
Processing triggers for ntp (1:4.2.8p15+dfsg-1ubuntu2) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
Processing triggers for shared-mime-info (2.1-2) ...
Processing triggers for ca-certificates (20230311ubuntu0.22.04.1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

done.
done.
Processing triggers for initramfs-tools (0.140ubuntu13.4) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-52-generic
I: The initramfs will attempt to resume from /dev/sda12
I: (UUID=822ce3d7-6ce7-40fc-a34f-69a3b00e8bd7)
I: Set the RESUME variable to override this.
Processing triggers for libc-bin (2.35-0ubuntu3.4) ...
len  ~ 

It seems that the front-end of that last cat command got truncated.

But everything seems to be OK. Does it look good to you?
Thanks.
coderlen
Reply
#4
Difficult to say from the truncated information.

There are some limits on what apt-get will do. If you do an update/upgrade sequence from the GUI (or run the apt version of the commands) it may be that your kernel can be updated.
stevef
clueless
Reply
#5
stevef, I did what you said, and I upgraded from Linux Lite 6.2 to 6.6. Everything seems to be working very well. So thanks so much for your help!

coderlen
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)