doc-base triggers fails with a segmentation fault

Bug #796145 reported by mitch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
doc-base (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: dpkg

just trying to upgrade and this error showed up so you tell me

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: aspell 0.60.6-3ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-33.66-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
Architecture: i386
Date: Sun Jun 12 01:23:49 2011
ErrorMessage: ErrorMessage: package aspell is already installed and configured
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
SourcePackage: dpkg
Title: package aspell 0.60.6-3ubuntu1 failed to install/upgrade: ErrorMessage: package aspell is already installed and configured

Revision history for this message
mitch (mitch987) wrote :
Revision history for this message
Raphaël Hertzog (hertzog) wrote :

The precise error is this one:
Unpacking replacement libcomerr2 ...

Processing triggers for man-db ...

Processing triggers for ureadahead ...

Processing triggers for python-gmenu ...

Rebuilding /usr/share/applications/desktop.en_US.utf8.cache...

Processing triggers for desktop-file-utils ...

Processing triggers for doc-base ...

Segmentation fault

dpkg: error processing doc-base (--unpack):

 subprocess installed post-installation script returned error exit status 139

Processing triggers for install-info ...

Processing triggers for python-support ...

Errors were encountered while processing:

 doc-base

The other error about aspell is that the .deb is corrupted. You should do apt-get clean and retry the upgrade. Reassigning to doc-base for the first (transient) error.

summary: - package aspell 0.60.6-3ubuntu1 failed to install/upgrade: ErrorMessage:
- package aspell is already installed and configured
+ doc-base triggers fails with a segmentation fault
affects: dpkg (Ubuntu) → doc-base (Ubuntu)
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.