package libutempter0:i386 1.1.6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1555334 reported by salman manj qadri
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libutempter (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

during 1st update after 16.04 beta fresh upgrade from 14.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libutempter0:i386 1.1.6-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
Uname: Linux 4.4.0-11-generic i686
ApportVersion: 2.20-0ubuntu3
Architecture: i386
Date: Thu Mar 10 01:33:12 2016
Dependencies:
 gcc-6-base 6-20160227-0ubuntu1
 libc6 2.21-0ubuntu6
 libgcc1 1:6-20160227-0ubuntu1
DuplicateSignature:
 Setting up libutempter0:i386 (1.1.6-1ubuntu1) ...
 The utempter system group isn't used anymore by this package
 chown: cannot access '/usr/lib/utempter': No such file or directory
 dpkg: error processing package libutempter0:i386 (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2013-05-31 (1012 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt 1.2.4
SourcePackage: libutempter
Title: package libutempter0:i386 1.1.6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-03-09 (0 days ago)

Revision history for this message
salman manj qadri (salmanbluechip) 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 libutempter (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastian Stark (sebstark) wrote :

Creating '/usr/lib/utempter' manually seems to be a workaround.

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.