failed upgrade from 20.04 to 22.04 part way through 20.04 will still boot but won't update. multiboot with grub win,22.04 on different partitions.
upgrade from 20.04 to 22.04 failed part way through with the following message:
/home/mark/
this is the current out from software updater
This error could be caused by required additional software packages which are missing or not installable. Furthermore there could be a conflict between software packages which are not allowed to be installed at the same time.
Transaction failed: Package dependencies cannot be resolved
The following packages have unmet dependencies:
glib-networking: Depends: libgnutls30 (>= 3.6.12) but 3.7.3-4ubuntu1.2 is to be installed
How do I get it finish the upgrade to 22.04 Or failing that repair the 20.04 with out wiping the whole system?
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
![]() |
#1 |
Attached is the screen shot that was supposed to be in the original post
On 10/28/23 17:46, Mark wrote:
> New question #708316 on Ubuntu:
> https:/
>
> upgrade from 20.04 to 22.04 failed part way through with the following message:
>
> /home/mark/
>
> this is the current out from software updater
> This error could be caused by required additional software packages which are missing or not installable. Furthermore there could be a conflict between software packages which are not allowed to be installed at the same time.
> Transaction failed: Package dependencies cannot be resolved
> The following packages have unmet dependencies:
>
> glib-networking: Depends: libgnutls30 (>= 3.6.12) but 3.7.3-4ubuntu1.2 is to be installed
> Depends: glib-networking
> Depends: glib-networking
>
> How do I get it finish the upgrade to 22.04 Or failing that repair the 20.04 with out wiping the whole system?
>
Revision history for this message
![]() |
#2 |
Attaching screenshots to Launchpad questions does not work. If you see the need to show a picture, then you have to make that picture available on the internet (e.g. by uploading it to some public image hosting service like imgur)
To your problem:
For diagnsotic purposes, what output do you receive for the following commands (to be executed in a terminal window, and the output transferred to this question document by copy and paste):
uname -a
lsb_release -crid
sudo dpkg --audit
sudo dpkg --configure -a
sudo apt update
apt policy glib-networking: libgnutls30 glib-networking
Revision history for this message
![]() |
#3 |
thanks for confirming what I thought when the second attempt to post the
screen shot didn't work. below is the output of your requested commands:
uname -a
Linux Studio 5.4.0-146-
19:07:53 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 20.04.6 LTS
Release: 20.04
Codename: focal
sudo dpkg --audit
[sudo] password for mark:
mark@Studio:
sudo dpkg --configure -a
mark@Studio:
sudo apt update
Hit:1 http://
Get:2 http://
Get:3 http://
Get:4 http://
Fetched 338 kB in 1s (610 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
545 packages can be upgraded. Run 'apt list --upgradable' to see them.
apt policy glib-networking: libgnutls30 glib-networking
glib-networking
glib-networking:
Installed: 2.64.2-1ubuntu0.1
Candidate: 2.64.2-1ubuntu0.1
Version table:
*** 2.64.2-1ubuntu0.1 100
100 /var/lib/
libgnutls30:
Installed: 3.6.13-2ubuntu1.8
Candidate: 3.7.3-4ubuntu1.2
Version table:
3.
500 http://
500 http://
Packages
*** 3.6.13-2ubuntu1.8 100
100 /var/lib/
glib-networking
Installed: 2.64.2-1ubuntu0.1
Candidate: 2.64.2-1ubuntu0.1
Version table:
*** 2.64.2-1ubuntu0.1 100
100 /var/lib/
glib-networking
Installed: 2.64.2-1ubuntu0.1
Candidate: 2.64.2-1ubuntu0.1
Version table:
*** 2.64.2-1ubuntu0.1 100
100 /var/lib/
thanks for your help mark
On 10/29/23 08:05, Manfred Hampl wrote:
> uname -a
Revision history for this message
![]() |
#4 |
Strange. Your output is somewhat incomplete. There are no available versions listed for the glib-networking packages.
What is the output of the command
cat -n /etc/apt/
Revision history for this message
![]() |
#5 |
here is the output
cat -n /etc/apt/
1 # deb cdrom:[
amd64 (20200423)]/ focal main multiverse restricted universe
2
3 # See http://
to upgrade to
4 # newer versions of the distribution.
5 deb http://
6 # deb-src http://
restricted
7
8 ## Major bug fix updates produced after the final release of the
9 ## distribution.
10 deb http://
11 # deb-src http://
main restricted
12
13 ## N.B. software from this repository is ENTIRELY UNSUPPORTED
by the Ubuntu
14 ## team. Also, please note that software in universe WILL NOT
receive any
15 ## review or updates from the Ubuntu security team.
16 deb http://
17 # deb-src http://
18 deb http://
19 # deb-src http://
universe
20
21 ## N.B. software from this repository is ENTIRELY UNSUPPORTED
by the Ubuntu
22 ## team, and may not be under a free licence. Please satisfy
yourself as to
23 ## your rights to use the software. Also, please note that
software in
24 ## multiverse WILL NOT receive any review or updates from the
Ubuntu
25 ## security team.
26 deb http://
27 # deb-src http://
28 deb http://
29 # deb-src http://
multiverse
30
31 ## N.B. software from this repository may not have been tested as
32 ## extensively as that contained in the main release,
although it includes
33 ## newer versions of some applications which may provide
useful features.
34 ## Also, please note that software in backports WILL NOT
receive any review
35 ## or updates from the Ubuntu security team.
36 deb http://
restricted universe multiverse
37 # deb-src http://
focal-backports main restricted universe multiverse
38
39
40 deb http://
41 # deb-src http://
main restricted
42 deb http://
43 # deb-src http://
universe
44 deb http://
45 # deb-src http://
multiverse
46
47 # This system was installed using small removable media
48 # (e.g. netinst, live or single CD). The matching "deb cdrom"
49 # entries were disabled at the end of the installation process.
50 # For information about how to configure apt package sources,
51 # see the sources.list(5) manual.
On 10/29/23 13:46, Manfred Hampl wrote:
> cat -n /etc/apt/
Revision history for this message
![]() |
#6 |
This looks completely normal.
I recommend that you try completely re-loading the package inventory lists and then try again.
If that still produces the same output, then you probably should try switching to a different repository server and try again.
sudo rm -v /var/lib/
sudo apt update
apt policy glib-networking: libgnutls30 glib-networking
Revision history for this message
![]() |
#7 |
after your suggested answer update loaded a lot more packages but still
did not complete would not let me change into settings to change sources
on reboot locks up at login I get a black screen no courser no response
to the keyboard.
On 10/29/23 14:11, Manfred Hampl wrote:
> Your question #708316 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> This looks completely normal.
>
> I recommend that you try completely re-loading the package inventory lists and then try again.
> If that still produces the same output, then you probably should try switching to a different repository server and try again.
>
> sudo rm -v /var/lib/
> sudo apt update
> apt policy glib-networking: libgnutls30 glib-networking
>
Revision history for this message
![]() |
#8 |
When you boot your system, can you bring up the grub menu (by hitting the left shift or escape keys early during boot)?
If you can do that, select "advanced mode" and "root command prompt".
Does that work?
If yes, issue the command
sudo mount -o remount,rw /
sudo dpkg --configue -a
What is the gist of the output that you receive (especially the last lines)
(you can shutdown from that mode by "sudo poweroff").
Revision history for this message
![]() |
#9 |
Sorry it has taken so long to respond. I have made several attempts
with no success the most I get is a blinking cursor on a black screen
and no keyboard response.
On 10/30/23 02:50, Manfred Hampl wrote:
> Your question #708316 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> When you boot your system, can you bring up the grub menu (by hitting
> the lest shift or escape keys early during boot)?
>
> If you can do that, select "advanced mode" and "root command prompt".
> Does that work?
>
> If yes, issue the command
>
> sudo mount -o remount,rw /
> sudo dpkg --configue -a
>
> What is the gist of the output that you receive (especially the last
> lines)
>
> (you can shutdown from that mode by "sudo poweroff").
>
Revision history for this message
![]() |
#10 |
You have to find the right timing.
Try again, hitting the left shit key several times, starting very early in the boot process.
Revision history for this message
![]() |
#11 |
after several attempts I still end up at the same blinking cursor
however I get the flash of a line of text before the cursor I get the
same thing whether I shift key repeatedly , hold it down ,or do nothing.
I will keep trying but that is the result so far
On 11/5/2023 2:36 PM, Manfred Hampl wrote
> Your question #708316 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> You have to find the right timing.
> Try again, hitting the left shit key several times, starting very early in the boot process.
>
Revision history for this message
![]() |
#12 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.
Revision history for this message
![]() |
#13 |
after many attempts the most I get is a blinking cursor and a black
screen and no keyboard response at all. Is all I can do is reformat the
partition and re install ?
On 11/21/23 05:35, Launchpad Janitor wrote:
> Your question #708316 on Ubuntu changed:
> https:/
>
> Status: Open => Expired
>
> Launchpad Janitor expired the question:
> This question was expired because it remained in the 'Open' state
> without activity for the last 15 days.
>
Revision history for this message
![]() |
#14 |
You need the grub menu.
If you get a blinking cursor, then you have already missed the moment where you have to press the left shift key.
(another possibility is booting an installer in the "try Ubuntu without installing" mode and then trying to re-install the kernel to your disk partition)
Revision history for this message
![]() |
#15 |
It will probably be Monday before I get access to that computer again
(traveling for the holidays) which CD would be the better choice I have
both 20.04 and 22.04 available.
On 11/21/23 13:06, Manfred Hampl wrote:
> Your question #708316 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> You need the grub menu.
> If you get a blinking cursor, then you have already missed the moment where you have to press the left shift key.
>
> (another possibility is booting an installer in the "try Ubuntu without
> installing" mode and then trying to re-install the kernel to your disk
> partition)
>
Revision history for this message
![]() |
#16 |
Usually the advice is using the installer with the release that's installed on the disk, but any version should work.
Revision history for this message
![]() |
#17 |
I have tried both suggested methods several times with no success with
the installer either I get the live CD or it wants to wipe the partition
and reinstall fresh. I have tried this with both 20.04 and 22.04 with
the same results. I have a new SSD arrived late yesterday I will move
this SSD to an external enclosure where I can recover every thing
except the settings for 20.04 that failed the upgrade to 22.04
On 11/21/2023 2:31 PM, Manfred Hampl wrote:
> Your question #708316 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> Usually the advice is using the installer with the release that's
> installed on the disk, but any version should work.
>
Revision history for this message
![]() |
#18 |
"the installer either I get the live CD or it wants to wipe the partition"
Yes, that's the starting point.
You have to boot the installer in live mode ("Try Ubuntu without installing") and then change-root into the installation on the hard disk,
See https:/
Can you help with this problem?
Provide an answer of your own, or ask Mark for more information if necessary.