Error in apt-get upgrade

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Post Reply
mahavirvataliya
Level 1
Level 1
Posts: 2
Joined: Mon May 01, 2017 3:39 pm

Error in apt-get upgrade

Post by mahavirvataliya »

Dear forum members,

Could you please help me with this error:

Code: Select all

$ sudo apt-get upgrade 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up tor (0.2.7.6-1ubuntu1) ...
insserv: warning: script 'S99runlcactivator' missing LSB tags and overrides
insserv: warning: script 'runlcactivator' missing LSB tags and overrides
insserv: There is a loop between service plymouth and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service hwclock at depth 3
insserv: There is a loop between service runlcactivator and udev if started
insserv:  loop involving service udev at depth 1
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop at service plymouth if started
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop at service runlcactivator if started
insserv:  loop involving service networking at depth 6
insserv:  loop involving service mountdevsubfs at depth 3
insserv:  loop involving service mountkernfs at depth 1
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service runlcactivator and dns-clean if started
insserv:  loop involving service dns-clean at depth 1
insserv: Starting runlcactivator depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package tor (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 tor
E: Sub-process /usr/bin/dpkg returned an error code (1)
Thanks a lot for the support.
Last edited by killer de bug on Mon May 01, 2017 3:51 pm, edited 1 time in total.
Reason: politness added.

User avatar
EmpireITtech
Level 4
Level 4
Posts: 409
Joined: Fri Oct 12, 2012 8:45 am

Re: Error in apt-get upgrade

Post by EmpireITtech »

Strange - what repo's are you using? Anything custom? When you run

Code: Select all

sudo apt-get update
does it complete?
Linux: Mint 19 Tara Cinnamon 64-Bit

Box 1: Intel Core 2 Quad | 8gb RAM | 500gb WD 7200rpm | nVidia Geforce GTS250
Box 2: Intel Core i3-3240 | 4gb RAM | 1tb WD 7200rpm | AMD/ATI Radeon HD 4550

Pants: 32x30

User avatar
richyrich
Level 19
Level 19
Posts: 9063
Joined: Mon May 04, 2009 8:31 pm

Re: Error in apt-get upgrade

Post by richyrich »

dpkg: error processing package tor (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
tor

mahavirvataliya
Level 1
Level 1
Posts: 2
Joined: Mon May 01, 2017 3:39 pm

Re: Error in apt-get upgrade

Post by mahavirvataliya »

richyrich wrote:
dpkg: error processing package tor (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
tor

before installation of tor also this problem is occurred
and my update output is

sudo apt-get update
Hit:1 http://download.mono-project.com/repo/debian wheezy InRelease
Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:3 http://ppa.launchpad.net/alexlarsson/flatpak/ubuntu xenial InRelease
Hit:4 http://dl.google.com/linux/chrome/deb stable Release
Hit:5 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:7 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu xenial InRelease
Hit:8 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:9 https://packages.microsoft.com/repos/vscode stable InRelease
Hit:10 http://ppa.launchpad.net/plushuang-tw/u ... ble/ubuntu xenial InRelease
Hit:11 http://archive.canonical.com/ubuntu xenial InRelease
Hit:12 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:13 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu xenial InRelease
Hit:14 http://ppa.launchpad.net/ubuntu-desktop ... ake/ubuntu xenial InRelease
Hit:15 http://ppa.launchpad.net/webupd8team/java/ubuntu xenial InRelease
Ign:16 http://packages.linuxmint.com serena InRelease
Hit:17 http://packages.linuxmint.com serena Release
Hit:19 http://security.ubuntu.com/ubuntu xenial-security InRelease
Reading package lists... Done

User avatar
richyrich
Level 19
Level 19
Posts: 9063
Joined: Mon May 04, 2009 8:31 pm

Re: Error in apt-get upgrade

Post by richyrich »

Using Debian repositories on an Ubuntu-based Mint system will definitely cause problems ! :shock:

Post Reply

Return to “Newbie Questions”