Announcement

**pooky2483** · Mar 04, 2020, 10:39 AM

I am also getting an error in package updater;
Spawn of helper '/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py'
failed: failed to spawn /usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py:
Failed to execute child process “/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py” (No such file or directory)

And 'blocked updates'

**oshunluvr** · Mar 04, 2020, 11:03 AM

Yeah, you won't be able to launch Dolphin or Kate as root. That's changed for good. You should be able to edit a root owned file using Kate, then it will prompt you for the root password when you try and save. You can always use "sudo nano" in a konsole window to edit a root owned file.

Clearly, you have a mess in your /etc/apt/ folder, Looks like the 20auto-upgrades file got renamed from somewhere and all the sources got duplicated some how. I'd start digging around in there and undo whatever you can find. Your error list above is your guide. The messages clearly state the problems.

As far as held packages or blocked updates, there's usually a reason like an unmet dependency or there's more than one version available as an install candidate. I'd recommend ignoring that for now and cleaning up your apt mess first.

FYI: /etc/apt/apt.conf.d/20auto-upgrades should contain

Code:

APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";

unless it's been edited.

**oshunluvr** · Mar 04, 2020, 11:09 AM

BTW< I'm not using 20.04 but when I tried to use Updater on my 20.04 vbox install, it failed. You might want to try it from the command line. At least you'll get more meaningful error messages. @here at least, it worked fine from the CLI. Here's the commands:

Code:

pkcon refresh
pkcon get-updates
pkcon update

Obviously, clean up your sources first.

**pooky2483** · Mar 04, 2020, 12:41 PM

So, unlike 16.04 where I had to open dolphin or kate as root to be able to edit a file, now I can open a file as normal but when saving, I have to enter the root password.
I'd say that's an improvement.

Right, now down to business...
I'll be back ;-)

**pooky2483** · Mar 04, 2020, 12:46 PM

Originally posted by oshunluvr View Post

Clearly, you have a mess in your /etc/apt/ folder, Looks like the 20auto-upgrades file got renamed from somewhere

That's down to the upgrade from 16.04 to 18.04
Is it a necessary file or can it be deleted?

My 'sources.list.d' folder has '.list' & '.save' files in it, all with xenial in the filename, would it be safe to delete them as that's the old version.

It also looks like I can delete the xenial stuff from the 'sources.list' file also.

# deb cdrom:[Kubuntu 16.04.6 LTS _Xenial Xerus_ - Release amd64 (20190226)]/ xenial main multiverse restricted universe

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
# deb-src http://gb.archive.ubuntu.com/ubuntu/ xenial restricted main

## Major bug fix updates produced after the final release of the
## distribution.

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
deb http://archive.canonical.com/ubuntu/ xenial partner
# deb-src http://archive.canonical.com/ubuntu/ xenial partner

deb http://liveusb.info/multisystem/depot/ all hand
# deb-src http://liveusb.info/multisystem/depot/ all hand

deb https://www.mediahuman.com/packages/ubuntu/ xenial main
# deb-src https://www.mediahuman.com/packages/ubuntu/ xenial main
deb https://dl.winehq.org/wine-builds/ubuntu/ xenial main
# deb-src https://dl.winehq.org/wine-builds/ubuntu/ xenial main

deb http://security.ubuntu.com/ubuntu/ xenial-security main multiverse universe restricted

deb http://mirror.ratiokontakt.de/mirror/ubuntu/ xenial main universe restricted multiverse
deb http://mirror.ratiokontakt.de/mirror/ubuntu/ xenial-updates multiverse universe main restricted

**oshunluvr** · Mar 04, 2020, 01:12 PM

If you install xenial packages to a bionic install, you'll break things. I don't know why it didn't get cleaned up, but that's clearly why you're getting the majority of those messages.

Delete all xenial lines and try apt update again.

**claydoh** · Mar 04, 2020, 01:19 PM

Is that the entire sources.list?
if so, then all your sources are still set to 16.04, not 18.04 (Bionic)

Which makes me ask, based on this

I have just done a dist upgrade from 16.04 to 18.04 and I am having a complete breakdown.

By dist upgrade, do you mean that you ran sudo apt-get dist-upgrade ? If so, then you have NOT upgraded to 18.04.

Either way, something looks broken.

Can you tell us what method you used to move from Xenial to Bionic?

Despite the wording, in Ubuntu apt-get dist-upgrade (or the current apt full-upgrade ) is the correct command to update the system (as opposed to apt-get upgrade, which does not fully do so)

**oshunluvr** · Mar 04, 2020, 01:20 PM

Originally posted by pooky2483 View Post

So, unlike 16.04 where I had to open dolphin or kate as root to be able to edit a file, now I can open a file as normal but when saving, I have to enter the root password.
I'd say that's an improvement.

I agree when it come to Kate for sure. Much easier way to do things. LOTS of people complain about not being able to run Dolphin as root, but frankly IMO, if you're unable to manage things without dolphin you probably shouldn't be using dolphin as root. Supposedly the devs are working on a similar implementation for dolphin like kate. The old "root actions" service menu functions would be fine IMO. Honestly, I just go to the konsole when doing root "stuff".

**claydoh** · Mar 04, 2020, 01:22 PM

Originally posted by oshunluvr View Post

If you install xenial packages to a bionic install, you'll break things. I don't know why it didn't get cleaned up, but that's clearly why you're getting the majority of those messages.

Delete all xenial lines and try apt update again.

At this point, if the OP does so, there won't be any sources at all , unless there are lines with Bionic not shown.

**oshunluvr** · Mar 04, 2020, 01:24 PM

Originally posted by claydoh View Post

Is that the entire sources.list?
if so, then all your sources are still set to 16.04, not 18.04 (Bionic)

Which makes me ask, based on this

By dist upgrade, do you mean that you ran sudo apt-get dist-upgrade ? If so, then you have NOT upgraded to 18.04.

Either way, something looks broken.

Can you tell us what method you used to move from Xenial to Bionic?

Despite the wording, in Ubuntu apt-get dist-upgrade (or the current apt full-upgrade ) is the correct command to update the system (as opposed to apt-get upgrade, which does not fully do so)

I didn't catch that nuance. I assumed he or she was seeing both xenial and bionic repos thus the duplicate errors from apt.

**oshunluvr** · Mar 04, 2020, 01:25 PM

Originally posted by claydoh View Post

At this point, if the OP does so, there won't be any sources at all , unless there are lines with Bionic not shown.

Go back to the first post, it shows "Hits" on bionic

**claydoh** · Mar 04, 2020, 01:26 PM

Originally posted by oshunluvr View Post

Go back to the first post, it shows "Hits" on bionic

Ahah, I knew I missed something

**pooky2483** · Mar 04, 2020, 03:13 PM

Originally posted by claydoh View Post

IBy dist upgrade, do you mean that you ran sudo apt-get dist-upgrade ? If so, then you have NOT upgraded to 18.04.

Either way, something looks broken.

Can you tell us what method you used to move from Xenial to Bionic?

I ran this command in terminal

Code:

do-release-upgrade

From https://askubuntu.com/questions/1107...o-ubuntu-18-04

**jglen490** · Mar 04, 2020, 04:34 PM

Refer to this page. Look about halfway down at the do-release-upgrade discussion. There is a specific sequence that must be done, and in my opinion do-release -upgrade should be specifically called out with sudo.

It's entirely possible that this may be a big part of your "is it Xenial or is it Bionic" dilemma.

Announcement

Run as root

[SOLVED] Run as root

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment