package cryptsetup 2:1.6.1-1ubuntu7 failed to install/upgrade: η υποδιεργασία installed post-installation script επέστρεψε κατάσταση λάθους 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
cryptsetup was on upgrade procedure, but there are no crypt filesystems in my installation. Additionally it is a live ubuntu-mate 15.04 beta2 usb installation with casper-rw file.
Further system informations:
1) ubuntu-
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
2) ubuntu-
cryptsetup:
Εγκατεστημένα: 2:1.6.1-1ubuntu7
Υποψήφιο: 2:1.6.1-1ubuntu7
Πίνακας Έκδοσης:
*** 2:1.6.1-1ubuntu7 0
500 http://
100 /var/lib/
3)I expected to update initramfs but I suppose it is no possible in a live ubuntu install. Perhaps I'll just uninstall cryptsetup, as I don't use it.
4) The synaptic upgrade procedure couldn't upgrade cryptsetup.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: cryptsetup 2:1.6.1-1ubuntu7
ProcVersionSign
Uname: Linux 3.19.0-10-generic i686
ApportVersion: 2.16.2-0ubuntu5
Architecture: i386
CasperVersion: 1.357
Date: Mon Mar 30 13:52:06 2015
DuplicateSignature: package:
ErrorMessage: η υποδιεργασία installed post-installation script επέστρεψε κατάσταση λάθους 1
LiveMediaBuild: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta i386 (20150326)
RelatedPackageV
dpkg 1.17.24ubuntu1
apt 1.0.9.7ubuntu3
SourcePackage: cryptsetup
Title: package cryptsetup 2:1.6.1-1ubuntu7 failed to install/upgrade: η υποδιεργασία installed post-installation script επέστρεψε κατάσταση λάθους 1
UpgradeStatus: No upgrade log present (probably fresh install)
crypttab: # <target name> <source device> <key file> <options>
fstab:
overlay / overlay rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0
/dev/sdb2 swap swap defaults 0 0
tags: | removed: need-duplicate-check |
The DpkgTerminalLog.txt log file attached to this bug report is empty. It is not possible to diagnose a package upgrade error without this. If you can provide dpkg logs of the upgrade error in question, please attach them and reopen this bug report.