Ubuntu
xemacs21 package

package xemacs21 (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Bug #697424 reported by alain maronani on 2011-01-04

This bug report is a duplicate of: Bug #467446: update-alternatives: error: alternative path /usr/bin/xemacs21 doesn't exist.. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xemacs21 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: xemacs21

lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04

xemacs from stock distrib ubuntu xemacs21

synaptic install crashes

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: xemacs21 (not installed)
ProcVersionSignature: Ubuntu 2.6.32-26.48-generic-pae 2.6.32.24+drm33.11
Uname: Linux 2.6.32-26-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Jan 4 16:30:00 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
SourcePackage: xemacs21
Title: package xemacs21 (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Tags:

Revision history for this message

alain maronani (alain-maronani) wrote on 2011-01-04:

AptOrdering.txt Edit (525 bytes, text/plain; charset="utf-8")
Df.txt Edit (794 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (50.1 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (20.1 KiB, text/plain; charset="utf-8")

Revision history for this message

era (era) wrote on 2011-01-05:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #467446, so it 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. Feel free to continue to report any other bugs you may find.