![]() |
7.4 install 1st update results - grub exit status 32 - Printable Version +- Linux Lite Forums (https://www.linuxliteos.com/forums) +-- Forum: Software - Support (https://www.linuxliteos.com/forums/forumdisplay.php?fid=5) +--- Forum: Updates (https://www.linuxliteos.com/forums/forumdisplay.php?fid=46) +--- Thread: 7.4 install 1st update results - grub exit status 32 (/showthread.php?tid=9507) |
7.4 install 1st update results - grub exit status 32 - BilyJimyBobb - 06-20-2025 ...i have NO clue what to do here, other than per instructions, let alone how to read/interpret the following - assistance mucho appreciato! ![]() RE: new 7.4 install & 1st/initial update results - stevef - 06-20-2025 This may be a known problem in which an update appears to fail but actually completes behind the scenes Please can you open a terminal by pressing 'Ctrl' 'Alt' and 'T' together. Type or paste in this command followed by enter. This will refresh the update cache. Code: sudo apt-get update | tee ~/"$(date +"%Y_%m_%d_%T")-apt-get-update.txt" Then enter this command which will calculate if any programs need upgrading and if so, it will ask if you wish to apply them. You can answer 'n' if asked, we are interested in what upgrades the system reports being as required. Code: sudo apt-get upgrade | tee ~/"$(date +"%Y_%m_%d_%T")-apt-get-upgrade.txt" Each command creates a text file in your home directory in which the screen output is saved. After running the two commands please review the two text files and paste the results back here. Thank you RE: new 7.4 install & 1st/initial update results - BilyJimyBobb - 06-20-2025 sudo apt-get update | tee ~/"$(date +"%Y_%m_%d_%T")-apt-get-update.txt" Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease Hit:2 https://brave-browser-apt-release.s3.brave.com stable InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu noble InRelease Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu noble-updates InRelease Hit:6 http://us.archive.ubuntu.com/ubuntu noble-backports InRelease Hit:8 https://packages.mozilla.org/apt mozilla InRelease Hit:9 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu noble InRelease Hit:10 https://ppa.launchpadcontent.net/mozillateam/thunderbird-next/ubuntu noble InRelease Hit:7 https://repo.linuxliteos.com/linuxlite galena InRelease Reading package lists... W: https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/dists/noble/InRelease: Signature by key 0AB215679C571D1C8325275B9BDB3D89CE49EC21 uses weak algorithm (rsa1024) W: https://ppa.launchpadcontent.net/mozillateam/thunderbird-next/ubuntu/dists/noble/InRelease: Signature by key 0AB215679C571D1C8325275B9BDB3D89CE49EC21 uses weak algorithm (rsa1024) sudo apt-get upgrade | tee ~/"$(date +"%Y_%m_%d_%T")-apt-get-upgrade.txt" E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 33988 (apt-get) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? 2025_06_19_21:51:16-apt-get-update Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease Hit:2 https://brave-browser-apt-release.s3.brave.com stable InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu noble InRelease Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu noble-updates InRelease Hit:6 http://us.archive.ubuntu.com/ubuntu noble-backports InRelease Hit:8 https://packages.mozilla.org/apt mozilla InRelease Hit:9 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu noble InRelease Hit:10 https://ppa.launchpadcontent.net/mozillateam/thunderbird-next/ubuntu noble InRelease Hit:7 https://repo.linuxliteos.com/linuxlite galena InRelease Reading package lists... 2025_06_19_21:52:21-apt-get-upgrade ...reports/labels it as an "empty document" RE: new 7.4 install & 1st/initial update results - stevef - 06-20-2025 That looks better. The 'could not get lock' error message indicates more than one update processes are competing for the resources. There may have been a background task running. Leave it for 10 minutes and then try an update/upgrade again. |