- Forum
- The Ubuntu Forum Community
- Ubuntu Official Flavours Support
- Installation & Upgrades
- How to resolve �dpkg: error processing package systemd�
-
How to resolve �dpkg: error processing package systemd�
After upgrade from Ubuntu 16 to Ubuntu 18
When I want to use this command:I see this output:Code:
dpkg: error processing package systemd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1)
And
Code:
dpkg --configure -a
Output is:
Code:
Errors were encountered while processing: python3-numpy libc-bin systemd python3-gdbm:amd64 python3-cairo:amd64 python3-tk:amd64 python3-matplotlib dh-python libglib2.0-bin locales libpam-systemd:amd64
Code:
python Python 2.7.12 (default, Dec 4 2017, 14:50:18)
And
Code:
python3 Python 3.6.5 (default, Apr 1 2018, 05:46:30)
And install any package for example: apt install systemd Output is:
Code:
python3-cairo : Depends: python3 (>= 3.6~) but 3.5.1-3 is to be installed python3-gdbm : Depends: python3 (>= 3.6.4-1~) but 3.5.1-3 is to be installed python3-matplotlib : Depends: python3 (>= 3.6~) but 3.5.1-3 is to be installed python3-numpy : Depends: python3 (>= 3.6~) but 3.5.1-3 is to be installed python3-tk : Depends: python3 (>= 3.6.4-1~) but 3.5.1-3 is to be installed
Any suggestions?
-
Re: How to resolve �dpkg: error processing package systemd�
python3-cairo : Depends: python3 (>= 3.6~) but 3.5.1-3 is to be installed
Somehow your system is not up-to-date, package listings wise.
How did you update from 16.04 to 18.04?What does
output?
-
Re: How to resolve �dpkg: error processing package systemd�
my way was:
sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
sudo apt install update-manager-core
sudo do-release-upgrade
sudo do-release-upgrade -dAnd:
root@win:~# sudo apt update
Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB]
Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1021 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic/main Translation-en [517 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8561 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic/universe Translation-en [4941 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 kB]
Fetched 15.4 MB in 1min 14s (206 kB/s)
Reading package lists… Done
Building dependency tree
Reading state information… Done
1982 packages can be upgraded. Run ‘apt list —upgradable’ to see them.
-
Re: How to resolve �dpkg: error processing package systemd�
1982 packages can be upgraded. Run ‘apt list —upgradable’ to see them.
Then there is your answer.
For some reason or another the upgrade must not have ran as it should have.No reason for that to result in any more than a couple dozen to couple hundred new updates at most.
But 1900+ means it wasn’t a proper upgrade or something wrong happened during the upgrade.So what does
Code:
sudo apt full-upgrade
do/show?
(This would be more for a curiosity stand point, and feel free to select n to abort.
I’m more interested in seeing what the output of install.upgrade/remove will be)
-
Re: How to resolve �dpkg: error processing package systemd�
this command output is:
Code:
root@win:~# sudo apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: dh-python : Depends: python3-distutils but it is not installed indicator-session : Depends: systemd-services but it is not installable libc-bin : Depends: libc6 (< 2.24) but 2.27-3ubuntu1 is installed libc-dev-bin : Depends: libc6 (< 2.24) but 2.27-3ubuntu1 is installed libc6-dbg : Depends: libc6 (= 2.23-0ubuntu10) but 2.27-3ubuntu1 is installed libc6-dev : Depends: libc6 (= 2.23-0ubuntu10) but 2.27-3ubuntu1 is installed libglib2.0-bin : Depends: libglib2.0-0 (= 2.56.1-2ubuntu1) but 2.48.2-0ubuntu1 is installed libglib2.0-dev : Depends: libglib2.0-bin (= 2.48.2-0ubuntu1) but 2.56.1-2ubuntu1 is installed locales : Depends: libc-bin (> 2.27) but 2.23-0ubuntu10 is installed python3 : PreDepends: python3-minimal (= 3.5.1-3) but 3.6.5-3 is installed Depends: libpython3-stdlib (= 3.5.1-3) but 3.6.5-3 is installed python3-cairo : Depends: python3 (>= 3.6~) but 3.5.1-3 is installed python3-gdbm : Depends: python3 (>= 3.6.4-1~) but 3.5.1-3 is installed python3-matplotlib : Depends: python3 (>= 3.6~) but 3.5.1-3 is installed python3-numpy : Depends: python3 (>= 3.6~) but 3.5.1-3 is installed python3-tk : Depends: python3 (>= 3.6.4-1~) but 3.5.1-3 is installed udev : Depends: libudev1 (= 229-4ubuntu21.2) but 237-3ubuntu8 is installed E: Unmet dependencies. Try using -f.and additional results are in my first post
-
Re: How to resolve �dpkg: error processing package systemd�
-
Re: How to resolve �dpkg: error processing package systemd�
Well let’s see how far along the upgrade actually got
what doCode:
uname -r lsb_release -a
show.
Also release upgrade have logs in /var/log/dist-upgrade.
Look at what main.log shows at the end.Code:
tail -n 100 /var/log/dist-upgrade/main.log
you might also check what the ends of the apt.log, history.log, and term.log files show.
You can use the same tail command and simply change out the file name.
-
Re: How to resolve �dpkg: error processing package systemd�
Code:
root@win:/var/log/dist-upgrade# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic
And:
Code:
root@win:/var/log/dist-upgrade# tail -l apt-term.log Executing: /lib/systemd/systemd-sysv-install enable ondemand [/usr/lib/tmpfiles.d/tmp.conf:15] Failed to replace specifiers: /tmp/systemd-private-%b-* [/usr/lib/tmpfiles.d/tmp.conf:16] Failed to replace specifiers: /tmp/systemd-private-%b-*/tmp [/usr/lib/tmpfiles.d/tmp.conf:17] Failed to replace specifiers: /var/tmp/systemd-private-%b-* [/usr/lib/tmpfiles.d/tmp.conf:18] Failed to replace specifiers: /var/tmp/systemd-private-%b-*/tmp dpkg: error processing package systemd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: systemd Log ended: 2018-04-20 20:53:47
And:
Code:
root@win:/var/log/dist-upgrade# tail -100 apt.log Investigating (0) php-bz2 [ amd64 ] < none -> 1:7.2+60ubuntu1 > ( universe/php ) Broken php-bz2:amd64 Depends on php7.2-bz2 [ amd64 ] < none -> 7.2.3-1ubuntu1 > ( universe/php ) Considering php7.2-bz2:amd64 1 as a solution to php-bz2:amd64 0 MarkKeep php-bz2 [ amd64 ] < none -> 1:7.2+60ubuntu1 > ( universe/php ) FU=0 Holding Back php-bz2:amd64 rather than change php7.2-bz2:amd64 Investigating (0) libcurl4-openssl-dev [ amd64 ] < 7.47.0-1ubuntu2.7 -> 7.58.0-2ubuntu3 > ( libdevel ) Broken libcurl4-openssl-dev:amd64 Depends on libcurl4 [ amd64 ] < none -> 7.58.0-2ubuntu3 > ( libs ) (= 7.58.0-2ubuntu3) Considering libcurl4:amd64 -1 as a solution to libcurl4-openssl-dev:amd64 0 MarkKeep libcurl4-openssl-dev [ amd64 ] < 7.47.0-1ubuntu2.7 -> 7.58.0-2ubuntu3 > ( libdevel ) FU=0 Removing libcurl4-openssl-dev:amd64 rather than change libcurl4:amd64 MarkDelete libcurl4-openssl-dev [ amd64 ] < 7.47.0-1ubuntu2.7 -> 7.58.0-2ubuntu3 > ( libdevel ) FU=0 Investigating (0) libqalculate6-data [ amd64 ] < none -> 0.9.10-1 > ( universe/libs ) Broken libqalculate6-data:amd64 Breaks on libqalculate5-data [ amd64 ] < 0.9.7-9.1 > ( libs ) Considering libqalculate5-data:amd64 -2 as a solution to libqalculate6-data:amd64 0 Added libqalculate5-data:amd64 to the remove list Fixing libqalculate6-data:amd64 via remove of libqalculate5-data:amd64 MarkDelete libqalculate5-data [ amd64 ] < 0.9.7-9.1 > ( libs ) FU=0 Investigating (0) cmake [ amd64 ] < 3.5.1-1ubuntu3 -> 3.10.2-1ubuntu1 > ( devel ) Broken cmake:amd64 Depends on libcurl4 [ amd64 ] < none -> 7.58.0-2ubuntu3 > ( libs ) (>= 7.16.2) Considering libcurl4:amd64 -1 as a solution to cmake:amd64 0 MarkKeep cmake [ amd64 ] < 3.5.1-1ubuntu3 -> 3.10.2-1ubuntu1 > ( devel ) FU=0 Removing cmake:amd64 rather than change libcurl4:amd64 MarkDelete cmake [ amd64 ] < 3.5.1-1ubuntu3 -> 3.10.2-1ubuntu1 > ( devel ) FU=0 Investigating (0) libmagickwand-6.q16-2 [ amd64 ] < 8:6.8.9.9-7ubuntu5.9 > ( libs ) Broken libmagickwand-6.q16-2:amd64 Depends on libmagickcore-6.q16-2 [ amd64 ] < 8:6.8.9.9-7ubuntu5.9 > ( libs ) (>= 8:6.8.9.9) Considering libmagickcore-6.q16-2:amd64 0 as a solution to libmagickwand-6.q16-2:amd64 0 Removing libmagickwand-6.q16-2:amd64 rather than change libmagickcore-6.q16-2:amd64 MarkDelete libmagickwand-6.q16-2 [ amd64 ] < 8:6.8.9.9-7ubuntu5.9 > ( libs ) FU=0 Investigating (0) pollinate [ amd64 ] < 4.25-0ubuntu1~16.04.1 -> 4.31-0ubuntu1 > ( admin ) Broken pollinate:amd64 Depends on curl [ amd64 ] < 7.47.0-1ubuntu2.7 -> 7.58.0-2ubuntu3 > ( web ) Considering curl:amd64 12 as a solution to pollinate:amd64 0 MarkKeep pollinate [ amd64 ] < 4.25-0ubuntu1~16.04.1 -> 4.31-0ubuntu1 > ( admin ) FU=0 Removing pollinate:amd64 rather than change curl:amd64 MarkDelete pollinate [ amd64 ] < 4.25-0ubuntu1~16.04.1 -> 4.31-0ubuntu1 > ( admin ) FU=0 Investigating (0) libwebkitgtk-1.0-0 [ amd64 ] < 2.4.11-0ubuntu0.1 -> 2.4.11-3ubuntu3 > ( universe/libs ) Broken libwebkitgtk-1.0-0:amd64 Breaks on libwebkitgtk-1.0-common [ amd64 ] < 2.4.11-0ubuntu0.1 > ( libs ) (< 2.4.11-2~) Considering libwebkitgtk-1.0-common:amd64 -3 as a solution to libwebkitgtk-1.0-0:amd64 0 Added libwebkitgtk-1.0-common:amd64 to the remove list Fixing libwebkitgtk-1.0-0:amd64 via remove of libwebkitgtk-1.0-common:amd64 MarkDelete libwebkitgtk-1.0-common [ amd64 ] < 2.4.11-0ubuntu0.1 > ( libs ) FU=0 Investigating (0) perl-modules-5.22 [ amd64 ] < 5.22.1-9ubuntu0.3 > ( perl ) Broken perl-modules-5.22:amd64 Conflicts on perl-modules [ amd64 ] < none -> > ( none ) Considering perl-modules-5.26:amd64 115 as a solution to perl-modules-5.22:amd64 -1 Removing perl-modules-5.22:amd64 rather than change perl-modules:amd64 MarkDelete perl-modules-5.22 [ amd64 ] < 5.22.1-9ubuntu0.3 > ( perl ) FU=0 Investigating (0) linuxbrew-wrapper [ amd64 ] < 20150804-3 -> 20170516-2 > ( universe/utils ) Broken linuxbrew-wrapper:amd64 Depends on curl [ amd64 ] < 7.47.0-1ubuntu2.7 -> 7.58.0-2ubuntu3 > ( web ) Considering curl:amd64 12 as a solution to linuxbrew-wrapper:amd64 -1 MarkKeep linuxbrew-wrapper [ amd64 ] < 20150804-3 -> 20170516-2 > ( universe/utils ) FU=0 Removing linuxbrew-wrapper:amd64 rather than change curl:amd64 MarkDelete linuxbrew-wrapper [ amd64 ] < 20150804-3 -> 20170516-2 > ( universe/utils ) FU=0 Investigating (0) libvlccore8 [ amd64 ] < 2.2.2-5ubuntu0.16.04.4 > ( libs ) Broken libvlccore8:amd64 Depends on vlc-data [ amd64 ] < 2.2.2-5ubuntu0.16.04.4 -> 3.0.1-3build1 > ( universe/graphics ) (= 2.2.2-5ubuntu0.16.04.4) Considering vlc-data:amd64 2 as a solution to libvlccore8:amd64 -1 Removing libvlccore8:amd64 rather than change vlc-data:amd64 MarkDelete libvlccore8 [ amd64 ] < 2.2.2-5ubuntu0.16.04.4 > ( libs ) FU=0 Investigating (0) libperl5.22 [ amd64 ] < 5.22.1-9ubuntu0.3 > ( libs ) Broken libperl5.22:amd64 Depends on perl-modules-5.22 [ amd64 ] < 5.22.1-9ubuntu0.3 > ( perl ) (>= 5.22.1-9ubuntu0.3) Considering perl-modules-5.22:amd64 -1 as a solution to libperl5.22:amd64 -2 Removing libperl5.22:amd64 rather than change perl-modules-5.22:amd64 MarkDelete libperl5.22 [ amd64 ] < 5.22.1-9ubuntu0.3 > ( libs ) FU=0 Investigating (0) libmagickcore-6.q16-2-extra [ amd64 ] < 8:6.8.9.9-7ubuntu5.9 > ( libs ) Broken libmagickcore-6.q16-2-extra:amd64 Depends on libmagickcore-6.q16-2 [ amd64 ] < 8:6.8.9.9-7ubuntu5.9 > ( libs ) (>= 8:6.8.9.9) Considering libmagickcore-6.q16-2:amd64 0 as a solution to libmagickcore-6.q16-2-extra:amd64 -2 Removing libmagickcore-6.q16-2-extra:amd64 rather than change libmagickcore-6.q16-2:amd64 MarkDelete libmagickcore-6.q16-2-extra [ amd64 ] < 8:6.8.9.9-7ubuntu5.9 > ( libs ) FU=0 Investigating (0) pulseaudio-module-x11 [ amd64 ] < 1:8.0-0ubuntu3.8 > ( sound ) Broken pulseaudio-module-x11:amd64 Depends on libpulse0 [ amd64 ] < 1:8.0-0ubuntu3.8 -> 1:11.1-1ubuntu7 > ( libs ) (= 1:8.0-0ubuntu3.8) Considering libpulse0:amd64 137 as a solution to pulseaudio-module-x11:amd64 -2 Removing pulseaudio-module-x11:amd64 rather than change libpulse0:amd64 MarkDelete pulseaudio-module-x11 [ amd64 ] < 1:8.0-0ubuntu3.8 > ( sound ) FU=0 Investigating (0) xserver-xorg-input-vmmouse [ amd64 ] < 1:13.1.0-1ubuntu2 > ( x11 ) Broken xserver-xorg-input-vmmouse:amd64 Depends on xorg-input-abi-22 [ amd64 ] < none -> > ( none ) Considering xserver-xorg-core:amd64 29 as a solution to xserver-xorg-input-vmmouse:amd64 -2 Removing xserver-xorg-input-vmmouse:amd64 rather than change xorg-input-abi-22:amd64 MarkDelete xserver-xorg-input-vmmouse [ amd64 ] < 1:13.1.0-1ubuntu2 > ( x11 ) FU=0 Investigating (0) libnss3-nssdb [ amd64 ] < 2:3.28.4-0ubuntu0.16.04.3 > ( admin ) Broken libnss3-nssdb:amd64 Depends on libnss3 [ amd64 ] < 2:3.28.4-0ubuntu0.16.04.3 -> 2:3.35-2ubuntu2 > ( libs ) (= 2:3.28.4-0ubuntu0.16.04.3) Considering libnss3:amd64 43 as a solution to libnss3-nssdb:amd64 -2 Removing libnss3-nssdb:amd64 rather than change libnss3:amd64 MarkDelete libnss3-nssdb [ amd64 ] < 2:3.28.4-0ubuntu0.16.04.3 > ( admin ) FU=0 Investigating (0) libmagick++-6.q16-5v5 [ amd64 ] < 8:6.8.9.9-7ubuntu5.9 > ( libs ) Broken libmagick++-6.q16-5v5:amd64 Depends on libmagickcore-6.q16-2 [ amd64 ] < 8:6.8.9.9-7ubuntu5.9 > ( libs ) (>= 8:6.8.9.9) Considering libmagickcore-6.q16-2:amd64 0 as a solution to libmagick++-6.q16-5v5:amd64 -2 Removing libmagick++-6.q16-5v5:amd64 rather than change libmagickcore-6.q16-2:amd64 MarkDelete libmagick++-6.q16-5v5 [ amd64 ] < 8:6.8.9.9-7ubuntu5.9 > ( libs ) FU=0 Investigating (0) libmetacity-private3a [ amd64 ] < 1:3.18.7-0ubuntu0.3 > ( libs ) Broken libmetacity-private3a:amd64 Depends on metacity-common [ amd64 ] < 1:3.18.7-0ubuntu0.3 -> 1:3.28.0-1 > ( universe/misc ) (= 1:3.18.7-0ubuntu0.3) Considering metacity-common:amd64 1 as a solution to libmetacity-private3a:amd64 -2 Removing libmetacity-private3a:amd64 rather than change metacity-common:amd64 MarkDelete libmetacity-private3a [ amd64 ] < 1:3.18.7-0ubuntu0.3 > ( libs ) FU=0 Investigating (0) libqalculate5v5 [ amd64 ] < 0.9.7-9.1 > ( libs ) Broken libqalculate5v5:amd64 Depends on libqalculate5-data [ amd64 ] < 0.9.7-9.1 > ( libs ) Considering libqalculate5-data:amd64 -2 as a solution to libqalculate5v5:amd64 -2 Removing libqalculate5v5:amd64 rather than change libqalculate5-data:amd64 MarkDelete libqalculate5v5 [ amd64 ] < 0.9.7-9.1 > ( libs ) FU=0 Done dmesg: read kernel buffer failed: Function not implemented pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method.
And:
Code:
root@win:/var/log/dist-upgrade# tail -l main.log 2018-04-20 20:53:46,893 ERROR got an error from dpkg for pkg: 'systemd': 'subprocess installed post-installation script returned error exit status 1' 2018-04-20 20:53:46,894 DEBUG running apport_pkgfailure() systemd: subprocess installed post-installation script returned error exit status 1 2018-04-20 20:53:50,130 ERROR Exception during pm.DoInstall() Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-ikiurxn3/DistUpgrade/DistUpgradeView.py", line 218, in run res = pm.do_install(self.writefd) SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) 2018-04-20 20:53:50,197 ERROR SystemError from cache.commit(): installArchives() failed 2018-04-20 20:53:50,198 ERROR found exception: 'E:Sub-process /usr/bin/dpkg returned an error code (1)' 2018-04-20 20:54:20,728 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
-
Re: How to resolve �dpkg: error processing package systemd�
This isn’t by chance related to Windows Subsystem for Linux?
Seems the systemd error is common for that.
-
Re: How to resolve �dpkg: error processing package systemd�
yes, this is WSL
How can I resolve that?
Bookmarks
Bookmarks

Posting Permissions
I have recently upgraded to ubuntu 18.04 from ubuntu 14.04(via 16.04).
This is the error I see whenever I run apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libcloog-isl4 libcolord1 libelfg0 libisl10 libisl15 libmpfr4 libsox2 python-xapian python3-pycurl
Use 'apt autoremove' to remove them.
The following packages have been kept back:
amd64-microcode curl findutils initramfs-tools initramfs-tools-bin libcurl3 libsane-common libunwind8 mailutils mailutils-common openssh-client openssh-server openssh-sftp-server plymouth plymouth-theme-ubuntu-text python-pip python-pip-whl ssh
0 upgraded, 0 newly installed, 0 to remove and 18 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] y
Setting up systemd-shim (6-2bzr1) ...
dpkg-maintscript-helper: error: old-conffile **'debian/systemd-shim/etc/dbus-1/system.d/org.freedesktop.systemd1.conf'** is not an absolute path
dpkg: error processing package systemd-shim (--configure):
installed systemd-shim package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
systemd-shim
E: Sub-process /usr/bin/dpkg returned an error code (1)
The issue seemed close to this one and few others
But the fixes don’t work. I think it mainly because of this
dpkg-maintscript-helper: error: old-conffile ‘debian/systemd-shim/etc/dbus-1/system.d/org.freedesktop.systemd1.conf’ is not an absolute path
asked Oct 5, 2018 at 15:45
3
My solution was :
rm /var/lib/dpkg/info/$nomdupaquet* -f
Afterwards I was able to do:
apt install -f
apt upgrade
Sanpas
1,1709 silver badges29 bronze badges
answered Jan 29, 2019 at 9:38
sacsac
551 silver badge7 bronze badges
After mistakenly downloading pop-desktop again, udev and systemd have dependency errors that make me unable to use apt. When I run sudo apt upgrade, this error shows up:
user@computer:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
libpam-systemd : Depends: systemd (= 249.11-0ubuntu3.1)
systemd-sysv : Depends: systemd (= 249.11-0ubuntu3.1)
udev : Breaks: systemd (< 249.11-0ubuntu3.1)
Breaks: systemd:i386 (< 249.11-0ubuntu3.1)
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
When I try sudo apt —fix-broken install:
user@computer:~$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
libpam-systemd libudev1 libudev1:i386 systemd-sysv udev
The following packages will be DOWNGRADED:
libpam-systemd libudev1 libudev1:i386 systemd-sysv udev
0 upgraded, 0 newly installed, 5 downgraded, 0 to remove and 63 not upgraded.
3 not fully installed or removed.
Need to get 0 B/2,708 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
dpkg: dependency problems prevent configuration of systemd:
udev (249.11-0ubuntu3.1) breaks systemd (<< 249.11-0ubuntu3.1) and is installed.
Version of systemd to be configured is 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af.
dpkg: error processing package systemd (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a
previous failure.
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)
After doing that command, I went to multiple sources and could not find a solution to fix my situation.
I tried sudo dpkg —configure -a and it came back with this:
user@computer:~$ sudo dpkg --configure -a
dpkg: dependency problems prevent configuration of systemd:
udev (249.11-0ubuntu3.1) breaks systemd (<< 249.11-0ubuntu3.1) and is installed.
Version of systemd to be configured is 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af.
dpkg: error processing package systemd (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of systemd-timesyncd:
systemd-timesyncd depends on systemd (= 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af); however:
Package systemd is not configured yet.
dpkg: error processing package systemd-timesyncd (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libnss-systemd:amd64:
libnss-systemd:amd64 depends on systemd (= 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af); however:
Package systemd is not configured yet.
dpkg: error processing package libnss-systemd:amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
systemd
systemd-timesyncd
libnss-systemd:amd64
I tried sudo apt -f install and sudo apt —fix-broken install :
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
libpam-systemd libudev1 libudev1:i386 systemd-sysv udev
The following packages will be DOWNGRADED:
libpam-systemd libudev1 libudev1:i386 systemd-sysv udev
0 upgraded, 0 newly installed, 5 downgraded, 0 to remove and 63 not upgraded.
3 not fully installed or removed.
Need to get 0 B/2,708 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
dpkg: dependency problems prevent configuration of systemd:
udev (249.11-0ubuntu3.1) breaks systemd (<< 249.11-0ubuntu3.1) and is installed.
Version of systemd to be configured is 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af.
dpkg: error processing package systemd (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a
previous failure.
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)
I also tried Synaptic:
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
dpkg: dependency problems prevent configuration of systemd:
udev (249.11-0ubuntu3.1) breaks systemd (<< 249.11-0ubuntu3.1) and is installed.
Version of systemd to be configured is 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af.
dpkg: error processing package systemd (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of systemd-timesyncd:
systemd-timesyncd depends on systemd (= 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af); however:
Package systemd is not configured yet.
dpkg: error processing package systemd-timesyncd (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libnss-systemd:amd64:
libnss-systemd:amd64 depends on systemd (= 249.11-0ubuntu3pop0~1650312774~22.04~cecf6af); however:
Package systemd is not configured yet.
dpkg: error processing package libnss-systemd:amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
systemd
systemd-timesyncd
libnss-systemd:amd64
Is there any way to fix this udev and systems problem? If this problem has been solved, can you send the link where it has been resolved? Just to let you know, I am using Pop!_OS 22.04 LTS.
- Печать
Страницы: [1] 2 Все Вниз
Тема: bag обновления 204-5ubuntu20.18 (systemd-services libpam-systemd:amd64) (Прочитано 1798 раз)
0 Пользователей и 1 Гость просматривают эту тему.

qazawaq
Доброго времени !
Собственно вопрос:пришло обновление,после чего проблемы с зависимостями появились
Следствием чего теперь не отключается ноут 
Как это починить ? Или надеяться на починку после очередного обновления ?
В сети достаточно много вопросов на эту тему , в том числе bag на launchpad , хотя не уверен что проблема там аналогичная описана
apt-get -f install ничего не дает
ОС Ubuntu 14.04 c последними обновами
« Последнее редактирование: 14 Февраля 2016, 19:03:19 от qazawaq »

orionit
qazawaq,
А
sudo dpkg --configure -a
Всем добра как у бобра, а если вы и без добра добры, значит вы в душе бобры.

qazawaq
qazawaq,
Аsudo dpkg --configure -a
подобное пробовал , но безрезультатно
пробовал и с командами aptitude что нибудь сделать и dselect , но проблема осталась

orionit
qazawaq,
А
sudo apt-get --fix-broken install
Всем добра как у бобра, а если вы и без добра добры, значит вы в душе бобры.

qazawaq
qazawaq,
Аsudo apt-get --fix-broken install

ARTGALGANO
попробуй переименовать udev.postinst
sudo mv /var/lib/dpkg/info/udev.postinst{,.bak}если не сработает, верни обратно

orionit
qazawaq,
sudo rm /var/lib/apt/lists/* -vfпотом
sudo apt-get updateи теперь
sudo apt-get install -f
Всем добра как у бобра, а если вы и без добра добры, значит вы в душе бобры.

qazawaq
qazawaq,
sudo rm /var/lib/apt/lists/* -vfпотомsudo apt-get updateи теперьsudo apt-get install -f
пришло обновление , но проблема осталась
Пользователь решил продолжить мысль 14 Февраля 2016, 20:06:35:
попробуй переименовать udev.postinst
sudo mv /var/lib/dpkg/info/udev.postinst{,.bak}если не сработает, верни обратно
переименовал , все то же , система отчет выдала на launchpad
« Последнее редактирование: 14 Февраля 2016, 20:06:35 от qazawaq »

ARTGALGANO
уже остались тока
libpam-systemd:amd64
network-manager
sudo mv /var/lib/dpkg/info/libpam-systemd:amd64.postinst{,.bak} каталог /etc/rc0.d есть?
sudo mv /var/lib/dpkg/info/network-manager.postinst{,.bak}
sudo dpkg-reconfigure -a
« Последнее редактирование: 14 Февраля 2016, 20:28:24 от ARTGALGANO »

qazawaq
уже остались тока
libpam-systemd:amd64
network-managersudo mv /var/lib/dpkg/info/libpam-systemd:amd64.postinst{,.bak}каталог /etc/rc0.d есть?
sudo mv /var/lib/dpkg/info/network-manager.postinst{,.bak}
sudo dpkg-reconfigure -a
udev.postinst вернул обратное именование
libpam-systemd:amd64.postinst и network-manager.postinst не трогал пока
ругается на католог , что там должно быть , его создать ?
libpam-systemd:amd64.postinst и network-manager.postinst переименовал , каталог не создавал , проблемы нет вроде
обратно переименовать ? И немножко инфо , в чем проблема была ?

ARTGALGANO
обратно подожди пока
sudo apt-get install -f проходит без ошибок?

qazawaq
обратно подожди пока
sudo apt-get install -fпроходит без ошибок?
да , без ошибок , но на отсутсвие каталога ругается
и перезагрузка/выключение ноута не идет , выкидывает в логаут или несканчаемая заставка идет
alang
qazawaq, читал я, читал твою тему… Вывод как у Райкина.
Объясни, на кой черт ты связался с systemd на 14.04?

ARTGALGANO
почему нет /etc/rc0.d ?
там д.б линк на /init.d/halt
sudo init 0
systemctl poweroff
« Последнее редактирование: 14 Февраля 2016, 21:19:49 от ARTGALGANO »

qazawaq
qazawaq, читал я, читал твою тему… Вывод как у Райкина.
Объясни, на кой черт ты связался с systemd на 14.04?
не припомню чтобы что то трогал глобальное в системе , в том числе systemd , обновы из системы по дефолту . Хотя руки не фонтан , что лучше/должно быть на 14.04 вместо systemd ?
Пользователь решил продолжить мысль 14 Февраля 2016, 22:03:55:
почему нет /etc/rc0.d ?
там д.б линк на /init.d/haltsudo init 0
systemctl poweroff
простая ссылка на /init.d/halt ?
sudo init 0 — виснет на заставке выключения
systemctl poweroff — не знает таких
« Последнее редактирование: 14 Февраля 2016, 22:03:55 от qazawaq »
- Печать
Страницы: [1] 2 Все Вверх
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
coloradoauthor
<SOLVED> Can’t update anything
Brand-new Mint user here. I fired up my new Mintbox, got my mouse and printer working, then tried to do an update using the update manager. All I got was the following error:
Code: Select all
An error occurred
E: util-linux: subprocess installed post-installation script returned error exit status 1
When I click Details I see this:
Code: Select all
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up util-linux (2.27.1-6ubuntu3.3) ...
insserv: warning: script 'lprng' missing LSB tags and overrides
insserv: warning: script 'cupsys' missing LSB tags and overrides
insserv: warning: script 'lpd' missing LSB tags and overrides
insserv: There is a loop between service watchdog and lprng if stopped
insserv: loop involving service lprng at depth 2
insserv: loop involving service watchdog at depth 1
insserv: Stopping lprng depends on watchdog and therefore on system facility `$all' which can not be true!
insserv: Stopping cupsys depends on watchdog and therefore on system facility `$all' which can not be true!
insserv: Stopping lpd depends on watchdog 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 util-linux (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
util-linux
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
<...all of the above messages were repeated again...>
dpkg: dependency problems prevent processing triggers for systemd:
systemd depends on util-linux (>= 2.27.1); however:
Package util-linux is not configured yet.
dpkg: error processing package systemd (--configure):
dependency problems - leaving triggers unprocessed
Errors were encountered while processing:
util-linux
systemd
Here are my system details:
Code: Select all
$ inxi -F
System: Host: mintbox Kernel: 4.4.6-generic.fitlet x86_64 (64 bit)
Desktop: Cinnamon 3.0.7 Distro: Linux Mint 18 Sarah
Machine: Mobo: CompuLab model: fitlet v: 1.0
Bios: American Megatrends v: SBCFLTR_0.08.01 date: 06/23/2016
CPU: Quad core AMD A10 Micro-6700T APU+AMD Radeon R6 Graphics (-MCP-) cache: 8192 KB
clock speeds: max: 1200 MHz 1: 1200 MHz 2: 1000 MHz 3: 1000 MHz
4: 1000 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Mullins [Radeon R6 Graphics]
Display Server: X.Org 1.18.3 drivers: ati,radeon (unloaded: fbdev,vesa)
Resolution: 1920x1080@60.00hz
GLX Renderer: Gallium 0.4 on AMD MULLINS (DRM 2.43.0, LLVM 3.8.0)
GLX Version: 3.0 Mesa 11.2.0
Audio: Card-1 Advanced Micro Devices [AMD] FCH Azalia Controller
driver: snd_hda_intel
Card-2 Advanced Micro Devices [AMD/ATI] Kabini HDMI/DP Audio
driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.4.6-generic.fitlet
Network: Card-1: Intel Wireless 7260 driver: iwlwifi
IF: wlp1s0 state: up mac: 00:16:6f:e7:52:e8
Card-2: Intel I211 Gigabit Network Connection driver: igb
IF: enp2s0 state: down mac: 00:01:c0:1e:bb:56
Card-3: Intel I211 Gigabit Network Connection driver: igb
IF: enp3s0 state: up speed: 1000 Mbps duplex: full
mac: 00:01:c0:1e:bc:47
Drives: HDD Total Size: 128.0GB (14.7% used)
ID-1: /dev/sda model: ADATA_SP310 size: 128.0GB
Partition: ID-1: / size: 107G used: 6.9G (7%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 12.03GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 50.6C mobo: N/A gpu: 50.0
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 194 Uptime: 1:01 Memory: 1043.9/7659.1MB
Client: Shell (bash) inxi: 2.2.35
Rebooting didn’t help. I tried installing just one package (the Mint artwork…it seems to me like that should be one without many dependencies), and that failed in the same way.
It looks to me like I must have done something wrong when I installed the MFC-790CW printer driver using the Brother Printer Installer. I did have to try the installation a few times before I found settings that worked, but the printer works beautifully now. Sooo, what do I do? I’d like to be able to update my system, but I’d also like to learn what mistake I made so I don’t repeat it. Is there a way to temporarily kill off the printer services to allow the updates to proceed? Should I try uninstalling the printer? Something else?
One final note: I’m a Linux noob, but I was fluent with HP-UX once upon a time (long ago), so I won’t freak out if you need me to poke around in the shell.
Paul
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
MintBean
Re: Can’t update anything
Post
by MintBean » Sun Oct 29, 2017 8:31 pm
Hi Paul,
What’s this give you when entered in the terminal?
apt-cache policy util-linux
-
coloradoauthor
Re: Can’t update anything
Post
by coloradoauthor » Sun Oct 29, 2017 8:33 pm
Thanks for the quick response. Here’s what I get:
Code: Select all
$ apt-cache policy util-linux
util-linux:
Installed: 2.27.1-6ubuntu3.3
Candidate: 2.27.1-6ubuntu3.3
Version table:
*** 2.27.1-6ubuntu3.3 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.27.1-6ubuntu3 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
-
MintBean
Re: Can’t update anything
Post
by MintBean » Sun Oct 29, 2017 8:41 pm
I’m not understanding why your install was complaining about util-linux which shows as all present and correct.
Try this, although I’m not sure if it will help (but it won’t break anything either)
apt install util-linux
-
coloradoauthor
Re: Can’t update anything
Post
by coloradoauthor » Sun Oct 29, 2017 8:52 pm
As expected, it found the current version installed, but I said ‘Y’ to continue with the update. It’s complaining of the same strange printer-related error:
Code: Select all
apt install util-linux
[sudo] password for paulg:
Reading package lists... Done
Building dependency tree
Reading state information... Done
util-linux is already the newest version (2.27.1-6ubuntu3.3).
0 upgraded, 0 newly installed, 0 to remove and 620 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] y
Setting up util-linux (2.27.1-6ubuntu3.3) ...
insserv: warning: script 'lprng' missing LSB tags and overrides
insserv: warning: script 'cupsys' missing LSB tags and overrides
insserv: warning: script 'lpd' missing LSB tags and overrides
insserv: There is a loop between service watchdog and lprng if stopped
insserv: loop involving service lprng at depth 2
insserv: loop involving service watchdog at depth 1
insserv: Stopping lprng depends on watchdog and therefore on system facility `$all' which can not be true!
insserv: Stopping cupsys depends on watchdog and therefore on system facility `$all' which can not be true!
insserv: Stopping lpd depends on watchdog 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 util-linux (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
util-linux
E: Sub-process /usr/bin/dpkg returned an error code (1)
-
lmintnewb2
Re: Can’t update anything
Post
by lmintnewb2 » Sun Oct 29, 2017 9:03 pm
Is the printer usb, wireless ? If usb … maybe try unplugging the sucker and reboot, then trying to upgrade. Still getting the same errors afterwards then yep, seems whatever printer driver installation and Brother Printer Installer (< had to google it. ) fiddling you did wasn’t the right course of action.
So likely reverse the process and remove whatever it is you fiddled with. Did Mint not support the printer out-of-box .. did you try ? Just for kicks would also go ahead and try upgrading in terminal «sudo apt-get update && sudo apt-get upgrade -s»
See what more output you get from that, the -s flag there is to simulate the upgrade, it won’t actually do it. Could at least give you more info as to what’s going wrong and where.
Last edited by lmintnewb2 on Sun Oct 29, 2017 9:06 pm, edited 1 time in total.
-
MintBean
Re: Can’t update anything
Post
by MintBean » Sun Oct 29, 2017 9:05 pm
Short of perhaps trying to uninstall your printer, this one is beyond my knowledge.
-
WharfRat
- Level 21
- Posts: 13834
- Joined: Thu Apr 07, 2011 8:15 pm
Re: Can’t update anything
Post
by WharfRat » Sun Oct 29, 2017 9:30 pm
coloradoauthor wrote:t looks to me like I must have done something wrong when I installed the MFC-790CW printer driver using the Brother Printer Installer
What and how did you install this printer driver
What does aptitude why-not util-linux and dpkg -l|grep -v ^ii return
-
coloradoauthor
Re: Can’t update anything
Post
by coloradoauthor » Sun Oct 29, 2017 9:38 pm
My printer doesn’t have native Mint support, so I had to install the drivers generously provided by Brother. Following recommendations elsewhere in the forums, I installed it as USB then as network (wireless).
I tried the simulated ugrade (-s is a great flag to know about—thanks!). I don’t see anything that screams «error.» I highlighted the one line which mentions util-linux, then truncated about 1300 lines of the output.
Code: Select all
sudo apt-get update && sudo apt-get upgrade -s >update-upgrade-output
Hit:1 http://archive.canonical.com/ubuntu xenial InRelease
Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:3 http://dl.google.com/linux/chrome/deb stable Release
Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Ign:6 http://mirror.stjschools.org/public/linuxmint-packages sarah InRelease
Hit:7 http://mirror.stjschools.org/public/linuxmint-packages sarah Release
Hit:9 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:10 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
Get:11 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]
Hit:12 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu xenial InRelease
Fetched 306 kB in 20s (15.0 kB/s)
Reading package lists... Done
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages have been kept back:
gnome-panel gnome-panel-data gstreamer0.10-plugins-good:i386
gstreamer0.10-plugins-good kodi kodi-bin libegl1-mesa libgl1-mesa-dri:i386
libgl1-mesa-dri libinput10 libmirclient9 libwayland-egl1-mesa libxatracker2
mesa-vdpau-drivers mintsystem
The following packages will be upgraded:
accountsservice adobe-flashplugin apt apt-transport-https apt-utils
apt-xapian-index archdetect-deb base-files bind9-host binutils bluetooth
bluez bluez-cups bluez-obexd btrfs-tools ca-certificates casper
chromium-codecs-ffmpeg-extra cifs-utils console-setup console-setup-linux
[i]<...etc etc...>[/i]
605 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
1 not fully installed or removed.
[b]Conf util-linux (2.27.1-6ubuntu3.3 Ubuntu:16.04/xenial-updates [amd64])[/b]
Inst base-files [18.0.1] (18.0.2 linuxmint:18/sarah [all])
Conf base-files (18.0.2 linuxmint:18/sarah [all])
Inst mount [2.27.1-6ubuntu3.1] (2.27.1-6ubuntu3.3 Ubuntu:16.04/xenial-updates [amd64])
Conf mount (2.27.1-6ubuntu3.3 Ubuntu:16.04/xenial-updates [amd64])
Inst tar [1.28-2.1] (1.28-2.1ubuntu0.1 Ubuntu:16.04/xenial-updates, Ubuntu:16.04/xenial-security [amd64])
Conf tar (1.28-2.1ubuntu0.1 Ubuntu:16.04/xenial-updates, Ubuntu:16.04/xenial-security [amd64])
Inst locales [2.23-0ubuntu3] (2.23-0ubuntu9 Ubuntu:16.04/xenial-updates, Ubuntu:16.04/xenial-security [all])
Inst libc-bin [2.23-0ubuntu3] (2.23-0ubuntu9 Ubuntu:16.04/xenial-updates, Ubuntu:16.04/xenial-security [amd64])
Conf libc-bin (2.23-0ubuntu9 Ubuntu:16.04/xenial-updates, Ubuntu:16.04/xenial-security [amd64])
Inst gcc-5-base:i386 [5.4.0-6ubuntu1~16.04.4] (5.4.0-6ubuntu1~16.04.5 Ubuntu:16.04/xenial-updates [i386]) [gcc-5
-base:amd64 on gcc-5-base:i386] [gcc-5-base:i386 on gcc-5-base:amd64] [gcc-5-base:amd64 libstdc++6:i386 ]
[i]<...etc etc...>[/i]
Now that I am seeing some of what apt-get does, let’s see what happens if I were to install just one thing using apt-get.
Code: Select all
sudo apt-get install -s mint-artwork-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
mint-artwork-common
1 upgraded, 0 newly installed, 0 to remove and 619 not upgraded.
1 not fully installed or removed.
[b]Conf util-linux (2.27.1-6ubuntu3.3 Ubuntu:16.04/xenial-updates [amd64])[/b]
Inst mint-artwork-common [2.0.6] (2.0.9 linuxmint:18/sarah [all])
Conf mint-artwork-common (2.0.9 linuxmint:18/sarah [all])
I find it interesting that util-linux seems to be involved with updates in general.
I’ll give it until tomorrow to see if anyone comes up with a better idea, then I’ll try uninstalling the printer and see what happens.
Last edited by WharfRat on Sun Oct 29, 2017 9:55 pm, edited 1 time in total.
Reason: Changed quote tags to code tags
-
coloradoauthor
Re: Can’t update anything
Post
by coloradoauthor » Sun Oct 29, 2017 9:55 pm
More info for WharfRat:
Code: Select all
$ aptitude why-not util-linux
C util-linux Conflicts util-linux:i386
C util-linux Provides util-linux:i386
Code: Select all
$ dpkg -l|grep -v ^ii
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-============================================-==========================================-============-===============================================================================
rc oem-config 2.21.63+linuxmint3 all Perform end-user configuration after initial OEM installation
rc oem-config-gtk 2.21.63+linuxmint3 all GTK+ frontend for end-user post-OEM-install configuration
it systemd 229-4ubuntu7 amd64 system and service manager
iF util-linux 2.27.1-6ubuntu3.3 amd64 miscellaneous system utilities
Last edited by WharfRat on Sun Oct 29, 2017 10:00 pm, edited 1 time in total.
Reason: Changed quote tag to code tag
-
WharfRat
- Level 21
- Posts: 13834
- Joined: Thu Apr 07, 2011 8:15 pm
Re: Can’t update anything
Post
by WharfRat » Sun Oct 29, 2017 9:59 pm
You have a conflict so apt won’t go anywhere until that situation is rectified.
What does this show dpkg -l|grep util-linux
-
coloradoauthor
Re: Can’t update anything
Post
by coloradoauthor » Sun Oct 29, 2017 10:07 pm
$ dpkg -l|grep util-linux
iF util-linux 2.27.1-6ubuntu3.3 amd64 miscellaneous system utilities
-
lmintnewb2
Re: Can’t update anything
Post
by lmintnewb2 » Sun Oct 29, 2017 10:11 pm
«sudo apt-get -f install» should clear up the not fully installed thingy. Lol, that is one strange error in why-not. See what happens with the above command. Could always throw another -s onto it if you’re in a cautious mood (by the way I am advising you to use -s on it.)
Let us know what the output has to say.
«apt-cache show util-linux»
Description-en: miscellaneous system utilities
This package contains a number of important utilities, most of which
are oriented towards maintenance of your system. Some of the more
important utilities included in this package allow you to partition
your hard disk, view kernel messages, and create new filesystems.
That simulated run through upgrade looks fine to me. After doing the «sudo apt-get -f install» thing if all goes well ( ah go ahead and post the output so we can look it over too … Then if all is well)run the afore-mentioned upgrade command w/o the -s. Though honestly 600+ packages are a TON of upgrades, I’d use «sudo apt-get dist-upgrade» instead of upgrade. Yeah … yeah, this is where I get jumped about using dist-upgrade overrides the mintupdate and yada yada. While using LM10 ( and Lmde) dist-upgrade’d them both constantly and never had a single problem.
Last edited by lmintnewb2 on Sun Oct 29, 2017 10:26 pm, edited 1 time in total.
-
WharfRat
- Level 21
- Posts: 13834
- Joined: Thu Apr 07, 2011 8:15 pm
Re: Can’t update anything
Post
by WharfRat » Sun Oct 29, 2017 10:22 pm
util-linux:i386 and util-linux conflct — that is both cannot be installed, it’s one or the other.
I don’t know what that printer driver contained, but it’s my guess that it has something to do with this conflict.
So I would suggest backing out that package or whatever it was then running sudo dpkg-reconfigure util-linux
-
lmintnewb2
Re: Can’t update anything
Post
by lmintnewb2 » Sun Oct 29, 2017 10:29 pm
^ +1 WarfRat, was going to say the same thing «dpkg -l |grep packagename». Hadn’t seen this
dpkg -l|grep util-linux
iF util-linux 2.27.1-6ubuntu3.3 amd64 miscellaneous system utilities
Your Mint is 64bit and somehow you’ve managed to end up w an i386 (32bit ) version of that package. The command I gave should rectify it but still use the -s flag to be safe. See what else it wants to remove or do to fix the OS. Wth is this Brother Printer Installer thing ?!
-
coloradoauthor
Re: Can’t update anything
Post
by coloradoauthor » Sun Oct 29, 2017 11:05 pm
The i386 version of util-linux sure looks out of place on my AMD system!
The output of apt-get -f install -s didn’t look promising at all, so I tried it without the -s with no luck:
Code: Select all
$ sudo apt-get -f install -s
[sudo] password for paulg:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 620 not upgraded.
1 not fully installed or removed.
Conf util-linux (2.27.1-6ubuntu3.3 Ubuntu:16.04/xenial-updates [amd64])
paulg@mintbox ~ $ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 620 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up util-linux (2.27.1-6ubuntu3.3) ...
insserv: warning: script 'lprng' missing LSB tags and overrides
insserv: warning: script 'cupsys' missing LSB tags and overrides
insserv: warning: script 'lpd' missing LSB tags and overrides
insserv: There is a loop between service watchdog and lprng if stopped
insserv: loop involving service lprng at depth 2
insserv: loop involving service watchdog at depth 1
insserv: Stopping lprng depends on watchdog and therefore on system facility `$all' which can not be true!
insserv: Stopping cupsys depends on watchdog and therefore on system facility `$all' which can not be true!
insserv: Stopping lpd depends on watchdog 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 util-linux (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
util-linux
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reconfiguring util-linux seems promising. But here’s what I got without backing out the printer driver:
Code: Select all
$ sudo dpkg-reconfigure util-linux
/usr/sbin/dpkg-reconfigure: util-linux is broken or not fully installed
Hopefully I’ll have time tomorrow to try uninstalling the printer driver then repairing util-linux and we’ll see what happens.
Thanks for all your help so far. I’m learning a lot along the way.
-
lmintnewb2
Re: Can’t update anything
Post
by lmintnewb2 » Sun Oct 29, 2017 11:13 pm
Try «sudo dpkg —configure -a» and see what happens. Btw: Mentioned you should’ve checked before running that «sudo apt-get -f install» command w/o the -s. Sometimes apt ( esp on a highly pre-config’ed OS) might decide to get really jiggy with it. Never really had any problems but learned a bit about what I’m doing. Anyway the output looks fine.
After the above go ahead and proceed to step two, running the «sudo apt-get dist-upgrade -s» command, again with the -s flag and post the terminal output. Just being overly cautious, were my system damn the torpedo’s !!!!!! … but then have also learned a thing or 3 about borking and unborking stuff by this point. This doesn’t work, could have to resort to getting jiggy with it too. You would’ve finished reinstalling fresh 2 1/2hrs ago. Oh well it’s a process, ya break it, ya learn stuff, ya fix it, ya learn stuff … ya break it again, OVER and OVER and OVER AHHHHH !
Lmao I’m from that school of gnu/Linux thought, if you aren’t breaking it(then eventually unbreak’ing it w/o having to resort to reinstalling), then you probably aren’t trying very hard or doing much of anything interesting with that gnu/Linux operating system.
-
WharfRat
- Level 21
- Posts: 13834
- Joined: Thu Apr 07, 2011 8:15 pm
Re: Can’t update anything
Post
by WharfRat » Sun Oct 29, 2017 11:43 pm
lmintnewb2,
Non of that is going to fly with these errors
Code: Select all
insserv: warning: script 'lprng' missing LSB tags and overrides
insserv: warning: script 'cupsys' missing LSB tags and overrides
insserv: warning: script 'lpd' missing LSB tags and overrides
insserv: Stopping lprng depends on watchdog and therefore on system facility `$all' which can not be true!
insserv: Stopping cupsys depends on watchdog and therefore on system facility `$all' which can not be true!
insserv: Stopping lpd depends on watchdog and therefore on system facility `$all' which can not be true!
@coloradoauthor,
Can you paste backhead $(ls /etc/init.d/{lpd,cupsys,lprng})
-
lmintnewb2
Re: Can’t update anything
Post
by lmintnewb2 » Mon Oct 30, 2017 1:02 am
Ok getting a headache, lucky have enough time to have one or 2 more cuppa coffee before shutdown time. Had to google this, don’t have anything LM installed, don’t have anything recent Mint iso-ish handy either. My OS is uber customized w tons of odd-ball configs choosen, don’t even have insserv, nor cups installed. Started out it’s life as a minimal Stretch netinstall and I applied all kinds of my preferred whackiness from there. So whatcha supposed to do ? Google of course.
Found this in which the guy says a possible cure for this is simply to remove insserv. Kinda dated 2013 but can again use -s without risk. Such as «sudo apt-get remove insserv -s». AGAIN pay real close attention now to anything else it says apt is planning on removing should you actually proceed with it w/o -s. Can safely see what the output has to say about it. Buncha other stuff running through my bean though, so will come back later and check up on the OP/thread.
Don’t even think he has a 32bit version of util-linux. Though not sure, «dpkg -l |grep util-linux» is still showing the amd64(64bit) version installed. Would think if so, it’d be showing as util-linux:i386 or more than one entry. For example my OS is multi-arch, originally it was pure 32bit but I added the amd64 foreign architecture, installed a 64bit kernel, 64bit browsers … buncha other stuff, one of those stuff’s was upgrading systemd to the latest amd64 version from stretch-backports.
So when I do «dpkg -l |grep systemd» I get the following output.
ii libpam-systemd:amd64 234-3~bpo9+1 amd64 system and service manager — PAM module
ii libpam-systemd:i386 234-3~bpo9+1 i386 system and service manager — PAM module
ii libsystemd0:amd64 234-3~bpo9+1 amd64 systemd utility library
ii libsystemd0:i386 234-3~bpo9+1 i386 systemd utility library
ii systemd:amd64 234-3~bpo9+1 amd64 system and service manager
ii systemd-sysv:amd64 234-3~bpo9+1 amd64 system and service manager — SysV links
Clearly showing there are two packages installed anyway. Assuming the i368 versions were kept around cause other i386 packages I’ve got installed depend on them. Told you my install is whacky. Anyway, this is getting way off track. I’m uber-tired. Might try going ahead and checking out removing insserv WITH the -s flag and see what it says. What’s it got to say Coloradoauthor ? With the -s !!! DO NOT decide to just go ahead and let-em run w/o posting output and getting feedback. Sheesh … we’ve all done so much to try to get your install working, kinda starting to feel like the thing is family !!!
Oops, also you’re welcome for any tips/pointers, consider it a pay it forward kind of thing. TONS of people over the last couple decades made all this awesome software, shared info … contributed in however many ways and then share it free ?!?!?! Helping or sharing info with other nixers is only right n feels good. Yeah agree with you, believe package management in cli(terminal) is the way to go. Quit using any type of graphical frontend to do it probably 1 1/2months after getting into gnu/Linux. You get so much more information, so much more control and once you spend some time learning about it, faster, better … runs circles around synaptic or whichever.
Last edited by lmintnewb2 on Mon Oct 30, 2017 1:23 am, edited 3 times in total.
Hi everyone, I am having problems with my raspberry pi 3.
When I write:
Code: Select all
dpkg: dependency problems prevent configuration of systemd:
systemd depends on libsystemd0 (= 215-17+deb8u3); however:
Version of libsystemd0:armhf on system is 215-17+deb8u6.
systemd depends on udev (>= 208-8); however:
Package udev is not installed.
dpkg: error processing package systemd (--configure):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.7.0.2-5) ...
dpkg: dependency problems prevent configuration of bluez:
bluez depends on udev (>= 170-1); however:
Package udev is not installed.
dpkg: error processing package bluez (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
systemd
bluez
so I use:
Code: Select all
sudo apt-get update
sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
systemd : Depends: libsystemd0 (= 215-17+deb8u3) but 215-17+deb8u6 is installed
Recommends: libpam-systemd but it is not installed
udev : Depends: libudev1 (= 215-17+deb8u3) but 215-17+deb8u6 is installed
E: Unmet dependencies. Try using -f
Then:
Code: Select all
sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
systemd systemd-sysv udev
Suggested packages:
systemd-ui
Recommended packages:
libpam-systemd
The following packages will be upgraded:
systemd systemd-sysv udev
3 upgraded, 0 newly installed, 0 to remove and 131 not upgraded.
3 not fully installed or removed.
Need to get 3,098 kB of archives.
After this operation, 8,192 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://mirrordirector.raspbian.org/raspbian/ jessie/main udev armhf 215-17+deb8u6 [850 kB]
Get:2 http://mirrordirector.raspbian.org/raspbian/ jessie/main systemd armhf 215-17+deb8u6 [2,212 kB]
Get:3 http://mirrordirector.raspbian.org/raspbian/ jessie/main systemd-sysv armhf 215-17+deb8u6 [36.3 kB]
Fetched 3,098 kB in 2s (1,129 kB/s)
Preconfiguring packages ...
(Reading database ... 58000 files and directories currently installed.)
Preparing to unpack .../udev_215-17+deb8u6_armhf.deb ...
And it get stopped and take me out from my connection to the raspberry.
Can anyone help me, or give me an advice por it?
Thanks.
-
Anic297
- Posts: 7
- Joined: 2016-10-17 14:48
Installation broken; can’t install or update
#1
Post
by Anic297 » 2018-12-04 12:28
Hello,
When I try to update my Debian configuration, using “apt-get update”, I get this in the process:
dpkg: error processing package procps (—configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of udev:
udev depends on procps; however:
Package procps is not configured yet.
dpkg: error processing package udev (—configure):
dependency problems — leaving unconfigured
dpkg: dependency problems prevent configuration of systemd:
systemd depends on udev (>= 208-8); however:
Package udev is not configured yet.
dpkg: error processing package systemd (—configure):
dependency problems — leaving unconfigured
Processing triggers for libc-bin (2.19-18+deb8u10) …
Errors were encountered while processing:
procps
udev
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)
I have searched on the Internet, but so far, no answer helped me. Also, please note I’m not an advanced Linux user.
I have the feeling my installation is completely broken and I have no other choice than reinstalling the OS (but I can’t as it’s a VPS; at least, I don’t know how).
Any help welcome.
-
bw123
- Posts: 3940
- Joined: 2011-05-09 06:02
- Has thanked: 1 time
- Been thanked: 10 times
Re: Installation broken; can’t install or update
#3
Post
by bw123 » 2018-12-04 13:44
That’s the first thing I’d check, bad pkg from a non-debian source?
Many pkgs use scripts during install/remove, and they store them and info about themselves in /var/lib/dpkg/info
Sometimes this info can be corrupted during unpacking, and lead to this kind of error. The file mentioned (procps.postinst) should be 3481 bytes, and it is a readable script, no foreign characters in it. Or maybe one of the other procps.* files may be corrupt. This seems to happen on sd-card installations more often. Usually removing the files manually and reinstalling the pkg clears it up.
Code: Select all
$ ls -l /var/lib/dpkg/info/procps.postinst
-rwxr-xr-x 1 root root 3481 May 17 2018 /var/lib/dpkg/info/procps.postinst
resigned by AI ChatGPT
-
Anic297
- Posts: 7
- Joined: 2016-10-17 14:48
Re: Installation broken; can’t install or update
#5
Post
by Anic297 » 2018-12-04 14:16
Ok, the file I have has a different size:
root@<server>:~# ls -l /var/lib/dpkg/info/procps.postinst
-rwxr-xr-x 1 root root 3439 May 17 2018 /var/lib/dpkg/info/procps.postinst
However, it ends with “exit 0” and 3 blank lines, so it looks good to me (?).
Thanks.
-
None1975
- Posts: 1058
- Joined: 2015-11-29 18:23
- Location: Russia, Kaliningrad
- Has thanked: 3 times
- Been thanked: 4 times
Re: Installation broken; can’t install or update
#6
Post
by None1975 » 2018-12-04 16:40
That’s the culprit. Debian Stable should not be combined with other releases. If you’re trying to install software that isn’t available in the current Debian Stable release, it’s not a good idea to add repositories for other Debian releases. The problems might not happen right away, but the next time you install updates.
-
#1
Switched apt/sources.list and apt/source.list.d from buster to bullseye and did apt update && apt full-upgrade and I end with a systemd failure.
Only thing really installed is wireguard.
Bash:
Created symlink /etc/systemd/system/sysinit.target.wants/systemd-pstore.service -> /lib/systemd/system/systemd-pstore.service.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error exit status 73
dpkg: dependency problems prevent configuration of systemd-sysv:
systemd-sysv depends on systemd; however:
Package systemd is not configured yet.
dpkg: error processing package systemd-sysv (--configure):
dependency problems - leaving unconfigured
Setting up dmsetup (2:1.02.175-2.1) ...
Errors were encountered while processing:
systemd
systemd-sysv
E: Sub-process /usr/bin/dpkg returned an error code (1)
Last edited: Feb 10, 2022
-
#2
Hi,
I tested it here… works as expected! what is your LXC config look like pct config CTID? and can you provide us with the output of pveversion -v?
EDIT:
the sources.* from the LXC as well
Bash:
grep '' /etc/apt/sources.list && grep '' /etc/apt/sources.list.d/*
Last edited: Feb 11, 2022
-
#3
Thanks for taking a look. Here are the items you requested.
Code:
root@pve:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-3-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-10
pve-kernel-5.13: 7.1-7
pve-kernel-5.11: 7.0-10
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-1
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
Code:
root@pve:~# pct config 109
arch: amd64
cores: 1
features: nesting=1
hostname: wireguard
memory: 1024
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.2.1,hwaddr=62:3B:E2:11:FB:C6,ip=192.168.2.2/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-109-disk-2,size=8G
swap: 1024
unprivileged: 0
lxc.cgroup2.devices.allow: c 10:200 rwm
lxc.mount.entry: /dev/net dev/net none bind,create=dir
Code:
root@wireguard:~# grep '' /etc/apt/sources.list && grep '' /etc/apt/sources.list.d/*
deb http://ftp.debian.org/debian buster main contrib
deb http://ftp.debian.org/debian buster-updates main contrib
deb http://security.debian.org buster/updates main contrib
deb http://deb.debian.org/debian buster-backports main
grep: /etc/apt/sources.list.d/*: No such file or directory
-
#4
You are still using the buster (Debian 10) repos?
Last edited: Feb 11, 2022
-
#5
No, I had swapped them all to bullseye prior to the upgrade.
Code:
deb http://deb.debian.org/debian bullseye main
deb-src http://deb.debian.org/debian bullseye main
deb https://deb.debian.org/debian-security bullseye-security main contrib
deb-src https://deb.debian.org/debian-security bullseye-security main contrib
deb http://deb.debian.org/debian bullseye-updates main
deb-src http://deb.debian.org/debian bullseye-updates main
deb http://deb.debian.org/debian bullseye-backports main
deb-src http://deb.debian.org/debian bullseye-backports main
-
#6
No, I had swapped them all to bullseye prior to the upgrade.
But the output inside your container shows buster repos. You need to change them there too, if you want to upgrade your LXC from buster to bullseye.
-
#7
Yes, I’m showing what they are before I started the upgrade. I changed them to bullseye prior to starting within the LXC. (If I hadn’t it would have just upgraded buster to the latest packages)
Last edited: Feb 11, 2022
-
#8
@Moayad I’m just going to setup a new container on debian 11 and migrate the configs.
-
#9
In the Debian 10 lxc you have to change the sources to:
Code:
deb http://ftp.debian.org/debian bullseye main contrib
deb http://ftp.debian.org/debian bullseye-updates main contrib
deb http://security.debian.org bullseye-security main contrib
then upgrade by using apt update -y && apt full-upgrade -y commands. However, you can test that on a test LXC container in your Proxmox VE to see if the issue is repeatable.
-
#10
Just tried it again with your 3 lines. Repeatable.
I think these might be my problem but I don’t understand what they are.
Code:
Setting up systemd (247.3-6) ...
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal/d46b5b6aa1b44656b1a8994a8c36a29e.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal/d46b5b6aa1b44656b1a8994a8c36a29e.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal/d46b5b6aa1b44656b1a8994a8c36a29e.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal/d46b5b6aa1b44656b1a8994a8c36a29e/system.journal.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal/d46b5b6aa1b44656b1a8994a8c36a29e/system.journal.
Somehow it seems my ownership on a lot of files is wrong.
Just a temporary test I did:
chown -R root:root /
SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles —create —prefix /var/log/journal
Now apt full-upgrade -y completes.
Weird, I don’t know how the ownership got messed up. I also don’t know how to restore ownership to what it should actually be instead of root:root.
Lastly, I noticed a peculiar message during upgrade.
Error! The /var/lib/dkms/wireguard/1.0.20210219/5.10.0-11-amd64/x86_64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch. This indicates that it should not be built.
This post helped me figure that out.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950684
Last edited: Feb 15, 2022




