Linux dpkg was interrupted

Dpkg Error “Dpkg Was Interrupted” and Solution

This is a small post about dpkg error. Dpkg is a tool used to manage package installation, removing, update of distributions like Debian, Ubuntu. Actually dpkg can be used distributions like Fedora, CentOS, RedHat but their default package manager is rpm.

Error

Here is the problem while install a package with apt-get or dpkg directly the operation is interrupted. After trying again to install a package we get an error like “dpkg was interrupted, you must manually run”

Dpkg Error

This error can be caused by different problems.

Reconfigure Dpkg

We need to repair dpkg package database in order to resume apt-get update operation. We can run dpkg to reconfigure the package database like below and correct the problem. We will provide —configure and -a option to the dpkg command like below. This command will regenerate the package database and fix errors. We also need the root privileges to change dpkg database which will be provided with sudo command like below.

Reconfigure Dpkg

The interrupted package installation with dpkg is completed with success.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] dpkg was interrupted, you must manually run.

[SOLVED] dpkg was interrupted, you must manually run.

Post by gicu » Sun Oct 30, 2016 10:21 pm

After checking for updates I have this error:

Re: dpkg was interrupted, you must manually run.

Post by richyrich » Sun Oct 30, 2016 10:27 pm

Re: dpkg was interrupted, you must manually run.

Post by gicu » Sun Oct 30, 2016 10:37 pm

Ou, yeah. I had to run this by mistake.
Didn’t noticed that klnagent is the Kaspersky package.

Is there any way to remove it?

Re: dpkg was interrupted, you must manually run.

Post by richyrich » Sun Oct 30, 2016 10:44 pm

Re: dpkg was interrupted, you must manually run.

Post by gicu » Sun Oct 30, 2016 10:47 pm

Re: dpkg was interrupted, you must manually run.

Post by richyrich » Sun Oct 30, 2016 10:54 pm

Re: dpkg was interrupted, you must manually run.

Post by gicu » Sun Oct 30, 2016 10:58 pm

Package is called
«kes4lwks_8.0.1-50_i386.deb»

(Version 8 (8.0.1) for Linux (deb) (Administration Agent))

Re: dpkg was interrupted, you must manually run.

Post by richyrich » Sun Oct 30, 2016 11:03 pm

Re: dpkg was interrupted, you must manually run.

Post by gicu » Mon Oct 31, 2016 7:52 am

I tried but same as I can’t install new software I can’t remove anything either.

Got message from ‘gdebi-gtk’:

Only one software management tool is allowed to run at a time.

Please close the other application e.g. ‘Update manager, ‘aptitude’ or ‘Synaptic’ first.

So this soft just ‘stuck’ my Mint.

And I don’t see this ‘apps’ in system monitor to kill it first.

When I want to manually delete it from /etc/init.d/klnagent
It says:

When I’m trying to run it: The Link «klnagent» is Broken. Move it to the Rubbish Bin?

And removed it through nautilus.
Done.

But problem still not solved.
Still got this:

Only one software management tool is allowed to run at a time.

Источник

Thread: dpkg was interrupted 18.04

Thread Tools

Display

dpkg was interrupted 18.04

I was installing GTX driver and then the power down so the laptop shutdown.
Then when i run sudo apt-get install <>
the error popped up, i ran sudo dpkg —configure -a as it suggested but
things stoped here:

Plase help me to fix this, i can not install or do anthing

Last edited by deadflowr; June 19th, 2018 at 06:57 AM . Reason: added code tags

Re: dpkg was interrupted 18.04

Looks like it completed building on an old kernel.
Latest kernel is:

from here we see what the next step in the process might be.

Re: dpkg was interrupted 18.04

hello thank you for your help
I try whis

Re: dpkg was interrupted 18.04

if it runs normal then great, if it still has problems post the output from that command.

Re: dpkg was interrupted 18.04

yep i did and i received the thing i posted above then it stopped there.

Re: dpkg was interrupted 18.04

somehow i managed to resolve the «dpkg was interupted»
but when i ran

Re: dpkg was interrupted 18.04

I used the ubuntu app Software & Update to recover the thing ( my initial problem )
then i used this as suggeted by Basing-om

things got back to normal

Thank you guys,
hope this helps

Re: dpkg was interrupted 18.04

You do good work
And thanks for providing your solution.

Re: dpkg was interrupted 18.04

Happy some ubunewbies like myself got the ‘sudo apt full-upgrade’ Error sorted with ‘sudo dpkg —configure -a’.

Didn’t work for my Thinkpad w. nvidia Quadro P4000 Mobile GPU running ubuntustudio 18.4.

The ‘sudo dpkg —configure -a‘ command hangs at *Building initial module for 4.15.0-24-lowlatency*

The entire log following the above command is:
con10t@the-beast:

$ sudo dpkg —configure -a
Processing triggers for initramfs-tools (0.130ubuntu3.1) .
update-initramfs: Generating /boot/initrd.img-4.15.0-24-lowlatency
Setting up nvidia-dkms-390 (390.67-0ubuntu0

gpu18.04.1) .
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia
DEBUG arsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG arsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG arsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
Removing old nvidia-390.67 DKMS files.

Status: This module version was INACTIVE for this kernel.
depmod.

DKMS: uninstall completed.

——————————
Deleting module version: 390.67
completely from the DKMS tree.
——————————
Done.
Loading new nvidia-390.67 DKMS files.
Building for 4.15.0-24-lowlatency
Building for architecture x86_64
Building initial module for 4.15.0-24-lowlatency

It freezes at this point.

I am running dual boot with windows 10 on my new ‘beast’, but stuck at this point. Any idea how to get ‘dpkg’ working?

‘apt list —upgradable’ gives the following list:

$ apt list —upgradable
Listing. Done
gir1.2-soup-2.4/bionic-updates,bionic-security 2.62.1-1ubuntu0.1 amd64 [upgradable from: 2.62.1-1]
libarchive-zip-perl/bionic-security,bionic-security 1.60-1ubuntu0.1 all [upgradable from: 1.60-1]
libexiv2-14/bionic-updates,bionic-security 0.25-3.1ubuntu0.18.04.1 amd64 [upgradable from: 0.25-3.1]
libnvidia-common-390/bionic,bionic 390.67-0ubuntu0

gpu18.04.1 all [upgradable from: 390.48-0ubuntu3]
libsdl2-2.0-0/bionic-updates 2.0.8+dfsg1-1ubuntu1.18.04.1 amd64 [upgradable from: 2.0.8+dfsg1-1ubuntu1]
libsoup-gnome2.4-1/bionic-updates,bionic-security 2.62.1-1ubuntu0.1 amd64 [upgradable from: 2.62.1-1]
libsoup2.4-1/bionic-updates,bionic-security 2.62.1-1ubuntu0.1 amd64 [upgradable from: 2.62.1-1]
libvulkan1/bionic 1.1.73+dfsg-1

gpu18.04.1 amd64 [upgradable from: 1.1.70+dfsg1-1]
libxnvctrl0/bionic 396.24-0ubuntu0

gpu18.04.1 amd64 [upgradable from: 390.42-0ubuntu1]
libzzip-0-13/bionic-updates,bionic-security 0.13.62-3.1ubuntu0.18.04.1 amd64 [upgradable from: 0.13.62-3.1]
nvidia-kernel-common-390/bionic 390.67-0ubuntu0

gpu18.04.1 amd64 [upgradable from: 390.48-0ubuntu3]
nvidia-settings/bionic 396.24-0ubuntu0

gpu18.04.1 amd64 [upgradable from: 390.42-0ubuntu1]

a conundrum this ubunewbie can’t fix without a bit of wizardry from the ether in here.

Источник

How to fix dpkg was interrupted, you must manually run sudo dpkg -configure-a

How to fix “dpkg was interrupted, you must manually run sudo dpkg –configure -a to correct the problem” error.

Whether you are a beginner or a pro, if you have been using Linux or Nginx for WordPress then it may be common to see the error when you try to install apt-get or using apt or doing just a Yum Update. And believe me, it can be very frustrating when it occurs as you are restricted to install or update your software packages on WordPress using Linux. Now, this error can occur for anyone and is not only restricted to some of you using Amazon EC2, AWS Lightsail, or your traditional LAMP or XAMPP.

Don’t worry, we have got you covered. Just run the following commands and tada!

sudo rm /var/lib/apt/lists/lock

sudo rm /var/cache/apt/archives/lock

cd /var/lib/dpkg/updates

sudo rm *

sudo apt-get update

If the above is helpful, please leave us your feedback in comments that keeps us motivated.

If the error prevails, feel free to email us or post a comment below for future issues.

Bonus

You can also check any processes running such as apt or apt-get. Kill those processes and then continue with your update or install.

Источник

подскажите с dpkg

Добрый день уважаемые, помогите разобраться. Система Ubuntu10.04.3 LTS, ставлю default-jdk, на настройке пакетов комп перестал реагировать что либо. Пришлось ребутать. После этого, любые попытки установить что-либо дают такой результат:

опять настройка пакетов и опять ребут

в смысле у тебя комп на этом подвисает?

Прям мгновенный зависон и ребут? Тогда это аппаратная проблема.

1) проверь оперативу и вообще тачка не чудит под нагрузкой? Только с жавой проблемы?

2) вообще, ты можешь удалить пакет через dpkg -r и поставить обратно. Но я бы залез внутрь и посмотрел что там выполняется в фазе конфигурирования и запустил это руками. Но, мне кажется, это не софтовый глюк.

Комп находится в облаке Амазон, самой простой micro instance. На самом деле уже jdk и не нужна, но ошибку надо исправить, пакеты то не установить из-за нее.

Скрипт, который тебе мешает, находится в /var/lib/dpkg/info/ .postinst. Помести туда что-нибудь вроде exit 0.

sudo env DEBCONF_DEBUG=’.*’ dpkg —configure —pending ничего интересного не покажет?

а своп у тебя там есть? Ну и Minoru подсказал что можно сделать.

сделал для openjdk вот на чем он падает:

sudo dpkg —configure -a Setting up openjdk-6-jre-headless (6b20-1.9.10-0ubuntu1

10.04.2) update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/java to provide /usr/bin/java (java) in auto mode. update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/keytool to provide /usr/bin/keytool (keytool) in auto mode. update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/pack200 to provide /usr/bin/pack200 (pack200) in auto mode. update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode. update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/rmiregistry to provide /usr/bin/rmiregistry (rmiregistry) in auto mode. update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/unpack200 to provide /usr/bin/unpack200 (unpack200) in auto mode. update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/orbd to provide /usr/bin/orbd (orbd) in auto mode. update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/servertool to provide /usr/bin/servertool (servertool) in auto mode. update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/tnameserv to provide /usr/bin/tnameserv (tnameserv) in auto mode. update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode.

и все, в ответ тишина.

sudo env DEBCONF_DEBUG=’.*’ dpkg —configure —pending Увы, точно такой же эффект, перестает отвечать.

Спасибо большое!! Очень помогли с советом. Оказалось все из-за openjdk-6-jre-headless.postinst.

решить окончательно проблему помогли ребята с форума амазона и bugs.launchpad.net :

Does anyone know how to recover from this issue temporarily? After requesting the install once, no matter what apt-get command I do, I get:
E: dpkg was interrupted, you must manually run ‘sudo dpkg —configure -a’ to correct the problem.
When I run that command, the hang occurs again and again. I cannot install or update anything else.

Don’t run ‘sudo dpkg —configure -a’ until the instance is started as a small.

On how to fix corrupted apt-get/dpkg:
1. Run: dpkg -l |grep -v -E «^ii»
This will list all packages that are either not in perfectly installed state; either incompletely installed, or that have config files remaining behind them after they have been uninstalled (or some other variant). You can tell them apart by value in first column. (rc = removed & conf-files; iU = install & unpacked). See listing header («dpkg -l | head» for detailed meanings).
2. Run: dpkg -P package_name [package_name2] [package_name3 . ]
This will purge those incomplete packages.
Personally, I have removed all listed packages (as they were all related to broken jre install), and dpkg was running without a problem afterwards.

Also, if you wish to remove all listed packages, first you can run this, to see the list of packages-to-be-removed:

echo `dpkg —list | tail -n +6 | grep -v -E «^ii» | cut -d» » -f3`

After you are 100% sure that you know what exactly is going to be removed (so you don’t get your system to even more corrupted state), then replace «echo» with «dpkg —purge».

Вот что помогло мне решить проблему и удалить пакет. Все из за нехватки оперативной памяти инстанса и какой то баг.

Источник