package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6

Bug #1606000 reported by Daniel Bantar
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Invalid
High
Unassigned
systemd (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

bug error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apt 1.2.12~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jul 24 09:52:56 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 6
InstallationDate: Installed on 2015-09-20 (308 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: apt
Title: package apt 1.2.12~ubuntu16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6
UpgradeStatus: Upgraded to xenial on 2016-07-24 (0 days ago)

Revision history for this message
Daniel Bantar (d-bantar) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Seth Arnold (seth-arnold) wrote :

There's a lot of errors like this in the journal:

ul 24 09:12:59 hostname systemd[1]: systemd-udevd.service: Failed with result 'signal'.
jul 24 09:13:02 hostname systemd[1]: [/lib/systemd/system/emergency.service:19] Not an absolute path, ignoring: -/root
jul 24 09:13:02 hostname systemd[1]: [/lib/systemd/system/rescue.service:18] Not an absolute path, ignoring: -/root
jul 24 09:13:02 hostname systemd[1]: [/lib/systemd/system/user@.service:20] Unknown lvalue 'TasksMax' in section 'Service'
jul 24 09:13:02 hostname systemd[1]: tmp.mount: Cannot add dependency job, ignoring: Unit tmp.mount failed to load: No such file or directory.

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 apt (Ubuntu):
status: New → Confirmed
Changed in systemd (Ubuntu):
status: New → Confirmed
Changed in apt (Ubuntu):
importance: Undecided → High
Changed in systemd (Ubuntu):
importance: Undecided → High
Revision history for this message
Julian Andres Klode (juliank) wrote :

The passwd file is in an inconsistent state, someone did not clean up a lock on it. We are using the same way to add users everyone else uses, so it's not our fault :)

Changed in apt (Ubuntu):
status: Confirmed → Invalid
Dan Streetman (ddstreet)
Changed in systemd (Ubuntu):
status: Confirmed → 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.