package man-db 2.7.0.2-5 failed to install/upgrade: triggers looping, abandoned

Bug #1415327 reported by Jonathan Mounier
72
This bug affects 15 people
Affects Status Importance Assigned to Milestone
man-db (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

did not upgrade to 15.04

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: man-db 2.7.0.2-5
ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
Uname: Linux 3.18.0-11-generic x86_64
NonfreeKernelModules: fglrx wl
ApportVersion: 2.15.1-0ubuntu4
Architecture: amd64
Date: Tue Jan 27 23:42:16 2015
DuplicateSignature: package:man-db:2.7.0.2-5:triggers looping, abandoned
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2015-01-15 (13 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: man-db
Title: package man-db 2.7.0.2-5 failed to install/upgrade: triggers looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jonathan Mounier (thunderpr) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote :

This may be a hardware issue, please try to discover the cause of the following messages in your logs:

[ 1062.198382] pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver ID)
[ 1062.198387] pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00000001/00002000
[ 1062.198391] pcieport 0000:00:03.0: [ 0] Receiver Error (First)
[ 1063.672409] pcieport 0000:00:03.0: AER: Corrected error received: id=0018
[ 1063.672422] pcieport 0000:00:03.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver ID)
[ 1063.672426] pcieport 0000:00:03.0: device [8086:2f08] error status/mask=00000001/00002000
[ 1063.672430] pcieport 0000:00:03.0: [ 0] Receiver Error (First)
[ 1065.793117] pcieport 0000:00:03.0: AER: Corrected error received: id=0018

Thanks

information type: Private Security → Public
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 man-db (Ubuntu):
status: New → Confirmed
Changed in man-db (Ubuntu):
importance: Undecided → High
Revision history for this message
Brian Murray (brian-murray) wrote :

From DpkgTerminalLog.txt:

dpkg: cycle found while processing triggers:
 chain of packages whose triggers are or may be responsible:
  bamfdaemon -> libc-bin
 packages' pending triggers which are or may be unresolvable:
  man-db: /usr/share/man
  libc-bin: ldconfig
  bamfdaemon: /usr/share/applications
  gnome-icon-theme: /usr/share/icons/gnome
dpkg: error processing package man-db (--remove):
 triggers looping, abandoned

Luke Faraone (lfaraone)
Changed in man-db (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Luke Faraone (lfaraone)
Revision history for this message
Luke Faraone (lfaraone) wrote :

Unable to reproduce this on an upgrade from 14.04->14.10->15.04 with latest packages. If you can, please feel free to reopne.

Changed in man-db (Ubuntu):
assignee: Luke Faraone (lfaraone) → nobody
status: In Progress → Incomplete
Revision history for this message
Andriopoulos Nikolaos (sirnicolas21) wrote :

just happent on me also on 14.10->15.04, i will have to add that the package update procedure crashed and the upgrade never finished normally.... i cannot find any logs so i can see why it failed.

Revision history for this message
Andriopoulos Nikolaos (sirnicolas21) wrote :

upgrade log file.

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 man-db (Ubuntu):
status: Incomplete → Won't Fix
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.