dpkg assert failure: dpkg: ../../src/packages.c:245: process_queue:
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| dpkg (Ubuntu) |
High
|
Unassigned | ||
| Bionic |
High
|
Unassigned |
Bug Description
I ran do-release-upgrade and had some problems with IBM specific packages. I then ran apt-get dist-upgrade and eventually got this error.
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: dpkg 1.18.2ubuntu5
ProcVersionSign
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelMo
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AssertionMessage: dpkg: ../../src/
Date: Mon Nov 2 11:22:52 2015
ExecutablePath: /usr/bin/dpkg
InstallationDate: Installed on 2015-07-15 (109 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
LANGUAGE=en_GB:en
Signal: 6
SourcePackage: dpkg
StacktraceTop:
__assert_fail_base (fmt=0x7f74e0c4f028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=
__GI___assert_fail (assertion=0x432360 "dependtry <= 4", file=0x4322ee "../../
?? ()
?? ()
?? ()
Title: dpkg assert failure: dpkg: ../../src/
UpgradeStatus: Upgraded to wily on 2015-11-02 (0 days ago)
UserGroups:
Matthew Jaggard (ubuntu-jaggard) wrote : | #1 |
Apport retracing service (apport) wrote : | #2 |
Changed in dpkg (Ubuntu): | |
importance: | Undecided → Medium |
tags: | removed: need-amd64-retrace |
tags: | added: zesty |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in dpkg (Ubuntu): | |
status: | New → Confirmed |
information type: | Private → Public |
Vincent Gerris (vgerris) wrote : | #7 |
I got the same issue on an upgrade of 17.10 to 18.04 development release
Brian Murray (brian-murray) wrote : | #8 |
This also happened to me when upgrading from 17.10 to 18.04 here's the relevant bit of the upgrade log files:
main.log:
2018-01-05 15:22:34,603 DEBUG failed to SystemUnLock() (E:Not locked)
2018-01-05 15:38:49,081 ERROR got an error from dpkg for pkg: 'systemd': 'triggers looping, abandoned'
2018-01-05 15:38:49,081 DEBUG running apport_pkgfailure() systemd: triggers looping, abandoned
2018-01-05 15:40:02,214 ERROR Exception during pm.DoInstall()
Traceback (most recent call last):
File "/tmp/ubuntu-
res = pm.do_install(
apt_pkg.Error: E:Sub-process /usr/bin/dpkg exited unexpectedly
2018-01-05 15:40:02,265 ERROR SystemError from cache.commit(): installArchives() failed
2018-01-05 15:40:02,265 ERROR found exception: 'E:Sub-process /usr/bin/dpkg exited unexpectedly'
apt-term.log:
Setting up gstreamer1.
dpkg: ../../src/
tags: | added: bionic rls-bb-incoming |
Brian Murray (brian-murray) wrote : | #9 |
There is a bucket for this in the Error Tracker here:
summary: |
- Problem upgrading IBM owned system to 15.10 + dpkg assert failure: dpkg: ../../src/packages.c:245: process_queue: |
Jean-Baptiste Lallement (jibel) wrote : | #10 |
Also happened to me during an upgrade from 17.10 to 18.04. I'm raising the importance.
Changed in dpkg (Ubuntu): | |
importance: | Medium → High |
Brian Murray (brian-murray) wrote : | #11 |
Here's some more details from apt-term.log for my upgrade.
4411 dpkg: cycle found while processing triggers:^M
4412 chain of packages whose triggers are or may be responsible:^M
4413 gnome-icon-theme -> bamfdaemon^M
4414 packages' pending triggers which are or may be unresolvable:^M
4415 systemd: /etc/init.d^M
4416 libc-bin: ldconfig^M
4417 bamfdaemon: /usr/share/
4418 gnome-icon-theme: /usr/share/
4419 sgml-base: update-
4420 initramfs-tools: update-initramfs^M
4421 shim-signed: shim-secureboot
4422 libgdk-
4423 dictionaries-
4424 ureadahead: /etc/init.d^M
4425 gconf2: /usr/share/
4426 dpkg: error processing package systemd (--configure):^M
4427 triggers looping, abandoned^M
....
4835 Setting up gstreamer1.
4836 dpkg: ../../src/
tags: | added: id-5a8770510f2c767f1820d61c |
tags: | removed: rls-bb-incoming |
Julian Andres Klode (juliank) wrote : | #12 |
So, from what I saw there indeed 4 dependtry with different semantics - see src/configure.
@Brian: The error tracker says it cannot find the problem.
I don't completely understand trigger looping, but maybe it's one of the situations again where some triggers are "interest" and can be made "interest-noawait"?
tags: | added: id-5ab94cb1c5f881e307a2751b |
Brian Murray (brian-murray) wrote : | #13 |
Here's a better link for the crash report in the Error Tracker:
https:/
The next one looks similar to the one above although it has a much lower count:
https:/
tags: | added: rls-bb-notfixing |
Changed in dpkg (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in dpkg (Ubuntu Bionic): | |
status: | Confirmed → Fix Released |
Changed in dpkg (Ubuntu Bionic): | |
status: | Fix Released → Triaged |
Changed in dpkg (Ubuntu): | |
status: | Fix Released → Triaged |
Steve Langasek (vorlon) wrote : | #14 |
https:/
Changed in dpkg (Ubuntu): | |
status: | Triaged → Fix Released |
StacktraceTop: assertion@ entry=0x432360 "dependtry <= 4", file=file@ entry=0x4322ee "../../ src/packages. c", line=line@ entry=245, function= function@ entry=0x432bd0 <__PRETTY_ FUNCTION_ _.6590> "process_queue") at assert.c:92 assertion@ entry=0x432360 "dependtry <= 4", file=file@ entry=0x4322ee "../../ src/packages. c", line=line@ entry=245, function= function@ entry=0x432bd0 <__PRETTY_ FUNCTION_ _.6590> "process_queue") at assert.c:101 packages. c:245 packages. c:162 a4c8) at ../../src/ main.c: 899
__assert_fail_base (fmt=0x7f74e0c4f028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=
__GI___assert_fail (assertion=
process_queue () at ../../src/
packages (argv=<optimized out>) at ../../src/
main (argc=<optimized out>, argv=0x7ffcea83