Quantcast
Channel: Ubuntu Forums - Installation & Upgrades
Viewing all 26379 articles
Browse latest View live

[ubuntu] Live CD not working 20.10

$
0
0
I had an issue with an upgrade from 20.04 LTS to 20.10, so I thought I would just reinstall over the failed upgrade. I have a dual boot pc with windows.

I burned a live cd and after the check it would not load, had to shut down and use the ubuntu basic graphics or something like that. Went through the install process using the overwrite the existing 20.10..... then I got an error.

Executing ‘grub-install/dev/sda’ failed
This is a fatal error

So, I burned another disk from the windows side and got the same issue with only loading the live cd with basic graphics....

Any suggestions?

d

apt-get upgrade doesn't finish on accountsservice package

$
0
0
I did a simple "apt-get update" followed by "apt-get upgrade"
which has never had any problems.
After finishing all the other updates, upgrade
just stayed there never finishing at the
accountsservice package.

I control-C'd out of it then followed it up with a
"dpkg --configure -a" which also just stayed
there, apparently not doing anything of substance
but not hung either.

Here's some relevant information:



root@XYZ:/home/person# dpkg --configure -a
Setting up accountsservice (0.6.40-2ubuntu11.6) ...





person@XYZ:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.7 LTS
Release: 16.04
Codename: xenial

# uname -a
Linux XYZ 4.4.0-173-generic #203-Ubuntu SMP Wed Jan 15 02:55:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux


What should I do?
Thanks in advance.

-sgc2c

BAD_SYSTEM_CONFIG_INFO error after istalling Ubuntu Budgie

$
0
0
Hi guys! I don't know how to handle this situation, I'm really new to linux. I hope you can help me save my pc!

I istalled Ubuntu Budgie 20.10 in a partition on my laptop, after that I'm not able to use windows, it gives me this error "BAD_SYSTEM_CONFIG_INFO"
I tryed some tutorials but they wont work

i tryed boot repair on ubuntu also. It doesen't work, this is the link it said to give to you guys

http://paste.ubuntu.com/p/Jwc4QcgyrW/

hope you guys can help me!

thanks!

[lubuntu] Exclamation marks on icons after upgrade to 20.04

$
0
0
After upgrading from Lubuntu 18 LTS to Lubuntu 20 LTS, white exclamation marks in a black circle appear over top of some of desktop icons. What is the cause of this and is there a fix?
Attached Images

[ubuntu] Can't install and boot Ubuntu 20.10 to USB flash drive (BusyBox Initramfs)

$
0
0
I installed Ubuntu 20.10 from a USB flash drive to another USB flash drive and the installation process completed successfully, but when I boot the system, it boots into BusyBox with a initramfs prompt. I tried running the fsck command, but it doesn't exist.

The laptop is a Dell XPS 15 with secure boot disabled. I also have the internal SSD disabled, because I don't want Ubuntu touching that.

[SOLVED] "Updated" to 16.04.7 now having issues playing video

$
0
0
I am using canned Firefox and having issues playing videos.
Not so with Google Chrome.

Not interested in "upgrade" , video issue is NOT a good reason to "upgrade".

Maybe periodic " experienced internal error" is better reason to "upgrade".
( Reported so many times it won't pass my "report" anymore. )

Anyway , Firefox is often automatically "updated" but the problem persists.
Mrs Google reports similar history with older Ubuntu versions - so reporting to Firefox seems redundant as results
of reporting cannot be easy identified.

When replying , please concentrate your comments on the following:

What are the chances Ubuntu will fix this in 16 ?


Cheers

[ubuntu] Can't boot to Windows anymore (Dual boot Windows 10 / Ubuntu 20.04.1)

$
0
0
Hello all,

I hope this is the right place to post this.

So I installed Ubuntu 20.04.1 a few days ago on my PC. I had a dual boot with Windows 10 on my first SSD (which was installed first), and Ubuntu on my 2nd SSD (I followed these instructions: https://askubuntu.com/questions/7269...te-hard-drives), and it all worked fine initially.

However today after a Windows update, my PC booted straight to Windows. After entering
Code:

bcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi
in Windows command line I was able to get GRUB back and to boot into Ubuntu.

Unfortunately now I can't boot into Windows. Windows Boot Manager does still appear in GRUB but selecting it does nothing.

I unsuccessfully tried
Code:

sudo update-grub
, as well as creating
Code:

/boot/grub/custom.cfg
as recommended here: https://askubuntu.com/questions/2179...ntu-how-to-fix. I did get a "Windows (UEFI)" entry in GRUB but it didn't have any effect either.

Finally I installed boot-repair, launched Recommended repair, and got a "Boot successfully repaired" message with the following pastebin: https://paste.ubuntu.com/p/FgwRKnvgD9/
However now I do not have access to GRUB anymore, it boots straight to Ubuntu instead.

I also noticed that now in UEFI, the fixed boot order priorities includes my 2nd drive (Ubuntu) instead of the first. Another option, UEFI Hard Disk Drive BBS Priorities, gives a list of 3 options: Ubuntu SATA1 (which I set first, as apparently recommended by boot-repair), Windows Boot Manager SATA1, & Ubuntu SATA2. Still boots straight to Ubuntu regardless.

So now I'm unsure what to do to get GRUB & Windows back. Any help would be much appreciated.

[ubuntu] Missing data at archive.ubuntu.com

$
0
0
Code:


$ sudo apt -y update && sudo apt -y upgrade && sudo apt autoremove -y && sudo apt install freeipa-client

* * * * * * * * * * * * * * * * * * * *

Need to get 24.7 MB of archives.
After this operation, 115 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Err:1 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic/main amd64 python-augeas all 0.5.0-1+ubuntu18.04.1+certbot+1
  Temporary failure resolving 'ppa.launchpad.net'
Ign:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libwbclient0 amd64 2:4.7.6+dfsg~ubuntu-0ubuntu2.21
Ign:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython2.7-minimal amd64 2.7.17-1~18.04ubuntu1.2
Ign:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 python2.7-minimal amd64 2.7.17-1~18.04ubuntu1.2
Err:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 python-minimal amd64 2.7.15~rc1-1
  Temporary failure resolving 'archive.ubuntu.com'
Ign:6 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython2.7-stdlib amd64 2.7.17-1~18.04ubuntu1.2
Ign:7 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 python2.7 amd64 2.7.17-1~18.04ubuntu1.2
Err:8 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython-stdlib amd64 2.7.15~rc1-1
  Temporary failure resolving 'archive.ubuntu.com'
Err:9 http://archive.ubuntu.com/ubuntu bionic/main amd64 python amd64 2.7.15~rc1-1
  Temporary failure resolving 'archive.ubuntu.com'

http://archive.ubuntu.com/

Why is this archive empty? What am I missing!?

Focal dist-upgrader-all

Attempts to upgrade from 18.04 to 20.04 result in EFI error

$
0
0
I have been a Ubuntu user for ten years but any time it becomes apparent that an issue will require anything beyond the basic terminal commands to resolve I am lost and require help. This time I got a notice that 20.04 was available and I elected to install it but was stopped a few minutes into the process by the following error message: "EFI System Partiton (ESP) not usable
Your EFI System Partition (ESP) is not mounted at /boot/efi. Please ensure that it is properly configured and try again."

I did a little bit of research and came across threads full of commands that are way over my head. Now what do I do? Any instructions will have to assume that I am an end user so if you're asking me to enter a command and post the results I'll need an explanation how to do it. I have a purpose built Ubuntu system purchased from Zareason and my wife has a System76 laptop so I may be facing the same situation with that. Ironically my old junky Dell laptop that I use to look things up in the garage running on Xubuntu upgraded with no issues.

[SOLVED] Can't see the partition where Ubuntu is installed on Windows and data loss

$
0
0
I installed dual systems on my computer with Windows 10 first and then Ubuntu 20.04 LTS.

I used create USB bootable tool to install Ubuntu and before that I freed up 300G disk space on Windows.

But during the installation I chose to "Install Ubuntu Alongside with Windows" and also chose to assign 300G to Ubuntu and Ubuntu did its automatic installation.

Everything went smooth during the installation. But when I logged into Windows and I found the were 300G lost on disk space when I checked in the Disk Management and I did not find the partition where Ubuntu is installed! There are only 2 partitions (D & E where my personal data located in) and there is a red cross on the lower left of the sign of each partition (I cannot suppress or expand each of them) and the 300G I freed up has gone.

And I also found that the more I logged in Ubuntu the more data loss on Windows.

I don't really care about my data on my disk(coz I've backed them up), I just don't want two systems conflict each other.

So I want to reinstall the Ubuntu on the right partition and also Windows, just can anyone tell me what is the simplest way to solve this problem?

Many many thanks!!!!

[SOLVED] New to Ubuntu and Linux - Trouble with installation due to Intel RST

$
0
0
Hi, as the title says, I am completely new to both Ubuntu and Linux as a whole. I decided to try out using Ubuntu on my HP laptop. However, I am not able to install it due to RST. If I understand correctly, I should go to BIOS > Advanced Settings and the switch SATA operation mode from RST to AHCI.

But the real problem is this: HP doesn't allow access to Advanced Settings in BIOS on it's consumer-grade laptops.

What should I do?





Side Note: I also tried installing Pop_OS! on the same laptop and it worked without any problems.

Stuck on Asus Screen with Ubuntu

$
0
0
When I try to buy Ubuntu from a 32 gig Usb drive that flashed correctly it goes to an Asus start up screen that also says Ubuntu. It freezes there. I took a picture.

[SOLVED] upgrade from 20.04 to 20.10 cannot write problem

$
0
0
Hello,

the other day I tried to upgrade from 20.04 to 20.10.

Upgrading was going fine until I was notified that internet connection was disconnected. This had happened to other upgrades as well, yet at a moment later I was able to see a message that was like that: no write permissions...

I do not remember exactly the message, which disappeared from screen, and then a new message informed me that the upgrade did take place with some errors and that I had to issue the command:
dpkg --configure -a.

I was not able to open any application at that time from panel. So I decided to drop to command line and restart my system. (Maybe it would have been a nice idea to issue the command proposed). The system did not proceed to boot normally so it was forced to restart.

Then I came across BIOS. I did not change anything and proceeded to boot, yet errors appeared on screen with a distinct one being:
[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0) ] ...something like that.

I typed: fsck /dev/sda1 -y
and saw many errors getting fixed.

Then I think that I typed reboot to initramfs prompt, and was greeted with grub.

I chose just the previous kernel I was using prior to the upgrade at recovery mode and typed:
dpkg --configure -a

which continued the upgrade.

When finished I opened a terminal and typed:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get autoremove

with the last command getting rid many files.

My system now seems to be fine.

Just for anyone that will encounter the same behavior.

Regards!

[lubuntu] install help files for lazarus pascal IDE

$
0
0
I installed the lazarus pascal IDE but it didn't install the help files.

Create a new application project.
It creates a new empty project.

Put the cursor in TForm:
Code:

type
  TForm1 = class(TForm)

Press F1.
It should open a help file but instead shows this error:

Code:

lcl.chm not found. Please put the chm help files in
/usr/lib/lazarus/2.0.6/docs/chm;/usr/lib/lazarus/2.0.6/docs/html;/usr/lib/lazarus/2.0.6/docs/html/lcl
 or set the path to lcl.chm rtl.chm fcl.chm with "HelpFilesPath" in
 Environment Options -> Help -> Help Options ->
 under HelpViewers - CHMHelpViewer


[ubuntu] Partitioning

$
0
0
I recently installed Ubuntu Server 20.04.1 LTS. I had it automatically partition my drive for me. I noticed that my root directory shows the following:
Code:

Filesystem                        Size  Used Avail Use% Mounted on
/dev/mapper/ubuntu--vg-ubuntu--lv  196G  6.1G  180G  4% /

It is a 1 TB WD HD.
Doing a fdisk on it:
Code:

Device  Start      End  Sectors SizeType
/dev/sda1    2048    1050623    1048576  512M EFI System
/dev/sda2  1050624    3147775    2097152    1G Linux filesystem
/dev/sda3  3147776 1953521663 1950373888  930G Linux filesystem

Which present a few questions. What is sda2? I assume that my root partition is on sda3. Why is it showing a size of only 196G available? Does that have to do with LVM? Will it automatically grow in size as need be? Lastly, do I really only have available to me ~930GB out of the 1TB?

[ubuntu] LVM & mdadm Guru (20.04)

$
0
0
I'm currently assembling my latest build. I have two SSDs (burner OS) configure raid0 with mdadm (md0), then add to VG, then partition out multiple \'s, \home, excetera.

I was hoping someone with strong skills would help me walkthrough the process.

[ubuntu] How to restore Windows boot loader and remove grub

$
0
0
Hi,
I have a laptop with Windows 10 on it (Windows 10 is encrypted).
I boot from a USB key when I want to boot Ubuntu.
Just installed Ubuntu 20.10 on USB key and made sure everything to do with grub and Ubuntu was specific to USB key.
Have followed same method many times without issue with previous versions of Ubuntu.. and the boot loader and Windows 10 was not affected on main drive.
Not this time however. For some reason it tried to install Grub on main drive instead of USB key only.

Windows 10 wont boot now as stand alone drive or from grub menu on USB Key.

I know I know... I should have taken laptop apart and removed internal drive before installing Ubuntu on USB key.

I installed boot-repair and captured boot info here:
https://paste.ubuntu.com/p/cVy8PMcXBp/

Hoping I can recover MBR so Windows 10 boots fine again.

Any help appreciated.

[ubuntu] Broken python2 packages preventing upgrade to 20.04

$
0
0
Hello all, I am trying to upgrade from Ubuntu 19.10 to 20.04 using "do-release-upgrade" in the terminal. I receive the following error. I am not sure what to do next. I know linux pretty well, and I am comfortable in the terminal if anyone has any ideas. I've provided a few logs, if there is another I should be looking at I can post those as well.

Code:

Checking package manager
Reading package lists... Done   
Building dependency tree         
Reading state information... Done

Calculating the changes
Calculating the changes
Could not calculate the upgrade
 
An unresolvable problem occurred while calculating the upgrade.

If none of this applies, then please report this bug using the
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If
you want to investigate this yourself the log files in
'/var/log/dist-upgrade' will contain details about the upgrade.
Specifically, look at 'main.log' and 'apt.log'.

Restoring original system state

Aborting
Reading package lists... Done   
Building dependency tree         
Reading state information... Done

main.log
Code:

2020-11-14 23:52:16,345 INFO Using config files '['./DistUpgrade.cfg']'
2020-11-14 23:52:16,345 INFO uname information: 'Linux CF-31-Ubuntu 5.3.0-64-generic #58-Ubuntu SMP Fri Jul 10 19:33:51 UTC 2020 x86_64'
2020-11-14 23:52:16,757 INFO apt version: '1.9.4ubuntu0.1'
2020-11-14 23:52:16,757 INFO python version: '3.7.5 (default, Apr 19 2020, 20:18:17)
[GCC 9.2.1 20191008]'
2020-11-14 23:52:16,761 INFO release-upgrader version '20.04.28' started
2020-11-14 23:52:16,770 INFO locale: 'en_US' 'UTF-8'
2020-11-14 23:52:16,825 DEBUG screen returned: 'No Sockets found in /run/screen/S-root.

'
2020-11-14 23:52:16,825 INFO re-exec inside screen: '['screen', '-e', '\\0\\0', '-c', 'screenrc', '-S', 'ubuntu-release-upgrade-screen-window', '/tmp/ubuntu-release-upgrader-5ufub9do/focal', '--mode=server', '--frontend=DistUpgradeViewText']'

apt.log
Code:

Log time: 2020-11-14 23:13:14.051867
Log time: 2020-11-14 23:13:17.260095
Log time: 2020-11-14 23:14:28.600601
  MarkInstall python2-dbg:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > FU=1
  Installing python2 as Depends of python2-dbg
    MarkInstall python2:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > FU=0
    Installing python2-minimal as PreDepends of python2
      MarkInstall python2-minimal:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > FU=0
    Installing libpython2-stdlib as Depends of python2
      MarkInstall libpython2-stdlib:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > FU=0
  Installing libpython2-dbg as Depends of python2-dbg
    MarkInstall libpython2-dbg:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > FU=0
Starting pkgProblemResolver with broken count: 7
Starting 2 pkgProblemResolver with broken count: 7
Investigating (0) python:amd64 < 2.7.17-1 @ii mK Ib >
Broken python:amd64 Depends on python2:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > (= 2.7.17-1)
  Considering python2:amd64 184 as a solution to python:amd64 343
  Added python2:amd64 to the remove list
  Fixing python:amd64 via keep of python2:amd64
  MarkKeep python2:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > FU=0
 Try to Re-Instate (0) python2:amd64
Re-Instated python2:amd64 (8 vs 7)
Investigating (0) python-minimal:amd64 < 2.7.17-1 @ii mK Ib >
Broken python-minimal:amd64 Depends on python2-minimal:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > (= 2.7.17-1)
  Considering python2-minimal:amd64 4 as a solution to python-minimal:amd64 179
  Added python2-minimal:amd64 to the remove list
  Fixing python-minimal:amd64 via keep of python2-minimal:amd64
  MarkKeep python2-minimal:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > FU=0
Investigating (0) libpython-stdlib:amd64 < 2.7.17-1 @ii mK Ib >
Broken libpython-stdlib:amd64 Depends on libpython2-stdlib:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > (= 2.7.17-1)
  Considering libpython2-stdlib:amd64 4 as a solution to libpython-stdlib:amd64 179
  Added libpython2-stdlib:amd64 to the remove list
  Fixing libpython-stdlib:amd64 via keep of libpython2-stdlib:amd64
  MarkKeep libpython2-stdlib:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > FU=0
 Try to Re-Instate (0) python2-minimal:amd64
  MarkKeep python2-minimal:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > FU=0
 Try to Re-Instate (0) libpython2-stdlib:amd64
  MarkKeep libpython2-stdlib:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > FU=0
Investigating (0) python-dev:amd64 < 2.7.17-1 @ii mK Ib >
Broken python-dev:amd64 Depends on python2-dev:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > (= 2.7.17-1)
  Considering python2-dev:amd64 2 as a solution to python-dev:amd64 3
  Added python2-dev:amd64 to the remove list
  Fixing python-dev:amd64 via keep of python2-dev:amd64
  MarkKeep python2-dev:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > FU=0
 Try to Re-Instate (0) python2-dev:amd64
  MarkKeep python2-dev:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > FU=0
Investigating (0) python2-dev:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umH Ib >
Broken python2-dev:amd64 Depends on python2:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > (= 2.7.17-1)
  Considering python2:amd64 184 as a solution to python2-dev:amd64 2
  Removing python2-dev:amd64 rather than change python2:amd64
  MarkDelete python2-dev:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umH Ib > FU=0
Investigating (0) libpython-dbg:amd64 < 2.7.17-1 @ii mK Ib >
Broken libpython-dbg:amd64 Depends on libpython2-dbg:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > (= 2.7.17-1)
  Considering libpython2-dbg:amd64 1 as a solution to libpython-dbg:amd64 0
  Removing libpython-dbg:amd64 rather than change libpython2-dbg:amd64
  MarkDelete libpython-dbg:amd64 < 2.7.17-1 @ii mK Ib > FU=0
Investigating (0) libpython-all-dbg:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umH Ib >
Broken libpython-all-dbg:amd64 Depends on libpython-dbg:amd64 < 2.7.17-1 @ii mR > (= 2.7.17-1)
  Considering libpython-dbg:amd64 0 as a solution to libpython-all-dbg:amd64 0
  Re-Instated libpython-all-dbg:amd64
Investigating (0) python-dbg:amd64 < 2.7.17-1 @ii mK Ib >
Broken python-dbg:amd64 Depends on libpython-dbg:amd64 < 2.7.17-1 @ii mR > (= 2.7.17-1)
  Considering libpython-dbg:amd64 0 as a solution to python-dbg:amd64 -1
  Removing python-dbg:amd64 rather than change libpython-dbg:amd64
  MarkDelete python-dbg:amd64 < 2.7.17-1 @ii mK Ib > FU=0
Investigating (0) python-all-dbg:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umH Ib >
Broken python-all-dbg:amd64 Depends on libpython-all-dbg:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > (= 2.7.17-1)
  Considering libpython-all-dbg:amd64 0 as a solution to python-all-dbg:amd64 -1
  Re-Instated python-all:amd64
  Re-Instated python-all-dbg:amd64
Investigating (1) python:amd64 < 2.7.17-1 @ii mK Ib >
Broken python:amd64 Depends on python2:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > (= 2.7.17-1)
  Considering python2:amd64 184 as a solution to python:amd64 343
  Added python2:amd64 to the remove list
  Fixing python:amd64 via keep of python2:amd64
  MarkKeep python2:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > FU=0
Investigating (1) python-dev:amd64 < 2.7.17-1 @ii mK Ib >
Broken python-dev:amd64 Depends on python2-dev:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umR > (= 2.7.17-1)
  Considering python2-dev:amd64 2 as a solution to python-dev:amd64 3
  Added python2-dev:amd64 to the remove list
  Fixing python-dev:amd64 via keep of python2-dev:amd64
  MarkKeep python2-dev:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umR > FU=0
Investigating (1) python-all:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib >
Broken python-all:amd64 Depends on python2:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umH > (= 2.7.17-2ubuntu4)
  Considering python2:amd64 184 as a solution to python-all:amd64 2
  MarkKeep python-all:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > FU=0
  Holding Back python-all:amd64 rather than change python2:amd64
Investigating (1) python-all-dbg:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib >
Broken python-all-dbg:amd64 Depends on python2:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umH > (= 2.7.17-2ubuntu4)
  Considering python2:amd64 184 as a solution to python-all-dbg:amd64 -1
  MarkKeep python-all-dbg:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > FU=0
  Removing python-all-dbg:amd64 rather than change python2:amd64
  MarkDelete python-all-dbg:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umH Ib > FU=0
Investigating (2) python2-dbg:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii pumU Ib >
Broken python2-dbg:amd64 Depends on python2:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umH > (= 2.7.17-2ubuntu4)
  Considering python2:amd64 184 as a solution to python2-dbg:amd64 10000
Done
Log time: 2020-11-14 23:14:31.859002

grep Broken /var/log/dist-upgrade/apt.log
Code:

Broken python:amd64 Depends on python2:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > (= 2.7.17-1)
Broken python-minimal:amd64 Depends on python2-minimal:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > (= 2.7.17-1)
Broken libpython-stdlib:amd64 Depends on libpython2-stdlib:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > (= 2.7.17-1)
Broken python-dev:amd64 Depends on python2-dev:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > (= 2.7.17-1)
Broken python2-dev:amd64 Depends on python2:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > (= 2.7.17-1)
Broken libpython-dbg:amd64 Depends on libpython2-dbg:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > (= 2.7.17-1)
Broken libpython-all-dbg:amd64 Depends on libpython-dbg:amd64 < 2.7.17-1 @ii mR > (= 2.7.17-1)
Broken python-dbg:amd64 Depends on libpython-dbg:amd64 < 2.7.17-1 @ii mR > (= 2.7.17-1)
Broken python-all-dbg:amd64 Depends on libpython-all-dbg:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU > (= 2.7.17-1)
Broken python:amd64 Depends on python2:amd64 < 2.7.17-1 -> 2.7.17-2ubuntu4 @ii umU Ib > (= 2.7.17-1)
Broken python-dev:amd64 Depends on python2-dev:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umR > (= 2.7.17-1)
Broken python-all:amd64 Depends on python2:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umH > (= 2.7.17-2ubuntu4)
Broken python-all-dbg:amd64 Depends on python2:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umH > (= 2.7.17-2ubuntu4)
Broken python2-dbg:amd64 Depends on python2:amd64 < 2.7.17-1 | 2.7.17-2ubuntu4 @ii umH > (= 2.7.17-2ubuntu4)

Installation: Ubuntu20.04.1-desktop-amd64 iso fails on sha256sum test

$
0
0
I downloaded ubuntu-20.04.1-desktop-amd64.iso. I am from India and the browser shows that the download was from 'tifr.rs.in' -- your mirror in India?. I have downloaded twice on 14 Nov . Signature verification of the check sum file SHA256SUMS file is OK, but the command " sha256sum -c SHA256SUMS 2>&1" outputs error message -> "ubuntu-20.04.1-desktop-amd64.iso: FAILED". Looks like the mirror is broken. Earlier, I tried to upgrade from 18.04, but it did not work and I had to re-install Ubuntu 18.04.4. If I try to upgrade again I may have a non-working installation again.
Viewing all 26379 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>