package dictionaries-common 1.20.2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 255
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dictionaries-common (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
In the middle of a release upgrade, I am suddenly presented with a crash report. I am in the middle of it, so I do not know wether this will leave me with an incomplete system (again, after the bug about my processor that DOES support pae, but is not recognized) or not.
I did not do anything special, other than:
sudo do-release-upgrade -d
I added the -d option because even upgrading from a less-than a year old Xubuntu version (13.04 to 13.10, current) no longer works normally.
Output of lsb_release -rd:
Description: Ubuntu 13.10
Release: 13.10
But notice that I am in the middle of upgrading to that version.
I would off course expect the release upgrade to succeed, not a crash report.
For the record, I am upgrading the machine over an SSH connection with X support enabled.
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: dictionaries-common 1.20.2
ProcVersionSign
Uname: Linux 3.8.0-35-generic i686
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
Date: Mon Apr 14 12:14:07 2014
DuplicateSignature: package:
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 255
InstallationDate: Installed on 2011-09-01 (955 days ago)
InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MarkForUpload: True
PackageArchitec
SourcePackage: dictionaries-common
Title: package dictionaries-common 1.20.2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 255
UpgradeStatus: Upgraded to saucy on 2014-04-14 (0 days ago)
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1211151, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.