octave3.2 fails to install via apt-get with libumfpack.so.3.2.0 error

Bug #465005 reported by udippel on 2009-10-30
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
octave3.2 (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: octave3.2

$ sudo apt-get install octave3.2
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  octave3.0-common libqt4-svg
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  libqrupdate1 octave3.2-common
Suggested packages:
  octave3.2-info octave3.2-doc octave3.2-htmldoc octave3.2-headers
  octave3.2-emacsen
The following NEW packages will be installed:
  libqrupdate1 octave3.2 octave3.2-common
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.9MB of archives.
[...]
Selecting previously deselected package libqrupdate1.
(Reading database ... 204693 files and directories currently installed.)
Unpacking libqrupdate1 (from .../libqrupdate1_1.0.1-1_amd64.deb) ...
Selecting previously deselected package octave3.2-common.
Unpacking octave3.2-common (from .../octave3.2-common_3.2.2-2build1_all.deb) ...
Selecting previously deselected package octave3.2.
Unpacking octave3.2 (from .../octave3.2_3.2.2-2build1_amd64.deb) ...
Processing triggers for desktop-file-utils ...
Processing triggers for man-db ...
Setting up libqrupdate1 (1.0.1-1) ...

Setting up octave3.2-common (3.2.2-2build1) ...
Setting up octave3.2 (3.2.2-2build1) ...
update-alternatives: using /usr/bin/octave-3.2.2 to provide /usr/bin/octave (octave) in auto mode.
update-alternatives: using /usr/bin/octave-bug-3.2.2 to provide /usr/bin/octave-bug (octave-bug) in auto mode.
octave-3.2.2: error while loading shared libraries: libumfpack.so.3.2.0: cannot open shared object file: No such file or directory
dpkg: error processing octave3.2 (--configure):
 subprocess installed post-installation script returned error exit status 127
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Errors were encountered while processing:
 octave3.2
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
Architecture: amd64
Date: Fri Oct 30 23:33:14 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: octave3.2 3.2.2-2build1
ProcEnviron:
 LANG=en_SG.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: octave3.2
Uname: Linux 2.6.31-14-generic x86_64

udippel (udippel) wrote :
Judd Storrs (storrsjm) wrote :

I think this is the result of having a broken /usr/local/bin/octave-3.2.2 before installing the package. For example this will break the install:

$ sudo ln -s /bin/false /usr/local/bin/octave-3.2.2
$ sudo apt-get install octave3.2

This fails with:

dpkg: error processing octave3.2 (--configure):
 subprocess installed post-installation script returned error exit status 1

Removing the link allows install to succeed.

$ sudo rm /usr/local/bin/octave-3.2.2
$ sudo apt-get install octave3.2

Judd Storrs wrote:
> I think this is the result of having a broken
> /usr/local/bin/octave-3.2.2 before installing the package. For example
> this will break the install:
>
> $ sudo ln -s /bin/false /usr/local/bin/octave-3.2.2
> $ sudo apt-get install octave3.2
>
> This fails with:
>
> dpkg: error processing octave3.2 (--configure):
> subprocess installed post-installation script returned error exit status 1
>
> Removing the link allows install to succeed.
>
> $ sudo rm /usr/local/bin/octave-3.2.2
> $ sudo apt-get install octave3.2
>
>

Confirmed. (It wasn't actually broken before the upgrade 9.04->9.10, though)

Thanks so much!

Uwe

This problem looks to be related to some manual installation of octave, so i'm marking the bug as such. Feel free to report any other problems you find.

Changed in octave3.2 (Ubuntu):
status: New → Invalid
ken (kmailuk+launchpad) wrote :

My /usr/local/bin directory is empty but installing octave3.2 still returns an error.

Running Ubuntu 9.10 (upgraded from 9.04) on amd64.

The last few lines of the install read:
Setting up octave3.2 (3.2.2-2build1) ...
error: `pkg' undefined near line 0 column 1

dpkg: error processing octave3.2 (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Processing triggers for menu ...
Errors were encountered while processing:
 octave3.2
E: Sub-process /usr/bin/dpkg returned an error code (1)

ken (kmailuk+launchpad) wrote :

Related bug: 418389

@ken
What does the output of 'which octave-3.2.2' give you?

ken (kmailuk+launchpad) wrote :

@Andreas
I have tried installing and uninstalling octave3.0 and ocate3.2 in various ways. It now appears to have installed correctly. I think the problem was that
> sudo apt-get --purge remove octave3.2
did not remove octave3.2-common. After issuing the above command I followed it up with
> sudo apt-get --purge remove octave3.2-common
Then my attempt to intall
> sudo apt-get install octave3.2
worked successfully.

I do not know what exactly I did, but it is now installed and working correctly.

Their seem to be some combination of the octave packages being in different removed/half-installed/installed states that causes the above postinst to fail. The postinst calls the octave binary with a command which fails in that state. If you hit it again, please post the state of octave packages, eg. 'dpkg -l | grep octave'.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers