package menu 2.1.47ubuntu3 failed to install/upgrade: triggers looping, abandoned

Bug #1825211 reported by Brian Murray
This bug report is a duplicate of:  Bug #1828639: Unlooping all the trigger loops!!!!!. Edit Remove
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
Confirmed
Undecided
Unassigned
Disco
Confirmed
Undecided
Unassigned

Bug Description

This was during a "regular" update of Disco during its development cycle.

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: menu 2.1.47ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Wed Apr 17 08:35:29 2019
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2016-01-22 (1180 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
RelatedPackageVersions:
 dpkg 1.19.6ubuntu1
 apt 1.8.0
SourcePackage: menu
Title: package menu 2.1.47ubuntu3 failed to install/upgrade: triggers looping, abandoned
UpgradeStatus: Upgraded to disco on 2019-01-22 (84 days ago)

Revision history for this message
Brian Murray (brian-murray) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in menu (Ubuntu):
status: New → Confirmed
Revision history for this message
Jonathan Polak (jpolak) wrote :

this error causes termination of upgrade from 18.10 -> 19.04

Revision history for this message
w2vy (tom-moulton) wrote :

Happened during upgrade from 18.10 to 19.04 but the system did update with nothing catastrophic obvious

Revision history for this message
Julian Andres Klode (juliank) wrote :

Let's reassign to dpkg, this is not caused by menu; and happens during dpkg --configure-pending

affects: menu (Ubuntu) → dpkg (Ubuntu)
Revision history for this message
Brian Murray (brian-murray) wrote :

Attached is my dpkg.log file from the incident.

Revision history for this message
Brian Murray (brian-murray) wrote :
tags: added: id-5cc1d062b6d1072e603f4c6e
Revision history for this message
Brian Murray (brian-murray) wrote :

Julian had asked about events in term.log surrounding unpacking openssl. Here's what I found:

Preparing to unpack .../184-libpcre3_2%3a8.39-12_amd64.deb ...^M
De-configuring libpcre3:i386 (2:8.39-11) ...^M
Unpacking libpcre3:amd64 (2:8.39-12) over (2:8.39-11) ...^M
Preparing to unpack .../185-libpcre3_2%3a8.39-12_i386.deb ...^M
Unpacking libpcre3:i386 (2:8.39-12) over (2:8.39-11) ...^M
Preparing to unpack .../186-passwd_1%3a4.5-1.1ubuntu2_amd64.deb ...^M
Unpacking passwd (1:4.5-1.1ubuntu2) over (1:4.5-1.1ubuntu1) ...^M
Setting up passwd (1:4.5-1.1ubuntu2) ...^M
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 321448 files and directories currently installed.)^M
Preparing to unpack .../000-openssl_1.1.1b-1ubuntu2_amd64.deb ...^M
Unpacking openssl (1.1.1b-1ubuntu2) over (1.1.1b-1ubuntu1) ...^M
Preparing to unpack .../001-tzdata_2019a-1_all.deb ...^M
Unpacking tzdata (2019a-1) over (2018i-2) ...^M
Preparing to unpack .../002-ubuntu-advantage-tools_19.4_amd64.deb ...^M
Unpacking ubuntu-advantage-tools (19.4) over (18) ...^M
Preparing to unpack .../003-ubuntu-minimal_1.431_amd64.deb ...^M
Unpacking ubuntu-minimal (1.431) over (1.430) ...^M

Revision history for this message
Brian Murray (brian-murray) wrote :

I was able to recreate this today by taking a stock cosmic lxc image, installing ubuntu-mate-desktop, and then upgrading to disco. Here's the DuplicateSignature from the crash:

== DuplicateSignature =================================
package:libvlc-bin:3.0.6-1
Setting up fontconfig (2.13.1-2ubuntu2) ...
Regenerating fonts cache... done.
dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  bamfdaemon -> mime-support
 packages' pending triggers which are or may be unresolvable:
  libvlc-bin:amd64: /usr/lib/x86_64-linux-gnu/vlc/plugins
  dbus: /etc/dbus-1/system.d
  ca-certificates: update-ca-certificates
  gnome-icon-theme: /usr/share/icons/gnome
  libc-bin: ldconfig
  dictionaries-common: update-default-ispell: update-default-wordlist: aspell-autobuildhash
  hicolor-icon-theme: /usr/share/icons/hicolor
  initramfs-tools: update-initramfs
  mime-support: /usr/share/applications: /usr/lib/mime/packages
  bamfdaemon: /usr/share/applications
dpkg: error processing package libvlc-bin:amd64 (--configure):
 triggers looping, abandoned

I submitted bug 1828639 with details.

Revision history for this message
Brian Murray (brian-murray) wrote :

The following bug report looks very similar to this one:

https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823004

Changed in dpkg (Ubuntu Disco):
status: New → Confirmed
Revision history for this message
N8JUC@YAHOO.COM (n8juc) wrote : Re: [Bug 1825211] Re: package menu 2.1.47ubuntu3 failed to install/upgrade: triggers looping, abandoned

Hi Brian:

Can u merge 'em??? Or tack mine onto the original one?

Thanks,

John

On 5/31/19 2:08 PM, Brian Murray wrote:
> The following bug report looks very similar to this one:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
> upgrader/+bug/1823004
>
> ** Also affects: dpkg (Ubuntu Disco)
> Importance: Undecided
> Status: New
>
> ** Changed in: dpkg (Ubuntu Disco)
> Status: New => Confirmed
>

Revision history for this message
Julian Andres Klode (juliank) wrote :

Marking trigger bugs as duplicates of 1828639, to have one bug to track the fix in with a clean reproducer.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.