Solved Problem Upgrading to Mint Virginia 21.3 from Mint Vanessa 21

Solved issue
P

PanLinux

New Member
Joined
May 2, 2024
Messages
7
Reaction score
7
Credits
105
Greetings, So, I successfully upgraded from Linux Mint 20.3 to 21 using: https://forums.linuxmint.com/viewtopic.php?t=235992. blog 4378 worked to get me from 20.3 to 21, but when I attempted the upgrade from 21 to 21.3
Error Occured- Details are provided while upgrading to Mint Virginia
In an attempt to upgrade from mint 21 to Mint 21.3 I use the command
“sudo apt update && sudo apt upgrade”
My laptop completed the reading, building dependency tree, and reading state information, then either error messages about duplicate files. Then the system got stuck in the message:

“Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 65207 (synaptic)”
Hardware Model: Latitude E5440
bernie78@bernie78-Latitude-E5440:~$ sudo apt update && sudo apt upgrade
[sudo] password for bernie78:
Hit:1 http://dl.google.com/linux/chrome/deb stable InRelease
Ign:2 http://packages.linuxmint.com virginia InRelease
Hit:3 http://packages.linuxmint.com virginia Release
Get:5 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Hit:6 http://archive.ubuntu.com/ubuntu jammy InRelease
Get:7 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Hit:8 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Fetched 229 kB in 2s (107 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
112 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/additional-repositories.list:1 and /etc/apt/sources.list.d/google-chrome.list:3

W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/additional-repositories.list:1 and /etc/apt/sources.list.d/google-chrome.list:3
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/additional-repositories.list:1 and /etc/apt/sources.list.d/google-chrome.list:3
W: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list.d/additional-repositories.list:1 and /etc/apt/sources.list.d/google-chrome.list:3
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/additional-repositories.list:1 and /etc/apt/sources.list.d/google-chrome.list:3
W: Target DEP-11 (main/dep11/Components-amd64.yml) is configured multiple times in /etc/apt/sources.list.d/additional-repositories.list:1 and /etc/apt/sources.list.d/google-chrome.list:3
W: Target DEP-11 (main/dep11/Components-all.yml) is configured multiple times in /etc/apt/sources.list.d/additional-repositories.list:1 and /etc/apt/sources.list.d/google-chrome.list:3
W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/additional-repositories.list:1 and /etc/apt/sources.list.d/google-chrome.list:3
W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/additional-repositories.list:1 and /etc/apt/sources.list.d/google-chrome.list:3

I believe the solution is to use the following command:
"sudo remove /etc/apt/sources.list.d/official-package-repositories.list" eight times?

So, any help to resolve this would be appreciated.

Reply
 


G'day PanLinux, Welcome to Linux.org

Did you take a Timeshift snapshot before attempting the upgrade?

Did you use LM21 before attempting the upgrade to 21.3 ?

Did you apply any updates while in LM21 ?
 
It's always safer to do a clean install...the only time I do a clean install is when support is nearly up for the version I'm running.
1714632017902.gif
 
Moving on from my previous post, did LM21.3 actually install/finish ?....are you able to carry on from where you left off ?. Because the only error in that list is the first two lines.....the rest are just warnings

the error: Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 65207 (synaptic)”

It is telling you that synaptic (update manager) is causing the error......it is likely that either synaptic or update manager are still open?....if so close them/it
If that is not the case, then read on. If there is a Terminal window open and it is running something and has not finished...allow it to finish (if it will)....If it won't finish, close it anyway ) If there is nothing open, close it.

If nothing changes after closing terminal and any open synaptic/update manager etc......Open Terminal (ctrl+alta=T)
and copy and paste the following into it

Code: 
ps aux | grep -i apt

Copy and paste the result in your reply, please.
 
Last edited:
I might add that before doing an upgrade you always need to disable any PPA's you may have in your apt.sources.list If you don't you will likely get conflicts. You can add them back after the upgrade is over. You may need to reinstall those programs after upgrading also.
This blog maybe of help.

How to upgrade to Linux Mint 21.3 – The Linux Mint Blog

blog.linuxmint.com blog.linuxmint.com
Click to expand...
 
Condobloke said:
G'day PanLinux, Welcome to Linux.org

Did you take a Timeshift snapshot before attempting the upgrade?

Did you use LM21 before attempting the upgrade to 21.3 ?

Did you apply any updates while in LM21 ?
Click to expand...
Yes. After I upgraded from 20.3 to 21. I did a Timeshiift snapshot of my LM21. then I did the step on the link to upgrade from 21/21.1/21.2 to 21.3. while doing the updates is when the error messages occurred. I responded to the notification, there is a newer version available in checking for updates.


Ok: I did not disable PpA!. I will look into that.
Thanks for the blog: However, that's the link I am using that got me to this point in time.
 
Condobloke said:
ps aux | grep -i apt
Click to expand...
Thanks again for replying. Just seeing your message. I had seen this command in one of the blogs/forum and this was like the last command I entered yesterday. Anyhow: the results were as follows:
bernie78@bernie78-Latitude-E5440:~$ ps aux | grep -i apt
root 658 0.0 0.0 128592 9236 ? Ssl Apr30 0:03 /usr/sbin/thermald --systemd --dbus-enable --adaptive
root 87532 0.0 0.0 16072 6180 ? S 18:55 0:00 sudo /usr/bin/mint-refresh-cache --use-synaptic 85983245
root 87533 0.0 0.0 20212 10212 ? S 18:55 0:00 /usr/bin/python3 /usr/bin/mint-refresh-cache --use-synaptic 85983245
root 87534 0.5 1.0 662132 162908 ? Sl 18:55 0:02 /usr/sbin/synaptic --hide-main-window --update-at-startup --non-interactive --parent-window-id 85983245
bernie78 89231 0.0 0.0 9212 2384 pts/0 S+ 19:03 0:00 grep --color=auto -i apt

Thanks for a better interpretation of the results.
 
PanLinux said:
Yes. After I upgraded from 20.3 to 21. I did a Timeshiift snapshot of my LM21. then I did the step on the link to upgrade from 21/21.1/21.2 to 21.3. while doing the updates is when the error messages occurred. I responded to the notification, there is a newer version available in checking for updates.


Ok: I did not disable PpA!. I will look into that.
Thanks for the blog: However, that's the link I am using that got me to this point in time.
Click to expand...
Ok Linux Family. Great News!

Never underestimate the Power of a Reboot. I rebooted my Dell laptop, and ran the code hostnamectl: Whalla: I am now Linux virginia 21.3. Thanks again for all who responded.
 
@PanLinux when you are sure this is solved, you can mark it as such by going to your first post, and at top right click the 3 dots to the right of Watch and do as follows

nYSKHvh.png


Only when you are sure

Cheers

Wizard
 
You must log in or register to reply here.

Members online

Total: 599 (members: 5, guests: 594)

Latest posts

Top