package shared-mime-info 1.3-1 failed to install/upgrade: triggers looping, abandoned

Bug #1429885 reported by Max
48
This bug affects 9 people
Affects Status Importance Assigned to Milestone
shared-mime-info (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

I just ran the updater from terminal.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: shared-mime-info 1.3-1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
Date: Mon Mar 9 16:49:17 2015
DuplicateSignature: package:shared-mime-info:1.3-1:triggers looping, abandoned
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-02-12 (24 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150211)
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.3-1 failed to install/upgrade: triggers looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Max (cofeiini) wrote :
description: updated
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 shared-mime-info (Ubuntu):
status: New → Confirmed
Changed in shared-mime-info (Ubuntu):
importance: Undecided → High
Revision history for this message
Brian Murray (brian-murray) wrote :

dpkg trigger cycle detection was an experimental feature in Debian, and subsequently Ubuntu, was has now been removed from dpkg. Therefore, this bug report is no longer valid and I'm marking it as such.

If you are interested in more information about this issue you could look at:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776910#42

Changed in shared-mime-info (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
Fergal Daly (fergal) wrote :

So is there another bug somewhere for the fact that a spurious crash reports are coming up during upgrade to 16.04?

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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