Upgrade to 20.04 problems -seems stuck in a loop at 'Setting software channels'
After many unsuccessful attempts to upgrade, this time I got as far as "Setting new software channels" "Caculating the changes." It has been stuck there for a couple of hours now. When I went to reboot, I got a warning message, and so stopped the restart.
What should I do? The "Distribution Upgrade " box is still open, with the busy indicator still going back and forth.
I am upgrading from 18.04.3LTS
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Manfred Hampl
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Have you tried in the terminal instead? Run:
sudo do-release-upgrade
The output will be useful
Revision history for this message
|
#2 |
I tried the update in the terminal as you suggest. It gives me back
"Please install all available updates for your release before
upgrading." When I go to Software Updater, it says it has to wait for
Focal to finish. I tried it a second time and it gave me "Package
dependendcies cannot be resolved" "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:
gsettings-
What should I do? (The info box for the Distribution Upgrade is still
open and running.)
T.E.
On 4/26/21 6:45 PM, actionparsnip wrote:
> Your question #696766 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> actionparsnip proposed the following answer:
> Have you tried in the terminal instead? Run:
>
> sudo do-release-upgrade
>
> The output will be useful
>
Revision history for this message
|
#3 |
I'm pretty sure it is still trying (unsuccessfully) to upgrade and is
stuck. But it means I cannot proceed until I stop the failing upgrade.
T.E.
On 4/26/21 9:12 PM, Thomas Ehrenberg wrote:
> I tried the update in the terminal as you suggest. It gives me back
> "Please install all available updates for your release before
> upgrading." When I go to Software Updater, it says it has to wait
> for Focal to finish. I tried it a second time and it gave me "Package
> dependendcies cannot be resolved" "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:
>
> gsettings-
>
> What should I do? (The info box for the Distribution Upgrade is still
> open and running.)
>
>
>
> T.E.
> On 4/26/21 6:45 PM, actionparsnip wrote:
>> Your question #696766 on Ubuntu changed:
>> https:/
>>
>> Status: Open => Answered
>>
>> actionparsnip proposed the following answer:
>> Have you tried in the terminal instead? Run:
>>
>> sudo do-release-upgrade
>>
>> The output will be useful
>>
Revision history for this message
|
#4 |
What is the output of:
sudo apt update
sudo apt upgrade
Thanks
Revision history for this message
|
#5 |
Hello actionparsnip,
Here it is:
thomas@
[sudo] password for thomas:
Reading package lists... Done
E: Could not get lock /var/lib/
temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/
thomas@
E: Could not get lock /var/lib/
temporarily unavailable)
E: Unable to acquire the dpkg frontend lock
(/var/lib/
thomas@
Thank you.
T.E.
On 4/27/21 3:01 AM, actionparsnip wrote:
> Your question #696766 on Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> actionparsnip requested more information:
> What is the output of:
>
> sudo apt update
> sudo apt upgrade
>
> Thanks
>
Revision history for this message
|
#6 |
If you are running updates then let them finish. If they have finished then reboot the system. If this still doesn't sort the issue then run:
sudo fuser -vki /var/lib/
and select to kill the process. This will free up the packages.
Revision history for this message
|
#7 |
I was running updates - the computer is in a loop and cannot finish.
I ran your command; here is the result:
thomas@
dpkg --configure -a
[sudo] password for thomas:
fuser: Invalid option /
Usage: fuser [-fIMuvw] [-a|-s] [-4|-6] [-c|-m|-n SPACE]
[-k [-i] [-SIGNAL]] NAME...
fuser -l
fuser -V
Show which processes use the named files, sockets, or filesystems.
-a,--all display unused files too
-i,--interactive ask before killing (ignored without -k)
-I,--inode use always inodes to compare files
-k,--kill kill processes accessing the named file
-l,-
-m,--mount show all processes using the named filesystems or
-M,-
-n,--namespace SPACE search in this name space (file, udp, or tcp)
-s,--silent silent operation
-SIGNAL send this signal instead of SIGKILL
-u,--user display user IDs
-v,--verbose verbose output
-w,--writeonly kill only processes with write access
-V,--version display version information
-4,--ipv4 search IPv4 sockets only
-6,--ipv6 search IPv6 sockets only
- reset options
udp/tcp names: [local_
dpkg: error: dpkg frontend is locked by another process
thomas@
-k,--kill: command not found
thomas@
I am worried that, since it got stuck in the middle of the upgrade, if I
force the system to shut down via the power button, I will not be able
to restart.
T.E.
On 4/27/21 8:15 AM, actionparsnip wrote:
> Your question #696766 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> actionparsnip proposed the following answer:
> If you are running updates then let them finish. If they have finished
> then reboot the system. If this still doesn't sort the issue then run:
>
> sudo fuser -vki /var/lib/
>
> and select to kill the process. This will free up the packages.
>
Revision history for this message
|
#8 |
It's fine to do. The package system will recover.
Try just:
sudo fuser -vki /var/lib/dpkg/lock
Should unlock the package for you. Also run:
pe -ef | egrep 'apt|dpkg' | grep -v grep
Kill the processes that show
Revision history for this message
|
#9 |
Thank you.
The first kill worked.
It did not like the pe command on the second. Here's the result:
thomas@
[sudo] password for thomas:
/var/lib/dpkg/lock: root 4296 F.... focal
Kill process 4296 ? (y/N) y
thomas@
pe: command not found
thomas@
T.E.
On 4/28/21 3:20 AM, actionparsnip wrote:
> Your question #696766 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> actionparsnip proposed the following answer:
> It's fine to do. The package system will recover.
>
> Try just:
>
> sudo fuser -vki /var/lib/dpkg/lock
>
> Should unlock the package for you. Also run:
>
> pe -ef | egrep 'apt|dpkg' | grep -v grep
>
> Kill the processes that show
>
Revision history for this message
|
#10 |
(Typo error, should have been ps instead of pe)
What do you now get for the commands
sudo apt update
sudo apt upgrade
Revision history for this message
|
#11 |
D'oh. My mistake. The lock should now be gone.
Revision history for this message
|
#12 |
I was able to upgrade successfully - almost. 20.04 is loaded in. I shut the system off last night and this morning I cannot complete the boot. It gets as far as the sign-in, when I enter my password, it processes, the screen goes purple and then dark then loops back to the sign-in. It is not saying that it’s the incorrect password, it just starts over. I can’t even get to the terminal.
TE
> On Apr 28, 2021, at 2:01 PM, Manfred Hampl <email address hidden> wrote:
>
> Your question #696766 on Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> (Typo error, should have been ps instead of pe)
>
> What do you now get for the commands
>
> sudo apt update
> sudo apt upgrade
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https:/
>
> You received this question notification because you asked the question.
Revision history for this message
|
#13 |
Workarounds for such situation:
1. on the login page press ctrl-alt-F3
This will hopefully start a virtual console where you can log in with username and password and then work like a terminal window (except being able to copy/paste). For rebooting enter "sudo reboot"
or
2. when you press the left shift key early during boot you should get the grub menu.
There you can select advanced options and root command prompt.
after issuing
mount -o remount,rw /
you are logged in with admin rights and also have all possibilities.
I suggest that you check whether all updates have been installed with the commands
sudo apt update
sudo apt full-upgrade
(This requires network connection, I hope that your system automatically connects to your router - if not, then this requires additional commands).
Revision history for this message
|
#14 |
When I press curl-alt-F3 it gives me the virtual terminal,. When I then enter “sudo reboot” it loops back around to the login page again.
However, from the ctrl-alt-F3 virtual terminal I then did the sudo apt update and am now doing the sudo apt upgrade. Will keep you posted.
Thank you.
TE
> On Apr 29, 2021, at 9:30 AM, Manfred Hampl <email address hidden> wrote:
>
> Your question #696766 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> Workarounds for such situation:
>
> 1. on the login page press ctrl-alt-F3
> This will hopefully start a virtual console where you can log in with username and password and then work like a terminal window (except being able to copy/paste). For rebooting enter "sudo reboot"
>
> or
>
> 2. when you press the left shift key early during boot you should get the grub menu.
> There you can select advanced options and root command prompt.
> after issuing
> mount -o remount,rw /
> you are logged in with admin rights and also have all possibilities.
>
> I suggest that you check whether all updates have been installed with
> the commands
>
> sudo apt update
> sudo apt full-upgrade
>
> (This requires network connection, I hope that your system automatically
> connects to your router - if not, then this requires additional
> commands).
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
Revision history for this message
|
#15 |
During the upgrade (@22%) it asks:
Configuration file ‘/etc/mime.types’
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it? Your options are:
Y or I : install the package maintainers version
N or O : keep your currently installed version
D : show the differences between the versions
Z. : start a shell to examine the situation
The default action is to keep your current version.
*** mime.types (Y/I/N/O/D/Z) [default=N] ?
Suggestions for what I should do?
TE
> On Apr 29, 2021, at 10:17 AM, T Ehrenberg <email address hidden> wrote:
>
> When I press curl-alt-F3 it gives me the virtual terminal,. When I then enter “sudo reboot” it loops back around to the login page again.
> However, from the ctrl-alt-F3 virtual terminal I then did the sudo apt update and am now doing the sudo apt upgrade. Will keep you posted.
> Thank you.
>
> TE
>
>> On Apr 29, 2021, at 9:30 AM, Manfred Hampl <email address hidden> wrote:
>>
>> Your question #696766 on Ubuntu changed:
>> https:/
>>
>> Status: Open => Answered
>>
>> Manfred Hampl proposed the following answer:
>> Workarounds for such situation:
>>
>> 1. on the login page press ctrl-alt-F3
>> This will hopefully start a virtual console where you can log in with username and password and then work like a terminal window (except being able to copy/paste). For rebooting enter "sudo reboot"
>>
>> or
>>
>> 2. when you press the left shift key early during boot you should get the grub menu.
>> There you can select advanced options and root command prompt.
>> after issuing
>> mount -o remount,rw /
>> you are logged in with admin rights and also have all possibilities.
>>
>> I suggest that you check whether all updates have been installed with
>> the commands
>>
>> sudo apt update
>> sudo apt full-upgrade
>>
>> (This requires network connection, I hope that your system automatically
>> connects to your router - if not, then this requires additional
>> commands).
>>
>> --
>> If this answers your question, please go to the following page to let us
>> know that it is solved:
>> https:/
>>
>> If you still need help, you can reply to this email or go to the
>> following page to enter your feedback:
>> https:/
>>
>> You received this question notification because you asked the question.
>
Revision history for this message
|
#16 |
1. of course it should not have been "sudo reboot" but "sudo shutdown".
2. It is not possible to give "the right" answer without knowing all details of your system.
I think it does not make much difference whether you answer "Y" or "N".
You can try "D" to see what the difference between your current version and the new version is, but I am not sure if it is easy to understand.
Revision history for this message
|
#17 |
I went with the system version. Seems OK.
At this point I am successfully booted up, but my desktop does not populate!
Any suggestions?
T.E.
On 4/29/21 11:01 AM, Manfred Hampl wrote:
> Your question #696766 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> 1. of course it should not have been "sudo reboot" but "sudo shutdown".
>
> 2. It is not possible to give "the right" answer without knowing all details of your system.
> I think it does not make much difference whether you answer "Y" or "N".
>
> You can try "D" to see what the difference between your current version
> and the new version is, but I am not sure if it is easy to understand.
>
Revision history for this message
|
#18 |
"my desktop does not populate"
What do you see after logging in?
Does ctrl-alt-t open a terminal window?
Revision history for this message
|
#19 |
Blank purple screen with the Focal Fossa cat; sidebar with 'favorites'.
"Desktop" (with my desktop files) is a file in "Files" but nothing on
the deskstop screen. So far programs seem to be functioning ok. Yes, I
can get to a terminal with ctrl-alt-t. alt-F2 opens a command box as well.
T.E.
On 4/29/21 1:55 PM, Manfred Hampl wrote:
> Your question #696766 on Ubuntu changed:
> https:/
>
> Status: Open => Needs information
>
> Manfred Hampl requested more information:
> "my desktop does not populate"
> What do you see after logging in?
>
> Does ctrl-alt-t open a terminal window?
>
Revision history for this message
|
#20 |
The gnome desktop normally does not show icons.
If you want to have this, then you must activate it.
See e.g. https:/
Revision history for this message
|
#21 |
Thank you Manfred,
I am up and running in 20.04. I thank the Ubuntu community and
particularly actionparsnip and Manfred.
T.E.
On 4/29/21 2:50 PM, Manfred Hampl wrote:
> Your question #696766 on Ubuntu changed:
> https:/
>
> Status: Open => Answered
>
> Manfred Hampl proposed the following answer:
> The gnome desktop normally does not show icons.
> If you want to have this, then you must activate it.
> See e.g. https:/
>
Revision history for this message
|
#22 |
If the problem has been resolved, then please set the status of this question document to "solved".
Revision history for this message
|
#23 |
Thanks Manfred Hampl, that solved my question.
Revision history for this message
|
#24 |
Thank you so much. Focal fossa up and running.