synaptic cannot remove fftw3 and libsdl-net1.2

[david parker]

Binary package hint: synaptic

this is the output from synaptic

E: fftw3: subprocess post-removal script returned error exit status 139
E: libsdl-net1.2: subprocess post-removal script returned error exit status 139

I am prevented from making any other changes via synaptic whilst this problem persists.

I am using Ubuntu 6.10

[Michael Vogt (mvo)]

Thanks for your bugreport.

I can't reproduce the problem here on my local machine. Can you please give me the versions of the two packages?

Then please run the following command in a terminal and attach the output to this bugreport:

sudo sh -x /var/lib/dpkg/info/fftw3.postrm remove

sudo sh -x /var/lib/dpkg/info/libsdl-net1.2.postrm remove

Thanks,
 Michael

[david parker (acmecorp)]

fftw3 version 3.1.1-2
libsdl-net1.2 version 1.2.5-7

sudo sh -x /var/lib/dpkg/info/fftw3.postrm remove

+ set -e
+ [ remove = remove ]
+ ldconfig
Segmentation fault

sudo sh -x /var/lib/dpkg/info/libsdl-net1.2.postrm remove

+ set -e
+ [ remove = remove ]
+ ldconfig
Segmentation fault

[david parker (acmecorp)]

I have done as you asked.

Thanks for the prompt reply

David

[Michael Vogt (mvo)]

Thanks for the info.

Its not a good sign if "ldconfig" segfaults. could you please install gdb and try to get a backtrace? https://wiki.ubuntu.com/Backtrace explains how. And attach it here?

Thanks,
 Michael

[david parker (acmecorp)]

Luckily I've already got the latest version of gdb installed, would I be
right in thinking that if I hadn't then apt-get would still try to
remove the offending packages before downloading gdb and thus be unable
to complete the transaction?

I ask this question merely to help anyone else who may experience a
similar problem.

thanks for your continuing help

David

[david parker (acmecorp)]

I need a little help here, it's been about fifteen years since I last
used gdb and I couldn't fully follow the instructions on the web site.

thanks

David

[david parker (acmecorp)]

I've now discovered that a re-boot cures this problem.

Thanks for all the help

David

[Michael Vogt (mvo)]

Thanks for this additional information.

If the problem cured itself via a reboot I would like to close the problem for now and reopen it if it appears again. The we can try to get a gdb backtrace again.

Cheers,
 Michael